Reactive-gRPC is effectively paused
Ryan Michela
After fits and starts of trying to re-home reactive-grpc, I've decided to pause any further work on the project.
Reactive-grpc is essentially feature complete and continues to work with current versions of gRPC-Java. At least, it will until gRPC or Protobuf introduce a hard breaking change. Liberal use of maven dependency excludes should keep reactive-grpc from dragging along old transitive dependencies.
I want to thank everybody who has contributed to this project over the years, especially @OlegDokuka, @cbornet, and @scottslewis.
I've reached an impasse in moving reactive-grpc to the grpc-ecosystem community. There doesn't seem to be anybody left at Google maintaining grpc-ecosystem. I've been unable to procure a repo under that org. Similarly, Salesforce has, for all intents and purposes, abandoned this project. There is nobody within the company actively (or even inactively) involved. Furthermore, since leaving Salesforce a few years ago, I no longer have any of the administrative rights to this project to publish a release or fix the build.
I can't move forward with Salesforce, I can't move forward with grpc-ecosystem, and I'm not in a place in life to own a hard fork. If you are interested in picking up the reactive-grpc torch, I'll enthusiastically help you keep things going. (Maybe the kind folks at @bufbuild are interested, like they were for protoc-gen-validate)
Thank you all again for your support over the years,
-Ryan