From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5122 invoked by alias); 22 Feb 2008 03:34:05 -0000 Received: (qmail 5109 invoked by uid 22791); 22 Feb 2008 03:34:04 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 22 Feb 2008 03:33:38 +0000 Received: from kahikatea.snap.net.nz (14.60.255.123.dynamic.snap.net.nz [123.255.60.14]) by viper.snap.net.nz (Postfix) with ESMTP id E72BD3DA5F5; Fri, 22 Feb 2008 16:33:35 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id AC0178FC6D; Fri, 22 Feb 2008 16:33:34 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18366.17038.2332.220976@kahikatea.snap.net.nz> Date: Fri, 22 Feb 2008 04:08:00 -0000 To: Stan Shebs Cc: Daniel Jacobowitz , gdb@sourceware.org, Richard Stallman Subject: Re: New MI maintainer In-Reply-To: <47BDCA93.2040404@earthlink.net> References: <20080219191222.GA10196@caradoc.them.org> <18363.14758.855327.355215@kahikatea.snap.net.nz> <47BDCA93.2040404@earthlink.net> X-Mailer: VM 7.19 under Emacs 22.1.90.4 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-02/txt/msg00176.txt.bz2 > 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