3 ms·
It's not only companies who ask for license changes, Google and other employees ask licences to be changes too simply because the corporation they work for forb
by Avamander 8y ago
It's not only companies who ask for license changes, Google and other employees ask licences to be changes too simply because the corporation they work for forbids even looking at the source otherwise. For example: https://github.com/pebble-dev/rebblestore-api/pull/31 https://github.com/pebble-dev/rebblestore-api/pull/31
- teddyh 8y agoIn my view, that’s more an unexpected feature. I can give people freedom to do what they need to do with the software I write, at the same time as I can, in effect, prevent Google from even reading it? Sign me up!
- vonmoltke 8y agoThat is what the commenter claims, but the link provided for support refers only to submitting patches that cover work Google owns. I found nothing about a prohibition on reading code, not a prohibition on using those licenses for personal projects.
- DannyBee 8y agoThis is false for Google (I created and owned the relevant policies). Google publishes it's open source docs, so you can just look: https://opensource.google.com/docs/using/agpl-policy/ https://opensource.google.com/docs/using/agpl-policy/ We also banned patching agpl projects, I'm just too lazy to find that link for you.
- Avamander 8y agoCan you please share why patching is forbidden for AGPL? To avoid what?