1 |
Niels Dettenbach (Syndicat.com) posted on Sat, 23 May 2015 08:39:36 +0200 |
2 |
as excerpted: |
3 |
|
4 |
> Some |
5 |
> of the very large mailers today still holding on postfix usually have |
6 |
> developed their own strongly modified and mostly („crapped") "version" |
7 |
> of it (more or less giggling around GPL barriers here) - this is not |
8 |
> THAT postfix anymore most people get with their linux distri. ß) |
9 |
|
10 |
FWIW on those GPL barriers... and with the usual "no lawyer here" |
11 |
disclaimer... |
12 |
|
13 |
It's worth noting the difference between the GPL and the AGPL, the latter |
14 |
of which considers usage of a server-based service to be distribution of |
15 |
that service, thereby triggering the traditional GPL sources distribution |
16 |
requirements. |
17 |
|
18 |
The GPL, by contrast, normally applies only locally, making the company |
19 |
doing the mods the only direct user, and they normally have access to the |
20 |
sources already, since they're either making the mods or commissioning |
21 |
them, themselves. |
22 |
|
23 |
Thus it is that many cloud-based services can legally avoid the otherwise |
24 |
restrictions of the GPL, because they are their own user and are not |
25 |
considered to be distributing. But the AGPL, unlike the GPL, never |
26 |
really developed a following of critical mass to create a self-sustaining |
27 |
ecosystem. |
28 |
|
29 |
So it isn't that these providers are giggling around the GPL |
30 |
restrictions. Those restrictions simply don't apply to the license |
31 |
chosen for the apps and libs they tend to use, and if they did, because |
32 |
the AGPL never developed that strong an ecosystem, it's always reasonably |
33 |
simple to simply go with a different "open source", or even "free |
34 |
software" alternative. |
35 |
|
36 |
-- |
37 |
Duncan - List replies preferred. No HTML msgs. |
38 |
"Every nonfree program has a lord, a master -- |
39 |
and if you use the program, he is your master." Richard Stallman |