would love community contributions :-). I see some efforts in community but nothing very concrete yet. You can suggest project in gRPC Ecosystem. https://github.com/grpc-ecosystem
gRPC core libraries for C++ are written in pure C. We need to extend these to use a pure C implementation of Proto and create a C based generated API. We have experimented with this and some users have also tried it. We are looking to add this in future and also welcome contributions.
So gRPC evolved out of Stubby. An excellent show of force would be to announce that Stubby has been internally replaced by gRPC, so that the "gRPC is internet scale" assertion can be more than just a gimmick. Knowing nothing of the first one and very little of the second I imagine it would be some important task, so I have to ask: do you plan to internally run with the stuff you open-sourced ? What is missing ?
Been a couple years since I worked at Google, but when I was there, Stubby was pretty intimately connected with Google's networking fabric, datacenter hardware, and internal security & auditing needs. None of this is at all useful to external customers - you're not running on Google's proprietary hardware, you don't interface with their monitoring & auditing systems, etc.
As an ex-Googler, using gRPC feels just like using Stubby: the interfaces are the same, the serialization code is the same, the only thing different is the networking code and transparent hooks into other systems.
gRPC faces a longer road to feature parity with Stubby. For external adopters this is not an issue, so it makes sense that it would be available to the public in advance of its adoption inside Google.
not to mention the internal infra grows all these knobbly bits as one-off feature requests for large/influential teams, that aren't necessarily useful outside the goog
