| ▲ | OJFord 12 hours ago | |||||||||||||||||||||||||||||||||||||||||||
I don't get it – you called the GitHub org 'googleworkspace' and used the Google logo? Presumably without permission? Don't Googlers regularly open-source side projects under the official org(s)? Did you really think this was going to be fine, or was it 'growth hacking' with tougher consequences than expected? | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | dekhn 12 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||||||||
I believe it's an official or semi-official Google github org. Typically at Google there is some process you are supposed to follow when opensourcing your code, and a repo like this exists specifically to get more people to use the API. The CLI still exists at the repo and the repo still has the Google branding, so it's 99% certain this is a Google repo. If you do an end-run around the normal open source publishing you can get in trouble- up to and including termination- but my guess is there is more context around the firing than just "posted open source code to work with standard Google APIs". For example, you can get punished at google (up to and including termination) for raising your voice in a meeting. | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | whstl 5 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||||||||
Google has quite a few of those. It's hard to figure out if they're really official. https://github.com/googleapis/googleapis/discussions/865 / https://github.com/google-research/big_vision / https://github.com/googleapis | ||||||||||||||||||||||||||||||||||||||||||||