Live data from Hacker News

Employer (Google?) forbids contributions to some open-source projects

github.com

1–8 of 8 posts

Re: Employer (Google?) forbids contributions to some open-source projects

#5
post #3

This is not uncommon for bigcorps. Could be many reasons for this, including licensing, competition, or fear of data leakage. Bit surprising for this to come from Google though.

This would make sense for larger infrastructural projects. But for a single feature extension to a command line shell?

Re: Employer (Google?) forbids contributions to some open-source projects

#7
post #3

This is not uncommon for bigcorps. Could be many reasons for this, including licensing, competition, or fear of data leakage. Bit surprising for this to come from Google though.

Google's policies on this are public: https://opensource.google/docs/patching/

Re: Employer (Google?) forbids contributions to some open-source projects

#8
post #7
post #3

This is not uncommon for bigcorps. Could be many reasons for this, including licensing, competition, or fear of data leakage. Bit surprising for this to come from Google though.

Google's policies on this are public: https://opensource.google/docs/patching/

This is unfortunate. An employer deciding what projects you can contribute to on your own time and with your own resources seems like an overstep to me.