1 |
> -----Original Message----- |
2 |
> From: lunarcrisis@×××××.com [mailto:lunarcrisis@×××××.com] On |
3 |
> Behalf Of Henk Boom |
4 |
> Sent: Tuesday, July 17, 2007 11:08 AM |
5 |
> To: gentoo-user@l.g.o |
6 |
> Subject: Re: [gentoo-user] 2 to 3?? |
7 |
> |
8 |
> |
9 |
> On 16/07/07, Volker Armin Hemmann |
10 |
> <volker.armin.hemmann@××××××××××××.de> wrote: |
11 |
> > because gplv3 removes freedom? |
12 |
> |
13 |
> As far as I remember from when I read it, it does not take |
14 |
> any freedoms which the previous versions did not intend to. |
15 |
> The purpose of the GPL is to protect the 4 freedoms. This |
16 |
> instalment just closes loopholes in the previous versions |
17 |
> which would allow these freedoms to be infringed upon. |
18 |
> |
19 |
> Henk Boom |
20 |
> -- |
21 |
|
22 |
The four freedoms: |
23 |
Freedom 0: The freedom to run a program for any purpose. |
24 |
Freedom 1: To study the way a program works, and adapt it to your needs. |
25 |
Freedom 2: To redistribute copies so that you can help your neighbors. |
26 |
Freedom 3: Improve the program, and release your improvements to |
27 |
the public, so that the whole community benefits. |
28 |
For freedom 1 and 3 to work, the code must be open. |
29 |
|
30 |
Freedom 1 is just as important as the other three. Freedom one is |
31 |
almost eliminated in GPLv3. Freedom One is the freedom that was |
32 |
most whole heartedly expressed in the original manifesto. |
33 |
|
34 |
Freedom 3 is the one that GPLv3 is making most important now. |
35 |
It does so to the detriment of the other three. |
36 |
|
37 |
The old GPL licenses say that if you use the code in a public way, |
38 |
you have to make the code you use available changes and all. That |
39 |
deals with software and only software. Stallman used to be so set |
40 |
on THAT mindset (software vs. hardware), that he was in favor of |
41 |
those groups that didn't want to make the source code of every ROM |
42 |
chip they made open to the world, on the grounds that certain parts |
43 |
of firmware are so tied to the hardware as to be indistinguishable. |
44 |
|
45 |
GPLV3 says, if you want to use code in a public way, you have |
46 |
to crack open your box so that people can play with it however |
47 |
they want, and then that potentially compromised box still has |
48 |
to be able to connect to your network if it connected in it's |
49 |
unmodified form. That very much deals with the hardware. |
50 |
|
51 |
Under the spirit of the GPL, one could take code and use what |
52 |
they could. They still had to have the technical capabilities |
53 |
to use that code, and understand the platform it was on. |
54 |
|
55 |
Under the new version, if you don't understand the code, then |
56 |
something must be wrong with the code. If the code is full of |
57 |
machine dependant features that cannot compile on another type |
58 |
of machine, then something must be wrong with the code. Oh, and |
59 |
these strange assumptions only apply if you are making money off |
60 |
of the machine that the code was written for. Otherwise no one |
61 |
will ever notice so they don't care. |
62 |
|
63 |
Free Software is about Freedom. GPLv3 is about religion. You |
64 |
are free as long as you do things our way. |
65 |
|
66 |
That is why I shy away from the GPL licenses. I like the |
67 |
LGPLv2, but GPLv3 is kind of scary. I want code that I make |
68 |
free to be free. :P I don't want to say, "It is free if you |
69 |
are a broke penniless college kid that plans to stay that way." |
70 |
|
71 |
LGPLv2 allows wide use of code, without heavy demands. |
72 |
|
73 |
If I by some miracle produce a chunk of code that propels another |
74 |
entity to the top of their industry, then I have achieved something |
75 |
Whether I get anything in return from them or not. If they |
76 |
are able to take what I have produced and make it useful, then |
77 |
more power too them. If they give back to the community in the |
78 |
form of code, cash, or even morale support, then that is them |
79 |
playing the game by our rules. It is good for us and will help |
80 |
them in the long run. |
81 |
|
82 |
Even if they don't give back code or cash or a pat on the back, |
83 |
if they simply say where the code came from, that will help the |
84 |
community. |
85 |
-- |
86 |
gentoo-user@g.o mailing list |