3 ms·
The Apache Software Foundation has something similar. It's mostly for ass-covering should future "SCO"s arise.
by davidw 17y ago
The Apache Software Foundation has something similar. It's mostly for ass-covering should future "SCO"s arise.
- Maciek416 17y agoThat makes sense. You'd almost expect that every single widely-used project should have something like this (jQuery is a good example).
- jrockway 17y agoNot really. It's more for ease in relicensing. When contributers don't assign copyright, the license can never change, since their contributions bind the original project to the original license. Emacs is a good example of this working. Because Emacs is copyrighted by GNU and not its contributers, it was a simple matter of changing a few strings to change the license from GPL2 to GPL3. For projects without copyright assignments, this is not possible; the Linux kernel will be GPL2 forever, even if someone wants to change. Some copyright holders are long dead, and contacting their estate to change some terms in the license agreement is impractical. (This is a shame, too; a GPL3 version of Linux would be great for hardware hackers everywhere.)
- davidw 17y agoWhat you are describing is the motivation behind the FSF assignment requirement, what I was talking about was the Apache Software Foundation: http://www.apache.org/licenses/ http://www.apache.org/licenses/ (see 'Contributor License Agreements')