> follow the proper release procedures for it
What happens when your thing
or nothing close to your thing
will ever see the light of day?
Is that relevant here,
given that Google was creating an official thing
quite close to his thing
at the same time?
(And why are we writing like this?)
None of that is relevant. You're working on things for their employer, they control when and if anything is released. Most of us have worked on projects that were cancelled - even when that happens you don't just release it anyway.
1. If google said ok but don't release under google’s name/in google’s repo, do that.
2. If google said no this goes against our goals for the product, don't release it if you want to keep working for google?