1 |
<grumble> I promised myself I'd stay the heck out of this one...but I just |
2 |
can't let Jon's comment slide unrebutted, and so I'll somment on Drake's |
3 |
message while I'm here. |
4 |
|
5 |
On Sun, Feb 22, 2004 at 04:33:03PM -0500, Jon Portnoy wrote: |
6 |
> On Sun, Feb 22, 2004 at 12:50:34PM -0800, Drake Wyrm wrote: |
7 |
> > The problem is that the XFree license and the GPL are now |
8 |
> > incompatible. For smooth progression of overall Linux development, one |
9 |
> > of these licenses must now change. This does not necessarily imply that |
10 |
> > the one which changed most recently needs to change back. So much focus |
11 |
> > has been applied to the "offending" portion of the new XFree license; |
12 |
> > perhaps we should lend the same critical eye to our beloved GPL. One |
13 |
> > possible analogy for the situation is that the XFree license demonstrated |
14 |
> > a bug in the GPL. |
15 |
|
16 |
I've been arguing for over a decade that the GPL is buggy. Its deliberate |
17 |
incompatibility with other open source licenses is one symptom of that. |
18 |
|
19 |
> I think it's perfectly reasonable for a license to insist on people not |
20 |
> placing further restrictions on the code. This is what prevents people |
21 |
> from making free software nonfree. |
22 |
|
23 |
NO!!! |
24 |
|
25 |
You CANNOT make existing freely available software non-freely-available. |
26 |
Period. It cannot be done. Copyright laws will not allow it. Regardless of |
27 |
what anyone does with a piece of code, no matter what license itt's under, |
28 |
that code cannot be made other than freely available. Non-viral licenses |
29 |
allow people to make THEIR OWN WORK other than freely available, but this is |
30 |
exactly as it should be. |
31 |
|
32 |
> The BSD license approach is not at all intended to keep free software |
33 |
> free; |
34 |
|
35 |
Wrong. If this were not the case, we wouldn't have the BSDs today. Sun would |
36 |
have made them proprietary a long time ago. |
37 |
|
38 |
> it's intended to let people create proprietary software using free |
39 |
> software code. |
40 |
|
41 |
Thus guaranteeing the maximum freedom for everyone. This is the true spirit |
42 |
of free software, and why I think the FSF has it all wrong - and is being |
43 |
intellectually dishonest in calling their position "free". |
44 |
|
45 |
> What you're actually suggesting is reforming the way the entire free |
46 |
> software community feels about freedom and licensing. |
47 |
|
48 |
Speak for yourself, pilgrim. |
49 |
|
50 |
> Have you really thought this through? |
51 |
|
52 |
More than the frothing Stallmanites have. |
53 |
|
54 |
> Basically you're stating that it should be acceptable to place |
55 |
> proprietary restrictions on what was at one point free software. |
56 |
|
57 |
No, he's not, because you cannot change the restrictions under which a piece |
58 |
of code is available. You can place additional restrictions on your code, |
59 |
but the original code is now and forever available under the same terms as |
60 |
it was when the proprietary fork was taken. |
61 |
|
62 |
> If people wanted their code to be treated that way, they wouldn't license |
63 |
> it under the GPL. |
64 |
|
65 |
Some folks don't have any choice. |
66 |
Further, there are LOTS of folks out there that hold the same wrong belief |
67 |
you do, and choose the GPL in light of that error. |
68 |
|
69 |
> Nobody's forcing anybody to put their code under one |
70 |
> license or another. |
71 |
|
72 |
It is the explicit aim of the GPL to have all software, everywhere, under |
73 |
any conditions, licensed under their anticommercial terms. |
74 |
|
75 |
> I would not use a license that allows additional restrictions for most of |
76 |
> what I do; I only license relatively trivial things under BSD-style |
77 |
> licenses. |
78 |
|
79 |
That is your prerogative. However, if you base that on the erroneous belief |
80 |
that someone could take that software and make it no longer freely |
81 |
available, I suggest you reexamine your position. |
82 |
|
83 |
> > One solution to the issue would be inclusion in the GPL of one or |
84 |
> > more optional clauses. Much in the same way that "front cover" and |
85 |
> > "back cover" texts may be included in a GPLed package, one could use a |
86 |
> > "GPL+attribution" license. Such a license would be compatible with the |
87 |
> > new XFree license. |
88 |
|
89 |
I stroongly doubt this will happen. RMS is so convinced of the holiness of |
90 |
his True Cause that any concession to the real world is anathema. |
91 |
|
92 |
-- |
93 |
gentoo-dev@g.o mailing list |