From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36749 invoked by alias); 14 Nov 2019 22:02:14 -0000 Mailing-List: contact libstdc++-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libstdc++-owner@gcc.gnu.org Received: (qmail 36738 invoked by uid 89); 14 Nov 2019 22:02:13 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=asap, H*MI:sk:ae462be, H*i:sk:ae462be, H*f:sk:ae462be X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-2.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 14 Nov 2019 22:02:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573768931; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=49/3spZS0jqsXtRFVT8l1UWmRS9RBMi7x/wGwkIwO94=; b=AkcCAdDJwws8CCD+HF1+H7c5H9iIUeAHzait7PydCAV5jUWOi9V6kCVinh6HpyuJbVLTSY /XLC1zEw8+DDtb2a08I3+cllfadiOcUD9tYehtbDeW5cBIiWVyheM2BUwqZI1RJJnBam1H opOiw8n1rNma3rQ3ve+xolnueRCDYWI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-299--JuTY4diNemwOUnfetuO7w-1; Thu, 14 Nov 2019 17:02:08 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D7C93100726B; Thu, 14 Nov 2019 22:02:06 +0000 (UTC) Received: from localhost (ovpn-116-223.phx2.redhat.com [10.3.116.223]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6E99D10A3932; Thu, 14 Nov 2019 22:02:06 +0000 (UTC) Date: Thu, 14 Nov 2019 22:02:00 -0000 From: Jonathan Wakely To: =?iso-8859-1?Q?Fran=E7ois?= Dumont Cc: "libstdc++@gcc.gnu.org" Subject: Re: Request for extended maintainers rights Message-ID: <20191114215548.GK17072@redhat.com> References: MIME-Version: 1.0 In-Reply-To: X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.12.1 (2019-06-15) X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00029.txt.bz2 On 14/11/19 22:01 +0100, Fran=E7ois Dumont wrote: >Hi > >=A0=A0=A0 With 4 official Maintainers but only 1 dealing with patch reques= ts=20 >who is moreover dealing with a lot of other tasks I fear that=20 >libstdc++ becomes really unattractive for occasional contributors. As I've said to other people in the past, anybody can review patches. One of the key responsibilities for maintainers is reviewing other people's patches, and anybody can do that whether they're a maintainer or not. There wouldn't be such a backlog if more people helped by reviewing patches (not approving them, because only maintainers can do that, but just saying "I've reviewed this and it looks good" which helps someone who *can* approve it to know it's not obviously wrong or totally broken). >=A0=A0=A0 This is why I would like to apply for promotion to become an=20 >official Maintainer myself not limited to special modes anymore. > >=A0=A0=A0 Don't worry, my plan is not to commit anything that comes to my= =20 >attention or all the patches that I proposed currently awaiting=20 >validation. I just think that I've broken the lib ABI or the build=20 >enough times to now know when I can commit a patch after a couple of=20 >days of announcement or if I still need review. This sounds like you're just saying "I don't want to wait for approval any more" :-) There's more to being a maintainer than that. >=A0=A0=A0 Note that there are still 2 points on which I am unclear: > >- The dev stage we are in. I see that stage 1 is almost over but I=20 >don't know if awaiting patches can be committed for instance. I count=20 >on th announcement period to allow someone to say 'Stop' Patches posted during stage 1 can still be committed after stage 1 ends. It's not ideal, but it's OK. That's why I've been concentrating on my own patches and will review all the pending submissions ASAP. >- The legal matter: I don't know when a patch can be considered as=20 >small enough that FSF DoR is not necessary. This is why I don't plan=20 >to commit someone else patch without proper agreement. > >If you agree let me know if I should specify something like 'newby' in=20 >the MAINTAINERS file or just go ahead without changing anything. > >Fran=E7ois >