Archive for the 'gnu' Category...
Filed under gnu
cyclop writes “I am coding a data analysis application in my laboratory that I would like to release as free (as in freedom) software. Moreover I am going to begin a small OSS game that will be based, in part, on GPLv2 libraries. Problem is: in both cases, I’d like to be able to exchange code both with GPLv2 and (future) GPLv3 projects. I have no particular passions about either license — only thing is I don’t want BSD-style ‘do anything you want’ licensing but a copyleft license. I know that GPLv2 and GPLv3 are not compatible. What can I do? Double licensing? Is there a compatible-with-both license? Adding exceptions? What do you think is the best way to address the GPLv2-to-GPLv3 transition without ending up on one or the other side of the barricade?”
Read more of this story at Slashdot.
Share and Enjoy:
These icons link to social bookmarking sites where [...]
Original post by kdawson and software by Elliott Back
Filed under gnu
chessweb writes “Here is a rather enlightening article by Richard Stallman on the reasons for moving to GPLv3 that puts the previous TiVo post into the right context.” From the article: “One major danger that GPLv3 will block is tivoization. Tivoization means computers (called ‘appliances’) contain GPL-covered software that you can’t change, because the appliance shuts down if it detects modified software… The manufacturers of these computers take advantage of the freedom that free software provides, but they don’t let you do likewise… GPLv3 ensures you are free to remove the handcuffs. It doesn’t forbid DRM, or any kind of feature. It places no limits on the substantive functionality you can add to a program, or remove from it. Rather, it makes sure that you are just as free to remove nasty features as the distributor of your copy was to add them.”
Read more of this story at Slashdot.
Share and [...]
Original post by kdawson and software by Elliott Back
Filed under gnu
An anonymous reader writes “The most notable changes found in this latest draft include making GPLv3 compatible with version 2.0 of the Apache license, ensuring that distributors who make discriminatory patent deals after March 28 may not convey software under GPLv3, adding terms to clarify how users can contract for private modification of free software or for a data center to run it for them, and replacing the previous reference to a U.S. consumer protection statute with explicit criteria for greater clarity outside the United States. The draft also does not prohibit Novell from distributing software under GPLv3 ‘because the patent protection they arranged with Microsoft last November can be turned against Microsoft to the community’s benefit,’ FSF executive director Peter Brown said.”
Read more of this story at Slashdot.
Share and Enjoy:
These icons link to social bookmarking sites where readers can share and discover new web pages.
Original post by CowboyNeal and software by Elliott Back
Filed under gnu
QCMBR writes “A new Microsoft-funded study by a Harvard Business School professor concludes that developers don’t want extensive patent licensing requirements in the GPL3. There are significant problems with the study, however, especially given the very small sample size. ‘Although 332 emails were sent to various developers, only 34 agreed to participate in the survey — an 11 percent response rate. Of the 34 developers who responded, many of them are associated with projects like Apache and PostgreSQL that don’t even use the GPL.’ Ars points out that the GPL3 draft editing and review process is highly transparent and inclusive ‘to an extent that makes MacCormack’s claims of under-representation seem difficult to accept given the small sample size of the study and the number of respondents who contribute to non-GPL projects.’”
Read more of this story at Slashdot.
Share and Enjoy:
These icons link to social bookmarking sites where readers can share and [...]
Original post by kdawson and software by Elliott Back
Filed under gnu
QCMBR writes “A new Microsoft-funded study by a Harvard Business School professor concludes that developers don’t want extensive patent licensing requirements in the GPL3. There are significant problems with the study, however, especially given the very small sample size. ‘Although 332 emails were sent to various developers, only 34 agreed to participate in the survey — an 11 percent response rate. Of the 34 developers who responded, many of them are associated with projects like Apache and PostgreSQL that don’t even use the GPL.’ Ars points out that the GPL3 draft editing and review process is highly transparent and inclusive ‘to an extent that makes MacCormack’s claims of under-representation seem difficult to accept given the small sample size of the study and the number of respondents who contribute to non-GPL projects.’”
Read more of this story at Slashdot.
Original post by kdawson and software by Elliott Back
