Novell preps SUSE Enterprise Linux 10 SP1
|
|
|
Comments (46)
26 earlier comments in the full thread.
Quoting:Before there was GPL, there was BSD. Apache is not GPL. Mozilla Firefox is not GPL. OpenOffice.org is not GPL. PostgreSQL is not GPL.
Darren,
It is the prerogative to use whatever license they want, it is their code. One question though, why didn't they use BSD license? I guess they are aware and cautious of the freeloaders and opportunistic companies.
Quoting:The majority of the FOSS community disagrees with your statement:
I wouldn't be so sure about the majority especially the developers of the community who write the code, otherwise, they would have released their code under licenses other than the GPL. As you know, most of FOSS code (Linux & what have you) is released under the GPL.
Quoting:Before there was Richard Stallman
Although it is true that free code was being exchanged back in the sixties, but the community at that time mainly consisted of educational researches and developers. There weren't many people outside the educational circles (which is a true FREE ecosystem for science and such) or companies involved as we have today.
FOSS software advanced, grew, flourished, and proliferated because everyone in the community believes that the GPL is a fair guideline to established fair use and good license to protect FREE code.
RMS didn't invent the FOSS concept. This concept existed centuries ago. But he created the GPL to establish the guidelines and rules for sharing and protecting FOSS code. Before the GPL, there were no licenses to prevent freeloaders, Leeches and code theives. The GPL is what made FOSS what it is today. That is a fact that can't be ignored nor forgoten.
Considering the success of projects like Apache and PostgreSQL, I'd say that it isn't true that
Quoting:Before the GPL, there were no licenses to prevent freeloaders, Leeches and code theives.seeing as their license are base on BSD licensing which predated the GPL.
Darren -
Might as well try talking to a wall.
The GPL has benefitted mightily from marketing and the network effect. RMS has preached his little self up a storm. Linux is GPL'd, and Linux is the free software superstar.
Put those together, and what do you think budding projects are likely to use?
Might as well try talking to a wall.
The GPL has benefitted mightily from marketing and the network effect. RMS has preached his little self up a storm. Linux is GPL'd, and Linux is the free software superstar.
Put those together, and what do you think budding projects are likely to use?
Non-copyleft licenses don't prevent others from using libre code in a non-libre-licensed project, which is Abe's point. I would also wonder about the strength of your majority argument, Darren, given that the GNU GPL remains the most-used FOSS license. You're obviously correct that the BSD/X-11 style licenses don't allow people to make the libre code non-libre. That doesn't, however, prevent - as Abe is trying to point out - people from using that same code in a non-free project. It may be true that some who use the GPL don't consider non-free developers as leeches when using the BSD-licensed code. However, a good many people choose the GPL specifically because it prevents 'leeching'.
> a good many people choose the GPL specifically because it prevents 'leeching'.
It's the only license I would ever consider. GPL code helps build the free software community, and that benefits me. BSD code is charity. I know I'm not alone in this viewpoint. Of course, I also know other developers who don't care.
It's the only license I would ever consider. GPL code helps build the free software community, and that benefits me. BSD code is charity. I know I'm not alone in this viewpoint. Of course, I also know other developers who don't care.
Quoting:Might as well try talking to a wall.
it is a copout, and no further comments from me.
>it is a copout
Hardly. Sometimes the truth is simply the truth.
Hardly. Sometimes the truth is simply the truth.
> The GPL has benefitted mightily from marketing and the network effect.
> RMS has preached his little self up a storm.
> Linux is GPL'd, and Linux is the free software superstar.
>
> Put those together, and what do you think budding projects are likely to use?
Or maybe it's because, you know, there's an evolutionary reason the GPL thrives? Because it's more fit?
Btw, I'm still waiting for a straight answer from you as to "can you think of a /relicensed/ fork that turned out well for the Free Software version?" over here: http://lxer.com/module/forums/t/24879/ . It seems like you're avoiding giving any justification for what you say. If you're having a hard time coming up with examples, maybe you should start asking yourself why you think the GPL doesn't succeed naturally due to reducing the negative pressure on Free Software projects rather than repeating the claim that it's mainly just momentum as above?
> Might as well try talking to a wall.
Pot + kettle?
Or maybe it's because, you know, there's an evolutionary reason the GPL thrives? Because it's more fit?
Btw, I'm still waiting for a straight answer from you as to "can you think of a /relicensed/ fork that turned out well for the Free Software version?" over here: http://lxer.com/module/forums/t/24879/ . It seems like you're avoiding giving any justification for what you say. If you're having a hard time coming up with examples, maybe you should start asking yourself why you think the GPL doesn't succeed naturally due to reducing the negative pressure on Free Software projects rather than repeating the claim that it's mainly just momentum as above?
> Might as well try talking to a wall.
Pot + kettle?
>Or maybe it's because, you know, there's an evolutionary reason the GPL thrives?
Could be
>Because it's more fit? More fit at what? What does "more fit" mean in this context? Better publicized, for sure...and yet...I would bet (don't know) that some percentage of people licensing their software under the GPL don't fully understand it, which, to my way of thinking, means that the details of the license itself wasn't very important in their choice.
>Btw, I'm still waiting for a straight answer from you as to "can you think of a /relicensed/ fork that turned out well for the Free Software version?"
Why are you waiting? Your asking a question (and then restricting the potential answers -- there's a great approach to free speech -- "Give me an answer you like so long as it's the one I want") doesn't obligate me to answer, especially since I never made the claim that forks benefit the original project. Most of the forks I've seen happen because people are dissatisfied in some way with the original project. X.org is the example. X.org is doing fine, xfree86 is not. By your definition -- at least as I understand it, that was a destructive fork because it seriously hurt the original project. You might disagree. After all, you're the one making up this "destructive fork" thingie that I don't even believe in.
>Because it's more fit? More fit at what? What does "more fit" mean in this context? Better publicized, for sure...and yet...I would bet (don't know) that some percentage of people licensing their software under the GPL don't fully understand it, which, to my way of thinking, means that the details of the license itself wasn't very important in their choice.
>Btw, I'm still waiting for a straight answer from you as to "can you think of a /relicensed/ fork that turned out well for the Free Software version?"
Why are you waiting? Your asking a question (and then restricting the potential answers -- there's a great approach to free speech -- "Give me an answer you like so long as it's the one I want") doesn't obligate me to answer, especially since I never made the claim that forks benefit the original project. Most of the forks I've seen happen because people are dissatisfied in some way with the original project. X.org is the example. X.org is doing fine, xfree86 is not. By your definition -- at least as I understand it, that was a destructive fork because it seriously hurt the original project. You might disagree. After all, you're the one making up this "destructive fork" thingie that I don't even believe in.
> "Give me an answer you like so long as it's the one I want") doesn't obligate me to answer
I eliminated the BS answers up front rather than wind up seeing them in a reply. For that to restrict your reply, you would have to believe some of those BS answers were valid answers to the question. Do you?
It seems from your reply you wanted to pick the "Argue the wrong question" choice, the "Well, x.org and XFree86 are effectively related by a relicensed fork, and the GPL-compatible version is doing great". x.org was not a relicensed fork of XFree86. x.org retained XFree86's license, and XFree86 changed its own license after the effective date of the fork. As such, that would be arguing the wrong question.
> especially since I never made the claim that forks benefit the original project.
Let's review what the actual question is:
My statement: "Wine switched to the LGPL later in the game (from a BSD-like permissive license) as they got fed up with the growth issues stemming from the destructive forks (relicensed forks)"
Your reply: "So, the BSD license didn't keep anybody from developing WINE. Developers who were working on it decided to switch to something else. Sounds reasonable to me, but I fail to see how it supports a hypothesis that BSD inhibits growth any more than the article can support a hypothesis that GPL inhibits growth."
So there are two issues in that reply related to the hypothesis of the BSD license inhibiting growth:
1) That since it can be abandoned, it does not inhibit growth. That's an extremely weak argument for four reasons:
* It can be said about /any/ license.
* The period while it was active is still inhibited.
* Transitions between licenses take a lot of effort that could have been spent on code (i.e., growth).
* There is a lasting harm from ever using it: I gave an example of WINE still competing against itself even after it went LGPL, as proprietary forks were produced from the BSD code.
2) That relicensed forks do not inhibit growth.
So for what I said about relicensed forks to not support a hypothesis that BSD inhibits growth, relicensed forks would have to be not significantly harmful to the BSDed projects. However, I showed specific examples of large, significant projects such relicensed forks had significantly harmed, and people in harmed projects that agreed it inhibited their growth.
So, I have provided support for the hypothesis that the BSD inhibits growth due to (for one) allowing relicensed forks, and I have asked you to give counter examples to that to the same degree as my examples for it (large, significant projects), yet you evade giving a straight answer. If you can't provide counter examples, then doesn't that mean I have successfully argued that the BSD inhibits growth due to allowing relicensed forks as I have shown those relicensed forks inhibit growth?
I eliminated the BS answers up front rather than wind up seeing them in a reply. For that to restrict your reply, you would have to believe some of those BS answers were valid answers to the question. Do you?
It seems from your reply you wanted to pick the "Argue the wrong question" choice, the "Well, x.org and XFree86 are effectively related by a relicensed fork, and the GPL-compatible version is doing great". x.org was not a relicensed fork of XFree86. x.org retained XFree86's license, and XFree86 changed its own license after the effective date of the fork. As such, that would be arguing the wrong question.
> especially since I never made the claim that forks benefit the original project.
Let's review what the actual question is:
My statement: "Wine switched to the LGPL later in the game (from a BSD-like permissive license) as they got fed up with the growth issues stemming from the destructive forks (relicensed forks)"
Your reply: "So, the BSD license didn't keep anybody from developing WINE. Developers who were working on it decided to switch to something else. Sounds reasonable to me, but I fail to see how it supports a hypothesis that BSD inhibits growth any more than the article can support a hypothesis that GPL inhibits growth."
So there are two issues in that reply related to the hypothesis of the BSD license inhibiting growth:
1) That since it can be abandoned, it does not inhibit growth. That's an extremely weak argument for four reasons:
* It can be said about /any/ license.
* The period while it was active is still inhibited.
* Transitions between licenses take a lot of effort that could have been spent on code (i.e., growth).
* There is a lasting harm from ever using it: I gave an example of WINE still competing against itself even after it went LGPL, as proprietary forks were produced from the BSD code.
2) That relicensed forks do not inhibit growth.
So for what I said about relicensed forks to not support a hypothesis that BSD inhibits growth, relicensed forks would have to be not significantly harmful to the BSDed projects. However, I showed specific examples of large, significant projects such relicensed forks had significantly harmed, and people in harmed projects that agreed it inhibited their growth.
So, I have provided support for the hypothesis that the BSD inhibits growth due to (for one) allowing relicensed forks, and I have asked you to give counter examples to that to the same degree as my examples for it (large, significant projects), yet you evade giving a straight answer. If you can't provide counter examples, then doesn't that mean I have successfully argued that the BSD inhibits growth due to allowing relicensed forks as I have shown those relicensed forks inhibit growth?
swbrown -
Good to see that you enjoy arguing with yourself.
Good to see that you enjoy arguing with yourself.
> I eliminated the BS answers
You eliminated answers you don't agree with. Whether they are BS answers is another matter entirely.
You eliminated answers you don't agree with. Whether they are BS answers is another matter entirely.
jdixon -
Proving once again that you are smarter than the average bear.
Got to give swbrown credit, though...
It's hard to lose any argument where the ground rules eliminate disagreement.
Proving once again that you are smarter than the average bear.
Got to give swbrown credit, though...
It's hard to lose any argument where the ground rules eliminate disagreement.
> You eliminated answers you don't agree with. Whether they are BS answers is another matter entirely.
I did not eliminate answers I do not agree with, I eliminated answers that are not answers at all. E.g., if someone asks you what your favorite color is, and you say "I like cartoons!", that is not an answer. Feel free to argue that one of the three /was/ an actual answer to the question and not just a way to evade it. Let's try now:
From the previous thread,
The question: can you think of a /relicensed/ fork that turned out well for the Free Software version?
The thread context: Do relicensed forks, permitted by the BSD license, inhibit growth of a project?
The answers that are not answers that I listed follow (I'll annotate each of these to explain why they are not answers if it's not clear):
1) Argue semantics with something like "Well, Apple's Darwin is Free Software, and so was FreeBSD, so they're both the Free Software version".
- This decides to word-play with the definition of "Free Software version" instead of answering, despite it not being relevant to the question in the context of the thread. Essentially, it's a smart-ass response. If you honestly felt you didn't understand what the question in context of the thread was asking for, I'll apply the context for you and phrase it as such: "can you think of a /relicensed/ fork that turned out well for the project that permitted the relicensed fork?".
- Now you see, this again leaves it open to a smart-ass response: "Yes, I can think of one". However, arguing like this is pointless, evasive, and childish, which is why people generally won't put up with it. The meaning of the question is understood, and it waits to be answered.
2) Argue misdirection with something like "Well, Konqueror was GPL, but by publishing changes as part of a huge blob with no comments, it was effectively a 'destructive' fork too by your standards".
- This is an answer to a different question, as if there was any destructive behavior it was not due to relicensing, as it was not relicensed. The question was about relicensed forks. Changing the subject is not a valid way to answer a question.
3) Argue the wrong question with something like "Well, x.org and XFree86 are effectively related by a relicensed fork, and the GPL-compatible version is doing great".
- x.org was not a relicensed fork of XFree86, so also has nothing to do with the question.
I did not eliminate answers I do not agree with, I eliminated answers that are not answers at all. E.g., if someone asks you what your favorite color is, and you say "I like cartoons!", that is not an answer. Feel free to argue that one of the three /was/ an actual answer to the question and not just a way to evade it. Let's try now:
From the previous thread,
The question: can you think of a /relicensed/ fork that turned out well for the Free Software version?
The thread context: Do relicensed forks, permitted by the BSD license, inhibit growth of a project?
The answers that are not answers that I listed follow (I'll annotate each of these to explain why they are not answers if it's not clear):
1) Argue semantics with something like "Well, Apple's Darwin is Free Software, and so was FreeBSD, so they're both the Free Software version".
- This decides to word-play with the definition of "Free Software version" instead of answering, despite it not being relevant to the question in the context of the thread. Essentially, it's a smart-ass response. If you honestly felt you didn't understand what the question in context of the thread was asking for, I'll apply the context for you and phrase it as such: "can you think of a /relicensed/ fork that turned out well for the project that permitted the relicensed fork?".
- Now you see, this again leaves it open to a smart-ass response: "Yes, I can think of one". However, arguing like this is pointless, evasive, and childish, which is why people generally won't put up with it. The meaning of the question is understood, and it waits to be answered.
2) Argue misdirection with something like "Well, Konqueror was GPL, but by publishing changes as part of a huge blob with no comments, it was effectively a 'destructive' fork too by your standards".
- This is an answer to a different question, as if there was any destructive behavior it was not due to relicensing, as it was not relicensed. The question was about relicensed forks. Changing the subject is not a valid way to answer a question.
3) Argue the wrong question with something like "Well, x.org and XFree86 are effectively related by a relicensed fork, and the GPL-compatible version is doing great".
- x.org was not a relicensed fork of XFree86, so also has nothing to do with the question.
> Good to see that you enjoy arguing with yourself.
I'm still waiting for you to respond with an answer. By your evasiveness, I take it you can't justify your position and are uncomfortable with challenging your own beliefs.
The bar is intentionally set low - a single, significant counter-example. Surely if relicensed forks do not inhibit the growth of projects that allow them, it should be easy to come up with significant counter-examples of such relicensed forks. If not, then it would seem they do inhibit, and as such, the BSD license does inhibit.
I'm still waiting for you to respond with an answer. By your evasiveness, I take it you can't justify your position and are uncomfortable with challenging your own beliefs.
The bar is intentionally set low - a single, significant counter-example. Surely if relicensed forks do not inhibit the growth of projects that allow them, it should be easy to come up with significant counter-examples of such relicensed forks. If not, then it would seem they do inhibit, and as such, the BSD license does inhibit.
swbrown: Darwin hasn't had a destructive effect on the BSD's. Sure, the BSD noosphere is smaller than Linux's, and that is caused in part by the BSD license. But that is unrelated to Apple forking BSD to create Darwin.
>I'm still waiting for you to respond with an answer.
And I'm still waiting for you to don a tutu and do a little jig for the lions at the zoo.
And I'm still waiting for you to don a tutu and do a little jig for the lions at the zoo.
> I did not eliminate answers I do not agree with, I eliminated answers that are not answers at all.
You can repeat that all day long, and it still translates to "answers I don't agree with". Whether you're willing to recognize that or not is immaterial.
If you want to have a debate with another person, you don't get to set the terms they're going to use. You can try to negotiate terms beforehand, but you can't set them unilaterally.
You can repeat that all day long, and it still translates to "answers I don't agree with". Whether you're willing to recognize that or not is immaterial.
If you want to have a debate with another person, you don't get to set the terms they're going to use. You can try to negotiate terms beforehand, but you can't set them unilaterally.
jdixon -
>If you want to have a debate with another person
It's worse than that. Not only does he want to set my arguments for me, but he insists that I should support a claim that I never made.
Which is why I think it's reasonable for me to ask that he don the tutu...
>If you want to have a debate with another person
It's worse than that. Not only does he want to set my arguments for me, but he insists that I should support a claim that I never made.
Which is why I think it's reasonable for me to ask that he don the tutu...
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

I would really say that without commercial companies we can "kiss FOSS final days goodbye".