From: Stan Shebs <stanshebs@earthlink.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb@sourceware.org, Richard Stallman <rms@gnu.org>
Subject: Re: New MI maintainer
Date: Thu, 21 Feb 2008 19:25:00 -0000 [thread overview]
Message-ID: <47BDCA93.2040404@earthlink.net> (raw)
In-Reply-To: <18363.14758.855327.355215@kahikatea.snap.net.nz>
Nick Roberts wrote:
> 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.
>
One of the qualities we look for in a maintainer is the ability to keep
a level head, and to tone down the flames rather than escalate when the
situation is difficult. As we know from bitter experience, technical
ability and knowledge is not sufficient. Nick, this kind of accusation
is precisely the sort of thing that we want to keep out of the GDB
development process - if there were fencesitters on the issue before
now, do you think that your public insinuation of bad faith and
incompetence is going to cause them to regard you more favorably? So
while I don't myself expect an apology, you should think more about your
goals and how you are most likely to achieve them.
As for the decision process not being open, I note that almost nobody
volunteers to have their job performance reviews and salary history be
put out in public. But if a wouldbe maintainer were to do that, I
suggest that the SC have the discussion about that person in public as well.
Stan
next prev parent reply other threads:[~2008-02-21 19:02 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
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 [this message]
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=47BDCA93.2040404@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
--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