Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: Daniel Jacobowitz <drow@false.org>,
	gdb@sourceware.org, 	Richard Stallman <rms@gnu.org>
Subject: Re: New MI maintainer
Date: Fri, 22 Feb 2008 04:08:00 -0000	[thread overview]
Message-ID: <18366.17038.2332.220976@kahikatea.snap.net.nz> (raw)
In-Reply-To: <47BDCA93.2040404@earthlink.net>

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

I have certainly done myself no favours and did not intend to so.  However, to
not allow the suggestion of a conflict of interest would certainly provide
cover for those who wish to abuse positions of trust.  Others, can presumably
decide for themselves whether those suggestions have validity or not.

 > while I don't myself expect an apology, you should think more about your 
 > goals and how you are most likely to achieve them.

It looks like I won't be able to achieve them so I should probably set
new goals.

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

No, but for Daniel alone, to just announce out of the blue that Vladimir is
now MI maintainer, you must admit, comes over as a bit of a stitch up.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-02-22  3:34 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
2008-02-22  4:08     ` Nick Roberts [this message]
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=18366.17038.2332.220976@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=rms@gnu.org \
    --cc=stanshebs@earthlink.net \
    /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