From: Elefterios Stamatogiannakis <estama@dblab.ece.ntua.gr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005
Date: Fri, 18 Feb 2005 13:05:57 +0200 [thread overview]
Message-ID: <4215CC15.5020701@dblab.ece.ntua.gr> (raw)
In-Reply-To: <1108700993.18898.119.camel@aragorn>
I prefer to stay out of threads like this, but (see below)
John R. Hogerhuis wrote:
> Fabrice,
>
> I've followed this project for a while, and though I'm not surprised the
> zealots are coming out of the woodwork, I am surprised by the vehemence
> of some of the long time users.
>
Your use of words like "zealots" and "woodwork" reminds me of trolls.
These words are certainly not used in a civilized conversation. Keep in
mind that some of the "zealots" have put a lot of work on qemu.
I'm not going to address the rest of your mail. I find it insulting
(conspiracy theories?).
I'll just put my 2 cents.
First the problem:
Other people take qemu and make money on it with little to no benefit
to the people that created it - advanced it.
Solutions:
1. Fabrice's way. Make a part of it proprietary.
Pros::
(Fabrice) When some company wants to sell this highly beneficial module
they have to pay him.
Cons::
(Fabrice): Otherwise HE has to sue them.
(community): It divides the community.
2. Pure GPL it.
Pros::
(community): That way when some company wants to sell this highly
beneficial module they have to give the changes (if any) back to the
community.
(community): Otherwise contact FSF and it will sue them. The community
protects us.
(community): It doesn't divide the community.
Cons::
(Fabrice): No immediate monetary benefit.
3. Double license it.
Both of the above apply.
Personally i would prefer 2 or 3. They benefit the community more.
Nevertheless fabrice has the right to do what is best for him. I don't
have hard feelings about that. I also understand people like Jean-Michel
Poure (a little kneejerk reaction but i'm ok with it).
prev parent reply other threads:[~2005-02-18 11:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 9:18 [Qemu-devel] FreeOSZoo will stop March 1, 2005 Jean-Michel POURE
2005-02-12 10:15 ` Magnus Damm
2005-02-12 10:18 ` Brad Campbell
2005-02-12 12:19 ` Antti-Juhani Kaijanaho
2005-02-12 12:20 ` Daniel Egger
2005-02-12 13:42 ` Brad Campbell
2005-02-12 16:15 ` Daniel Egger
2005-02-12 17:00 ` Fabrice Bellard
2005-02-12 18:11 ` Jernej Simončič
2005-02-12 21:18 ` Daniel Egger
2005-02-12 23:01 ` Darrin Ritter
2005-02-13 0:06 ` Jernej Simončič
2005-02-13 11:28 ` Daniel Egger
2005-02-13 17:01 ` Jim C. Brown
2005-02-13 17:40 ` [Qemu-devel] Plex86 and Qemu jeebs
2005-02-13 18:27 ` Jim C. Brown
2005-02-13 19:35 ` jeebs
2005-02-13 22:06 ` Jim C. Brown
2005-02-13 23:20 ` jeebs
2005-02-14 0:05 ` [Qemu-devel] coLinux and Qemu? --was-- " Darryl Dixon
2005-02-14 0:37 ` Jim C. Brown
2005-02-14 0:58 ` Mark Williamson
2005-02-14 0:34 ` [Qemu-devel] " Jim C. Brown
2005-02-14 10:39 ` Andreas Bollhalder
2005-02-13 22:18 ` Adrian Smarzewski
2005-02-13 23:04 ` Martin Koniczek
2005-02-14 14:18 ` Phil Krylov
2005-02-15 23:32 ` Old version support. Was: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005 Gregory Alexander
2005-02-16 18:51 ` Fabrice Bellard
2005-02-13 0:18 ` Jim C. Brown
2005-02-13 4:42 ` James Mastros
2005-02-13 5:26 ` Jim C. Brown
2005-02-13 6:21 ` James Mastros
2005-02-13 10:02 ` Darryl Dixon
2005-02-13 16:53 ` Jim C. Brown
2005-02-13 13:32 ` [Qemu-devel] " Robert Wittams
2005-02-12 22:41 ` [Qemu-devel] " Grzegorz Kulewski
2005-02-17 21:53 ` Herbert Poetzl
2005-02-17 22:18 ` Grzegorz Kulewski
2005-02-17 23:25 ` Fabrice Bellard
2005-02-18 4:29 ` John R. Hogerhuis
2005-02-18 8:23 ` Asko Kauppi
2005-02-18 11:05 ` Elefterios Stamatogiannakis [this message]
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=4215CC15.5020701@dblab.ece.ntua.gr \
--to=estama@dblab.ece.ntua.gr \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).