3 ms·
Working in places that were based off permissively licensed software, the default position we had was "no upstreaming" and if I wanted to upstream something I n
by rvp-x 7y ago
Working in places that were based off permissively licensed software, the default position we had was "no upstreaming" and if I wanted to upstream something I need to ask for permission.
when you're contributing to GPL software, you don't need your employer's permission for it to be upstreamed. If they release the code, and don't violate the GPL, then there's nothing the employer can do to stop it from going upstream.
- lilyball 7y ago> when you're contributing to GPL software, you don't need your employer's permission for it to be upstreamed. Yes you do. Except the permission in this case is "permission to use the library" in the first place, which is a much higher bar than permission to upstream changes to a permissively-licensed library because using a GPL library has much farther-reaching implications than merely contributing changes back.
- dragonwriter 7y ago> when you're contributing to GPL software, you don't need your employer's permission for it to be upstreamed Yes, you do; if you are contributing to it, you need to have exactly that permission. If you are working on a derivative, you need that permission before you can contribute it to anyone else, including upstream. > If they release the code Plenty of people work on internal code for their employers, so this is not a given.