4 ms·
In the README > This is not an officially supported Google product. Why was this project published under an account named "Google Workspace"? Google seems to
by waterTanuki 4mo ago
In the README
> This is not an officially supported Google product.
Why was this project published under an account named "Google Workspace"? Google seems to want to have their cake and eat it too, same with the cli creator.
If you want to publish a project under open source and you are the sole creator/owner -> do it in your own time, under your OWN individual github account. Nothing good has ever come from ceeding control of these things to giant corporations who only care how much it will increase their profit next quarter.
- ventana 4mo agoXoogler here who also published things within Google repositories. This is a standard phrase that you should have in the README to get an approval to publish your repository to GitHub, even if it is totally related to the Google business (as mine were). My guess is that it's similar to the regular "no warranty" clause in the licenses, just explicitly opting out this code from any possible agreements Google might have with its customers. Google's process to publish to open source is well documented and this documentation is public. [1] is the document that requires this disclaimer. [1]: https://opensource.google/documentation/reference/releasing/publishing https://opensource.google/documentation/reference/releasing/...
- waterTanuki 4mo agoThe issue isn't lack of documentation, it's the policy itself. If it's not supported by google it shouldn't be published under their name. Simple.