From: "François Dumont" <frs.dumont@gmail.com>
To: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Request for extended maintainers rights
Date: Thu, 14 Nov 2019 21:01:00 -0000 [thread overview]
Message-ID: <ae462be6-d233-b64d-d199-1a7bbd7ca7b9@gmail.com> (raw)
Hi
   With 4 official Maintainers but only 1 dealing with patch requests
who is moreover dealing with a lot of other tasks I fear that libstdc++
becomes really unattractive for occasional contributors.
   This is why I would like to apply for promotion to become an
official Maintainer myself not limited to special modes anymore.
   Don't worry, my plan is not to commit anything that comes to my
attention or all the patches that I proposed currently awaiting
validation. I just think that I've broken the lib ABI or the build
enough times to now know when I can commit a patch after a couple of
days of announcement or if I still need review.
   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 don't
know if awaiting patches can be committed for instance. I count on th
announcement period to allow someone to say 'Stop'
- The legal matter: I don't know when a patch can be considered as small
enough that FSF DoR is not necessary. This is why I don't plan to commit
someone else patch without proper agreement.
If you agree let me know if I should specify something like 'newby' in
the MAINTAINERS file or just go ahead without changing anything.
François
next reply other threads:[~2019-11-14 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 21:01 François Dumont [this message]
2019-11-14 22:02 ` Jonathan Wakely
2019-11-15 6:05 ` François Dumont
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=ae462be6-d233-b64d-d199-1a7bbd7ca7b9@gmail.com \
--to=frs.dumont@gmail.com \
--cc=libstdc++@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).