| |||||||||||||
Let's all develop just by forkingLet's all develop just by forkingPosted Oct 2, 2006 21:30 UTC (Mon) by man_ls (subscriber, #15091)In reply to: Let's all develop just by forking by mingo Parent article: Busy busy busybox
Is it your position that because RMS has the legal power to create such a situation, that it is automatically fine, no matter what RMS's decision ends up to be?No, of course not. If the license was unfair or inconsistent I would complain loudly. I just don't see how banning DRM (which is a bad thing, as I tried to explain on other pages) can be that bad -- especially for a group of people which aren't threatened by the GPLv3 update. So your previous points of trying to claim that Linus has a similar legal position in the Linux kernel space as RMS has in the GPL license space is materially false.I assure you I'm not trying to win my arguments blindly. The previous point was that GPLv3 drafting was as closed a process as Linux development. Linus has the same "benevolent dictator" status for Linux as Stallman for GPL. Their legal positions are as you say very different, since one is developing software and the other one updating a license.
(Log in to post comments)
Let's all develop just by forking Posted Oct 2, 2006 21:56 UTC (Mon) by mingo (subscriber, #31122) [Link] I assure you I'm not trying to win my arguments blindly. The previous point was that GPLv3 drafting was as closed a process as Linux development. Linus has the same "benevolent dictator" status for Linux as Stallman for GPL. Their legal positions are as you say very different, since one is developing software and the other one updating a license. I tried to answer this before, but lets try another approach to get my point across: Linux decision process: anyone can replace Linus, Linus has no legal power to decide what goes into Linux. Hence he has no choice but to be open about every decision. He delegates "merging decisions" to subsystem maintainers and generally keeps an open mind about stuff. (i have proven this with an actual incident of Linus strongly opposing something and then merging it anyway. I could show many other similar incidents too.) If the Linux decision process were dictatorial then you'd sure be able to cite me at least one example of Linus arbitrarily rejecting a change? GPL decision process: no-one can replace RMS, and RMS has the sole legal power to unilaterally decide what goes into the GPL. There's little outside pressure on RMS to change or adapt. How you can claim that the Linux decision process is "closed as the FSF decision process" and in fact how you can claim that the two decision processes are similar in any way, is beyond my cognitive capabilities :-)
Control over the kernel Posted Oct 3, 2006 9:33 UTC (Tue) by man_ls (subscriber, #15091) [Link] Linus has no legal power to decide what goes into Linux.In fact he does: below this same page you can read: Linux is a registered trademark of Linus TorvaldsIt is not a fine legal point; he may not use that power, but that is his prerrogative. He has de iure control on Linux. Besides he publishes the kernel.org main kernels, so he also has de facto control. He delegates "merging decisions" to subsystem maintainers and generally keeps an open mind about stuff.He chooses to do so, sometimes. There are counter-examples like micro-kernel design and alternative security frameworks, as I gather from LWN. If the Linux decision process were dictatorial then you'd sure be able to cite me at least one example of Linus arbitrarily rejecting a change?Those mentioned above, or his unillateral decision of using a proprietary tool (BitKeeper) despite lots of people advising against it (including many kernel submaintainers like Morton). People proposed free alternatives or even developing a new one but they were all rejected. Remember that the arguments in favour of BitKeeper were that it enabled Linus' workflow, there were no free alternatives and developing one would take years. After withdrawal of the free client, in 15 days Linus had a working replacement. Allowing binary modules is another area where Linus' opinion is final. Discussing these issues with a kernel developer is funny. I'm sure domain experts can suggest many more dictatorial changes in areas where there is no consensus. GPL decision process: no-one can replace RMS, and RMS has the sole legal power to unilaterally decide what goes into the GPL. There's little outside pressure on RMS to change or adapt.Little pressure? I don't think so. 22 years ago he had the whole industry against him; 8 years ago he confronted a pro-industry lobby (OSI) on his own. Free software (and "open source") licenses sprout every month. And still the GPL is used in 85% of free software projects. I would say that is enough pressure. RMS plus Moglen plus the FSF decide what goes into the GPL, just as Linus decides what goes into Linux. If you don't like it you can discuss it on the GPLv3 page (or on lkml), otherwise just choose another license (or another kernel). You can fork the kernel, and you can impose additional restrictions or permissions on top of the GPL (or rewrite it and change some aspects). Both are top-down processes; the fact that the dictators disagree on certain respects and you are friends with one of them does not change anything, Ingo. Linus listens to you, but that is because you think like he does; if you proposed a change to a micro-kernel architecture would he listen to you? If suddenly most kernel submaintainers proposed it? Would they be submaintainers for long?
|
|||||||||||||