From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24086 invoked by alias); 19 Nov 2005 10:54:30 -0000 Received: (qmail 24007 invoked by uid 22791); 19 Nov 2005 10:54:27 -0000 Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 19 Nov 2005 10:54:27 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-251-47.inter.net.il [83.130.251.47]) by nitzan.inter.net.il (MOS 3.6.5-GR) with ESMTP id BZA72374 (AUTH halo1); Sat, 19 Nov 2005 12:54:16 +0200 (IST) Date: Sat, 19 Nov 2005 10:54:00 -0000 Message-Id: From: Eli Zaretskii To: Jim Blandy CC: gdb@sourceware.org In-reply-to: <8f2776cb0511181634g34f855ddw1f54a76930ecf373@mail.gmail.com> (message from Jim Blandy on Fri, 18 Nov 2005 16:34:33 -0800) Subject: Re: Maintainer policy for GDB Reply-to: Eli Zaretskii References: <20051117140353.GA11432@nevyn.them.org> <20051118030711.GB31581@nevyn.them.org> <20051118152618.GB9100@nevyn.them.org> <20051118185135.GA13986@nevyn.them.org> <8f2776cb0511181351k6aba28f7m5223956e4f84f46@mail.gmail.com> <8f2776cb0511181634g34f855ddw1f54a76930ecf373@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00423.txt.bz2 > Date: Fri, 18 Nov 2005 16:34:33 -0800 > From: Jim Blandy > Cc: gdb@sourceware.org > > I would agree that it's unfair to give someone a responsibility > without giving them the power to carry it out. If we're doing that > here, then we're making a mistake. I most passionately agree, but I'm not sure everybody else shares our agreement. > But I don't think it's a good idea to grant exclusive authority as a > reward for accepting responsibility. I think contributors should earn > authority informally, through their contributions and their > participation in discussions. If you work steadily, explain yourself > well, and are easy to work with, then your words will carry weight > that no set of rules could give them. That is the sort of "position" > that we should offer our contributors to aspire to. Then why not give them the responsibility at the same time as we grant the authority, and through the same informal process? Under the proposed rules, nothing is lost by not having responsible maintainers, anyway. > Official authority to make decisions should be restricted to people > who have accumulated a track record of making good ones, and being > easy to work with. Those should be the only criteria. Until now, the criteria for granting this authority were not spelled out, and IIRC there was never a formal discussion whether a particular candidate satisfied those criteria. And the new rules don't propose any formal procedure for this, either. So we have no way of knowing whether the criteria you mention above (to which I think I agree) are met in each individual case. For example, some of you might think that I fail the second requirement, of being easy to work with; and yet here I am, being responsible and solely authorized for maintaining the GDB documentation. > Setting principle aside, in practice, our current rules --- > specifically that only area maintainers may approve changes to their > areas --- make exactly the tie between responsibility and authority > that you're suggesting. And that policy is a problem spot. It's a different problem, though: some area maintainers are slow in their response. When the response time is short, there are no problems whatsoever. I think we should look for rules that improve on the current situation without introducing new problems.