Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Alpár Jüttner" <alpar@cs.elte.hu>
To: Dave Korn <dave.korn@artimi.com>
Cc: gdb@sourceware.org
Subject: RE: New MI maintainer
Date: Sat, 23 Feb 2008 00:58:00 -0000	[thread overview]
Message-ID: <1203724876.4440.70.camel@piko.site> (raw)
In-Reply-To: <007a01c875ab$aae85770$2e08a8c0@CAM.ARTIMI.COM>

I think, the real issue is not the openness of the project management,
but this:

> Given that I have made significant contributions
> to GDB/MI over a long period of time then it would then seem appropriate to at
> least e-mail me off-list before the announcement to inform me of your
> intention.

As far as I see, nobody has commented on this sentence of Nick. I think
it would be worth doing that, at least before blaming him and saying
that a global maintainer must have a higher level of ability of being
able to avoid heated personal debates.

As a complete outsider, my feeling is that if Nick had really been
considered as a valuable and important member of the community rather
than someone who should be "outmaneuvered", then exactly the same
decision would have been communicated toward him in a much more friendly
way.

Although Nick's responses in this thread are offensive and his
statements may even be false, I understand his bad feeling and I must
say it - at least partially - justifies his reactions.

Some people expected an apology in this thread but nobody seemed to be
thinking about whether he should apologize. More than one person made a
mistake in this awkward story. I strongly believe that a frank 'sorry'
from the one who made the first one would be followed by others.

After all, this is a great community of great people. With no exception.

All the best,
Alpar





  reply	other threads:[~2008-02-23  0:01 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
2008-02-22 22:23                     ` Bob Rossi
2008-02-23  0:01                       ` Dave Korn
2008-02-23  0:58                         ` Alpár Jüttner [this message]
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=1203724876.4440.70.camel@piko.site \
    --to=alpar@cs.elte.hu \
    --cc=dave.korn@artimi.com \
    --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