From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org, Richard Stallman <rms@gnu.org>
Subject: Re: New MI maintainer
Date: Tue, 19 Feb 2008 20:47:00 -0000 [thread overview]
Message-ID: <18363.16396.16628.619030@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080219202853.GA14588@caradoc.them.org>
> > I must say I'm surprised by this appointment for several reasons. When I
> > offered to act as maintainer, a year or so ago, although I had Eli's
> > support and other's endorsed it off-list, e.g., Alain Magloire, my offer
> > was declined.
>
> Yes. The global maintainers have been discussing the problem of MI
> maintenance for at least that long. I was hoping to leave this out of
> the announcement, but the consensus of that group was that you were
> not a suitable choice for a GDB maintainer. Part of the delay was our
> hope that the situation would improve.
Apart from Eli's support I had no feedback from that offer so clearly I
don't understand what that means.
> > The process behind these decisions is not open to me but it doesn't escape
> > my attention that Vladimir is now part of CodeSourcery, and that
> > CodeSourcery have at least one contract (with Ericsson) to work on Eclipse
> > which uses GDB/MI in its DSF plugin. I ask myself in whose interest this
> > appointment is made. It's certainly not the GNU project or the FSF.
>
> I expect an apology from you for this offensive statement. I am the
> only member of the GDB steering committee working at CodeSourcery, and
> the SC is a group of GDB contributors, not some sort of sock puppet.
> The decision was made solely based on the interests of GDB in our best
> judgement.
I don't want to escalate the invective but I don't really see why I should
apologise for my perceptions. If, as you say, the decision was carefully
discussed, it would not have escaped the global maintainers attention that I
was interested in the role. 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.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-02-19 20:46 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 [this message]
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
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=18363.16396.16628.619030@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rms@gnu.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