| |||||||||||||
Possible routes to kernel on GPLv3Possible routes to kernel on GPLv3Posted Jan 27, 2007 3:15 UTC (Sat) by Arker (guest, #14205)In reply to: Possible routes to kernel on GPLv3 by sbergman27 Parent article: GPL 3: An Open-Source Earthquake? (CRN)
When you open *anything* up to public comment like this, it goes without saying that comments which amount to 'your goals are completely wrong, you should scratch the entire idea' aren't likely to be implemented. So what? Do you really expect them to read your peanut-gallery screechings and suddenly withdraw the idea and announce that v2, riddled as it is with known exploits, is perfect forever and all time? Please, get real.
(Log in to post comments)
Possible routes to kernel on GPLv3 Posted Jan 27, 2007 18:33 UTC (Sat) by bronson (subscriber, #4806) [Link] I don't remember the kernel guys saying that.
Possible routes to kernel on GPLv3 Posted Jan 27, 2007 23:31 UTC (Sat) by Arker (guest, #14205) [Link] Well that's exactly what some of them have said, boiled down to the essentials. They like the loopholes that v3 is being designed to close. The only way to make someone taking that position happy with v3 would be to abandon the fundamental reason for the existence of the GPL, all versions of it.
Possible routes to kernel on GPLv3 Posted Jan 28, 2007 0:07 UTC (Sun) by vonbrand (subscriber, #4458) [Link] They like the loopholes that v3 is being designed to close. They haven't say such a thing, they said that GPL should not try to get into areas that aren't properly a code license's. Also, GPLv2 gives certain specific rights, what is wrong with with wanting to give just that ones? Sure, GPLv2 would gain a lot by cleaning up the language, and making it (more) compatible with non-US laws. Besides, the 4 freedoms (and GPLv2) haven't ever talked about "If you get a device running free code, you are entitled to run anything else you want on it". I can certainly see uses for open source that require (for complying with regulations, for safety, etc) running only certified programs. Sure, the most talked about case is restricting users access to digital content, but nothing GPLvX could do will make any difference for or against that, but it will hurt other uses badly.
Possible routes to kernel on GPLv3 Posted Jan 28, 2007 0:57 UTC (Sun) by b3timmons (guest, #40286) [Link] They haven't say such a thing, they said that GPL should not try to get into areas that aren't properly a code license's. Also, GPLv2 gives certain specific rights, what is wrong with with wanting to give just that ones? Sure, GPLv2 would gain a lot by cleaning up the language, and making it (more) compatible with non-US laws. The GPL has always applied to distributors, so why should it not be adjusted to whatever new distribution methods such as Tivos that have developed in a decade and a half (incredibly long in this biz) since v2? To limit rights as in v2, are you not aware of the exceptions language in v3 that allows certain restrictions to be imposed? Besides, the 4 freedoms (and GPLv2) haven't ever talked about "If you get a device running free code, you are entitled to run anything else you want on it". I can certainly see uses for open source that require (for complying with regulations, for safety, etc) running only certified programs. Sure, the most talked about case is restricting users access to digital content, but nothing GPLvX could do will make any difference for or against that, but it will hurt other uses badly. Just a trivial google search on the terms "gplv3", "medical", "devices" gives as the top hit: http://fsfe.org/en/fellows/ciaran/... which is a recent summary of thought which has existed for some time now and which throws your concern here into doubt. The bottom line is that the GPL has always aimed to uphold the four freedoms, and with this protection now diminished from loopholes, v3 is needed to fix them.
Certifiable Posted Jan 29, 2007 23:07 UTC (Mon) by GreyWizard (guest, #1026) [Link] Many things (glassware, candles, ladders, power tools) that might maim or kill someone if carelessly handled, yet I am allowed to own and even modify them if I comply with regulations myself. So I'm afraid I can't share your enthusiasm for a world where I am denied as many choices as technologically possible in the name of safety. I would rather assume responsibility for my own actions and live in a free society.
Also you are mistaken about the "four freedoms" enumerated by the FSF. Number one is "the freedom to study how the program works, and adapt it to your needs." To do that I must be able to run modified software on the devices I actually own unless we suppose I have unlimited resources. Releasing software under a license that ensures this freedom more strictly than GPLv2 might not change the world but it seems worth trying -- after all the same thing was said about GPLv2 once.
Possible routes to kernel on GPLv3 Posted Jan 28, 2007 6:07 UTC (Sun) by bronson (subscriber, #4806) [Link] "[The kernel guys] like the loopholes that v3 is being designed to close."
Arker, that's an absurd thing to say. Most of them are very happy with v3, they just think it goes a little too far when it comes to DRM. Where did you get the idea that they want it full of loopholes?
Possible routes to kernel on GPLv3 Posted Jan 29, 2007 22:20 UTC (Mon) by Arker (guest, #14205) [Link] I did say *some* - I'm quite aware that there is considerable difference of opinion.
But the ones who have been making the anti-gpl noises are indeed propounding a position that says the loopholes are good, they don't need to be addressed. They say they don't *want* to prevent companies following Tivos lead and effectively making the software non-free. As long as that's their position, they won't be interested in version three, they're going to stay with version 2, and they aren't likely to have anything useful to contribute to the v3 discussion, since they don't agree with the purpose of the thing to begin with.
|
|||||||||||||