4 ms·
Release your patch on the same license as the project. The End. Everyone is granted a license to the patch under that license. Nobody can take your code and re-
by harry8 7y ago
Release your patch on the same license as the project. The End. Everyone is granted a license to the patch under that license. Nobody can take your code and re-license under a non-compatible license.
"a. Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties. "
The project has a license, just use it.
- spookthesunset 7y agoYou realize most FSF projects have similar copyright assignments, right?
- harry8 7y agoI have never been asked for a copyright assignment by the FSF for a patch. Maybe that happens and if and when it does I'd talk about that too. https://lwn.net/Articles/359013/ https://lwn.net/Articles/359013/ This is hardly a dangerous, radical criticism that is novel and needs to be fought on all fronts...
- froydnj 7y agoHow big and/or complicated have your patches been? Copyright assignment is not necessary for not-legally significant changes: https://www.gnu.org/prep/maintain/maintain.html#Legally-Significant https://www.gnu.org/prep/maintain/maintain.html#Legally-Sign... Copyright assignment has long been used as an argument of why not to contribute to FSF projects, and is arguably one of the reasons that Clang/LLVM were able to garner contributions from a much broader set of folks.
- teddyh 7y agoYou realize that FSF is in a different league of trustworthiness than Microsoft, right?