4 ms·
Interesting. This is from 2010, but random googling took me here: https://github.com/snapframework/snap-server/commit/5e4850d4cb74c75e706df509b90befc95263746a h
by ominous 10y ago
Interesting. This is from 2010, but random googling took me here: https://github.com/snapframework/snap-server/commit/5e4850d4cb74c75e706df509b90befc95263746a https://github.com/snapframework/snap-server/commit/5e4850d4...
The situation is quite simple:
- pre-existing work I contributed to this project remains under my copyright
- contributions other people make to this project remain under their own copyrights
- contributions I make to this project subsequent to November 2010 are under Google copyright
- nobody should really give a shit about this because a) I freely agreed to this even though Google has a process where I could have asked to retain my own copyright because b) the code is BSD licensed and you can use it however you like regardless of who owns the copyright.
~ https://github.com/gregorycollins https://github.com/gregorycollins
- uiri 10y agoThis is correct with respect to Google's process. When it comes to Amazon, you have employees sending patches upstream anonymously because the company culture is against contributing anything back to the open source community.