From: David Carlton <carlton@math.stanford.edu>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: gdb-patches@sources.redhat.com
Subject: Re: Stepping down from several maintainership roles
Date: Fri, 21 Mar 2003 20:20:00 -0000 [thread overview]
Message-ID: <ro1d6kk3215.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <o5isugwkm3.fsf@toenail.toronto.redhat.com>
On 18 Mar 2003 14:16:52 -0500, fche@redhat.com (Frank Ch. Eigler) said:
> fnasser wrote:
>> My new responsibilities in my job and the project I am working on
>> are not allowing me to be responsive to the list requests. This
>> will remain like that until the end of the Summer. [...] So I am
>> stepping down from several maintainership roles. [...]
> This is too bad. It appears that in order to solve the problem of
> insufficient time availability of maintainers, several of them have
> been nagged in order to get them to resign. These people having
> history and experience have been pressured into severing ties
> outright, making it likely that they spend even less time on gdb.
> How is this supposed to be progress?
That was my reaction, too. On the other hand, on a purely pragrmatic
level, going from having 1 maintainer in an area to having 0
maintainers in that area can be progress because it means that, all of
a sudden, any global maintainer can approve a patch in that area. And
removing maintainers from areas that, in practice, they'll never
approve patches for, doesn't hurt anything, though I don't see why it
helps anything either unless those maintainers no longer consider
themselves competent to approve patches in those areas.
Still, as I've said before, I would far prefer a solution that
increases the number of local maintainers: I do not believe that all
people competent to be local maintainers in various areas are, in
fact, currently local maintainers, and I do believe that the current
standard for becoming a local maintainer is too high.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-03-21 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 14:59 Fernando Nasser
2003-03-18 19:16 ` Frank Ch. Eigler
2003-03-21 20:20 ` David Carlton [this message]
2003-03-21 22:34 ` Andrew Cagney
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=ro1d6kk3215.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=fche@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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