From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16553 invoked by alias); 19 Feb 2003 15:43:00 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16544 invoked from network); 19 Feb 2003 15:43:00 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 19 Feb 2003 15:43:00 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 34CFB2E9D; Wed, 19 Feb 2003 10:47:46 -0500 (EST) Message-ID: <3E53A722.2030801@redhat.com> Date: Wed, 19 Feb 2003 15:43:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joel Brobecker Cc: Elena Zannoni , gdb@sources.redhat.com Subject: Re: [maint] The GDB maintenance process References: <20030217180709.GA19866@nevyn.them.org> <20030218042847.50F2E3CE5@localhost.redhat.com> <20030217180709.GA19866@nevyn.them.org> <20030218023553.2BBB73D02@localhost.redhat.com> <20030217180709.GA19866@nevyn.them.org> <15953.20132.193102.752916@localhost.redhat.com> <20030219014904.GA11446@nevyn.them.org> <20030219022636.GJ2105@gnat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00347.txt.bz2 > With my modest experience on the GDB project, and without any experience > on any other GNU project like this, it's difficult to make any > recommendation. My feeling is that we could try relaxing a bit the > rules, and allow global maintainers to approves changes if the > associated maintainer is unable to review them in say, a few (couple?) > of weeks. Fernando does this already. He also sends out e-mail saying he is off line for a bit (he is down the hall from me which is an advantage). Other maintainers do not, sigh! More of a concern is that repeated pings often result in radio silence. I don't think having a global maintainer step in after N weeks will really help. It just butters over what may be a more serious underlying problem. Andrew