From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Fri, 22 Feb 2008 22:14:00 -0000 [thread overview]
Message-ID: <20080222220927.GA21434@ednor.casa.cgf.cx> (raw)
In-Reply-To: <ur6f4ivvy.fsf@gnu.org>
On Fri, Feb 22, 2008 at 10:22:41PM +0200, Eli Zaretskii wrote:
>> Date: Fri, 22 Feb 2008 09:20:56 -0800
>> From: Thomas Dineen <tdineen@ix.netcom.com>
>> CC: "Frank Ch. Eigler" <fche@redhat.com>, gdb@sourceware.org
>>
>> Gentle People:
>>
>> Yes but with the conditions listed below:
>>
>> "robustly constructed and justified"
>>
>> any contributor can easily be blown off for
>> any political reason!
>
>While theoretically possible, I'm quite sure such conspiracies can
>never happen in practice in this case, since the people involved come
>from several different continents, cultural backgrounds, and political
>views. In fact, just reaching an agreement is sometimes a formidable
>job for us.
Yes! What seems to be getting lost is the fact that all of the
development of gdb IS *very* open. When someone submits a patch,
everyone gets to see it and everyone gets to see any technical
objections. How long would the project last if there were hidden
agendas behind every communication?
(Well, ok, experience has shown that it could last several years
like that but still, it's not like that *now*)
>>From my observations the attitudes expressed in this thread are NOT
>>positive for the Open Source Movement. I would suggest that your
>>movement would benefit from more openness and democracy.
>
>Sorry, but that's pure demagoguery. "Open Source" and "Free Software"
>mean that the sources are available. They don't mean that every aspect
>of human life is open to the public. Even the most open democracies
>always have closed deliberations about certain issues. You cannot lead
>a group in any significant human endeavor without a certain distance
>between the leadership and the rest, and without closed deliberations
>about some sensitive issues.
Amen.
It's interesting how often people try to tack on bigger concerns to the
simple concept of Free Software. Free Software isn't supposed to be
solving global warming and it isn't supposed to be a demonstration of a
New World Order with feel-good cum ba yah. It's just a guarantee that
you get the source code for the software that you're using.
Managing any project where people are involved means that sometimes the
people in charge have to have frank, private conversations. The
alternative, as Stan Shebs, notes is to essentially do performance
reviews in the open.
Some projects *do* work that way but they are hardly bastions of
civilized discourse.
cgf
next prev parent reply other threads:[~2008-02-22 22:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 19:37 Daniel Jacobowitz
2008-02-19 20:29 ` Nick Roberts
2008-02-19 20:46 ` Daniel Jacobowitz
2008-02-19 20:47 ` Nick Roberts
2008-02-21 1:43 ` Daniel Jacobowitz
2008-02-20 3:12 ` Bob Rossi
2008-02-20 8:59 ` Richard Stallman
2008-02-21 21:37 ` Bob Rossi
2008-02-20 19:05 ` Richard Stallman
2008-02-20 20:00 ` Nick Roberts
2008-02-20 20:57 ` Eli Zaretskii
2008-02-20 21:20 ` Nick Roberts
2008-02-20 21:50 ` Joel Brobecker
2008-02-20 23:25 ` Frank Ch. Eigler
2008-02-22 3:34 ` Nick Roberts
2008-02-22 17:37 ` Thomas Dineen
2008-02-22 22:09 ` Eli Zaretskii
2008-02-22 22:14 ` Christopher Faylor [this message]
2008-02-22 22:23 ` Bob Rossi
2008-02-23 0:01 ` Dave Korn
2008-02-23 0:58 ` Alpár Jüttner
2008-02-23 8:16 ` Jim Blandy
2008-02-23 11:13 ` Nick Roberts
2008-02-23 11:15 ` Eli Zaretskii
2008-02-23 12:34 ` Eli Zaretskii
2008-02-22 23:36 ` Jim Blandy
2008-02-21 19:25 ` Stan Shebs
2008-02-22 4:08 ` Nick Roberts
2008-02-22 2:52 ` Bob Rossi
2008-02-22 8:43 ` Vladimir Prus
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=20080222220927.GA21434@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=gdb@sourceware.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