News for hackers. Stuff that matters.
Re:The GNU Manifesto Turns Thirty by JoshTriplett on Tuesday March 17, 2015 @01:27PM (#9219612)
I do find it disappointing when someone intentionally makes work GPL without knowing the implications. The intention of GPL is very much to prevent use in proprietary software, and to make life more difficult for proprietary software users, while creating an ecosystem of software only usable by other Free Software. However, even RMS and the Free Software Foundation have explicitly acknowledged that there are cases where an all-permissive license like MIT or (2-clause or 3-clause) BSD makes sense; for instance, when implementing a free format to replace a proprietary one, such as Ogg Vorbis or WebM. See https://www.gnu.org/licenses/license-recommendations.html for instance: "For these projects, widespread use of the code is vital for advancing the cause of free software, and does more good than a copyleft on the project's code would do." (That page actually recommends Apache 2.0 now, which is GPLv3 but not GPLv2 compatible; it used to recommend GPLv2-compatible licenses, and personally I still do recommend using MIT when trying to promote the widest possible use.)
Re:The GNU Manifesto Turns Thirty by nullc on Tuesday March 17, 2015 @01:51PM (#9219818)
Apache 2 is important to avoid things like the situation with LLVM where aggressive patent holders like Apple and Qualcomm feed the project with patent encumbered contributions, so that sorting out what parts of it that you're patent exposed on or not is basically impossible (meaning, you'll take a blanket license at your expense if you depend on it).

If you're not using a more modern license with an explicit patent grant you should at least have some agreement from contributors to make any of their own patents required for their contributions available to all other users of the software and its derivatives. Otherwise you may find that your permissive licensing isn't.

Re:The GNU Manifesto Turns Thirty by legulere on Tuesday March 17, 2015 @02:21PM (#9220092)
http://llvm.org/docs/DeveloperPolicy.html#patents

> If you or your employer own the rights to a patent and would like to contribute code to LLVM that relies on it, we require that the copyright owner sign an agreement that allows any other user of LLVM to freely use your patent.

Re:The GNU Manifesto Turns Thirty by nitrogen on Tuesday March 17, 2015 @03:09PM (#9220457)
A copyright license that includes an explicit patent license would allow non-LLVM users to use the patents as well, as they would need to be able to in order to exercise their rights under the LLVM copyright license and use LLVM code in something that is not LLVM.