Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thomas Dineen <tdineen@ix.netcom.com>
Cc: nickrob@snap.net.nz, fche@redhat.com, gdb@sourceware.org
Subject: Re: New MI maintainer
Date: Fri, 22 Feb 2008 22:09:00 -0000	[thread overview]
Message-ID: <ur6f4ivvy.fsf@gnu.org> (raw)
In-Reply-To: <47BF0478.1050209@ix.netcom.com> (message from Thomas Dineen on 	Fri, 22 Feb 2008 09:20:56 -0800)

> 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.

>    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.


  reply	other threads:[~2008-02-22 20:23 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 [this message]
2008-02-22 22:14                   ` Christopher Faylor
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=ur6f4ivvy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=fche@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    --cc=tdineen@ix.netcom.com \
    /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