Migrate reactive-grpc to grpc-ecosystem

[rmichela]

With the loss of a consistent release sponsor at Salesforce, it's time to move this repo to the grpc-ecosystem org.

Tasks to do:

• Your project is currently hosted in a public repository.
• Your project's license is the Apache license 2.0.
• Your project doesn't depend on third party libraries with copyleft licenses such as AGPL and GPL.
• Your project has a top-level README.md with the following information:
  • Project overview
  • How gRPC is used
  • A list of external project dependencies such as third-party libraries
  • Build instructions
  • Automated tests and test instructions
• Ensure that all project contributors have signed Google's Contributor License Agreement, accepting that all license and patent rights are determined by the CLA under the Apache license.
• Get written signoff from Salesforce
• Once you've addressed all of the requirements listed above, complete and submit a gRPC Ecosystem Project Addition Request Form.
• Update Maven coordinates
• Update Java package names
• Add an explicit module-info.java for Java >9 users
• Secure access to new Maven repository at Sonatype
• Release version 2.x

[bsideup]

Hi @rmichela! Anything you could use help with? Would love to see the move and a release 🙌

[o-shevchenko]

Hi
@rmichela Do you have any updates? Is it still in progress?
Thanks!

[rmichela]

I'm coordinating with google and salesforce. I'm trying to avoid forking the project and renaming it.

[o-shevchenko]

Thanks @rmichela !
We actively use this project and want to contribute. I hope we will see new releases.
Thanks for the support and for pushing migration!

[scottslewis]

Hi @rmichela. I have an OS project: https://github.com/ECF/grpc-RemoteServicesProvider

that depends upon this project...to provide the implementation of using rx3 API for protofile-defined stream services with flow control. See the videos on main page for an example: going from protofile-defined service (with unary and streaming method) to generate the code for an OSGi Service.

I would like to update these components to grpc-java and protoc more recent versions (4.x for protoc). To do this, however, I would expect reactive-grpc (runtime and protoc plugin) might have to be rebuilt. It's possible no update to reactive-grpc will be necessary, but I haven't tried yet.

Any more news about this transition to grpc-java ecosystem? Once there, who is going to support it? I might be able to offer some help in the transition and ongoing support if desired.

Further, I would be willing to contribute the https://github.com/ECF/grpc-osgi-generator (a protoc plugin that generates a remote service interface class for OSGi's interface/impl separation), if you and/or the grpc-java people are interested. I'm even considering extending this generator to python so that Java <-> Python remote services can be easily created via osgi and ipopo's RSA support: https://ipopo.readthedocs.io/en/3.0.0/ ...for dynamic, Java<->Python, injection-based, standards-defined metadata (RSA), grpc/reactivex api services.

Thanks.