From: Federico Ferreres <fferreres@ojf.com>
To: David Schwartz <davids@webmaster.com>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: Funding GPL projects or funding the GPL?
Date: 03 Aug 2002 19:55:51 -0300 [thread overview]
Message-ID: <1028415361.431.80.camel@fede> (raw)
In-Reply-To: <20020803205750.AAA16052@shell.webmaster.com@whenever>
> Our General Public Licenses are designed to make sure that you
> have the freedom to distribute copies of free software (and charge for
> this service if you wish), that you receive source code or can get it
> if you want it, that you can change the software or use pieces of it
> in new free programs; and that you know you can do these things.
That is fantastic, unless what you need is not beign developed and
supported. In these cases, the GPL effectively prevents the software
from beign developed and funded.
Suppose Adobe wants to GPL Photoshop. They need funds to keep improving
it, patenting stuff so that other don't abuse their ideas (imagine those
patents under a General Public Patent License). The designers want to
have a Photoshop. But Adobe will have no way to charge for it, except by
redistributing it. But who want's to pay for a Photoshop CD or download
from Adobe when you'll have it bundled in your RedHat (or favorite)
distro? So Adobe doesn't want to GPL it, GIMP doesn't get enough funds
to improve it faster and the designed end up having to use a lower
quality product (GIMP) or having to pay for Windows and Photoshop.
The GPL effectively help the distribution of software but not the
developement of software. The fGPL helps developement of software and
doesn't harm redistribution.
But I do not expect any developer that's getting paid by a distribution,
the goverments or a big company to agree with me. Any other developer
that's _trully_ independant (from distributors, universities, tax and
big corps money), did a great contribution for OSS and can't get the
funds to keep on working, should agree.
Federico
next prev parent reply other threads:[~2002-08-03 22:56 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 16:09 Funding GPL projects or funding the GPL? Federico Ferreres
2002-07-26 16:15 ` Robinson Maureira Castillo
2002-07-26 19:39 ` Federico Ferreres
2002-07-26 19:48 ` Robinson Maureira Castillo
2002-07-26 19:56 ` Cort Dougan
2002-07-26 20:07 ` Robinson Maureira Castillo
2002-07-26 20:53 ` Federico Ferreres
2002-07-26 20:08 ` Andrew Rodland
[not found] ` <1027714314.906.56.camel@fede>
2002-07-26 20:15 ` Federico Ferreres
2002-07-26 21:23 ` Alexander Viro
2002-07-26 16:46 ` Rob Landley
2002-07-27 0:03 ` Federico Ferreres
2002-07-27 3:02 ` Gerhard Mack
2002-07-27 5:10 ` Federico Ferreres
2002-07-27 5:34 ` Alexander Viro
2002-07-27 5:51 ` Federico Ferreres
2002-07-27 6:29 ` Alexander Viro
2002-07-27 7:23 ` Federico Ferreres
2002-07-27 15:42 ` Rik van Riel
2002-07-27 15:59 ` Larry McVoy
2002-07-27 16:06 ` Rik van Riel
2002-07-27 16:22 ` Larry McVoy
2002-07-27 17:46 ` Roger Larsson
2002-07-27 19:49 ` Keith Adamson
2002-07-28 1:32 ` Daniel Mose
2002-07-28 5:21 ` Alexander Viro
2002-07-28 5:32 ` Larry McVoy
2002-07-28 9:16 ` Federico Ferreres
2002-07-28 10:35 ` Alexander Viro
2002-07-28 15:02 ` Federico Ferreres
2002-07-29 7:39 ` Hans Reiser
2002-07-29 9:07 ` Federico Ferreres
2002-07-29 13:11 ` Hans Reiser
2002-07-29 16:53 ` Federico Ferreres
2002-08-01 19:16 ` Thunder from the hill
2002-07-29 19:47 ` Eric W. Biederman
2002-07-29 20:55 ` Hans Reiser
2002-07-30 15:12 ` Gilad Ben-Yossef
2002-07-30 16:26 ` Jesse Pollard
2002-07-30 16:07 ` Alexander Viro
2002-07-30 18:22 ` Hans Reiser
2002-07-30 19:11 ` Gerhard Mack
2002-07-30 19:29 ` Alexander Viro
2002-07-30 19:42 ` Hans Reiser
2002-07-30 20:03 ` Richard B. Johnson
2002-07-28 14:20 ` Rik van Riel
2002-07-29 7:19 ` Hans Reiser
[not found] ` <20020801162716.B27939@work.bitmover.com>
2002-08-02 1:15 ` Hans Reiser
2002-07-27 21:44 ` Federico Ferreres
2002-07-27 7:44 ` Federico Ferreres
[not found] ` <20020730222018.GA17860@elf.ucw.cz>
2002-08-02 4:29 ` Federico Ferreres
2002-08-02 7:55 ` Pavel Machek
2002-08-03 20:57 ` David Schwartz
2002-08-03 22:55 ` Federico Ferreres [this message]
2002-07-27 20:10 ` Paul P Komkoff Jr
2002-07-31 20:03 ` Bill Davidsen
2002-08-01 9:32 ` David Schwartz
2002-08-01 13:48 ` Alan Cox
2002-08-01 16:51 ` Gerhard Mack
2002-08-01 20:17 ` David Schwartz
2002-08-02 8:46 ` Kai Henningsen
2002-08-03 21:04 ` David Schwartz
2002-08-01 21:56 ` David Schwartz
2002-08-01 18:41 ` Bill Davidsen
2002-08-01 20:24 ` David Schwartz
2002-08-01 20:52 ` Alexander Viro
2002-08-01 18:42 ` Funding Linux kernel -fringe and -future devel. projects ? Daniel Mose
2002-08-01 20:26 ` Mark Hahn
2002-07-29 11:48 ` Funding GPL projects or funding the GPL? Thunder from the hill
2002-07-26 16:42 ` Larry McVoy
2002-07-26 17:01 ` Alexander Viro
2002-07-26 17:07 ` Larry McVoy
2002-07-26 17:08 ` Cort Dougan
2002-07-26 17:18 ` Larry McVoy
2002-07-26 17:14 ` Cort Dougan
2002-07-26 20:03 ` Federico Ferreres
2002-07-26 20:29 ` Jon Portnoy
2002-07-26 20:43 ` Federico Ferreres
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 11:20 Samium Gromoff
2002-07-29 18:43 ` Eric W. Biederman
2002-07-29 17:00 Federico Ferreres
2002-07-30 6:05 Samium Gromoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1028415361.431.80.camel@fede \
--to=fferreres@ojf.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox