Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Stepping down from several maintainership roles
Date: Fri, 21 Mar 2003 22:34:00 -0000	[thread overview]
Message-ID: <3E7B936F.6050209@redhat.com> (raw)
In-Reply-To: <ro1d6kk3215.fsf@jackfruit.Stanford.EDU>

David,

An inactive maintainer, at some point, be it 6 months, or even two years 
of inactivity, needs recognize that they are no longer participating in 
GDB's day-to-day development and as such should probably step back from 
their maintenance roles.  If doing this means that the role becomes 
vacant then that is a good thing.  This is because having no maintainer 
removes any possible perception that the code is, in even the smallest 
way, being developed or maintained (c.f., java).

With this in mind I'll, from time to time, ping GDB maintainers and ask 
them to review their current level of commitment to both GDB and the 
FSF, and consider droping an area of maintenance responsibility. 
Overall, I receive a very positive response to such requests.  I 
personally appreciate such a level of professionalism, simply 
acknowledging this can be both difficult and painful.

No one has been `pressured into severing ties outright'.

Andrew


      reply	other threads:[~2003-03-21 22:34 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
2003-03-21 22:34     ` Andrew Cagney [this message]

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=3E7B936F.6050209@redhat.com \
    --to=ac131313@redhat.com \
    --cc=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