public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Removals reply (I am not going to figure out which tread of those all should i reply to)
Date: Fri, 1 Feb 2013 09:52:16 -0500	[thread overview]
Message-ID: <CAGfcS_mdmCHOQHi-a==QhkbjkZBQPTo9+ySJcLbh7gsgBNLPhQ@mail.gmail.com> (raw)
In-Reply-To: <CA+Nrkpd2E6KQQOt6FEN9eVdzcw9kpr06gbzUBOcFSj5rPbKPXw@mail.gmail.com>

On Fri, Feb 1, 2013 at 8:53 AM, Tomáš Chvátal <tomas.chvatal@gmail.com> wrote:
> If you as developers and users find some package useful you can retake
> the maintainership (or became proxy-maint) which also expects you to
> take care of the bugs (QA can prune it even if you take the
> maintainership but ignore failures [even if your personal feeling is
> that it is corner case, it is for QA to deicde]).

Citation?  I don't see any GLEPs or other Council-approved policies to
that effect.

And this is of course why nobody actually wants to maintain these
packages - everybody is going to be looking over your shoulder because
they've already decided that the existence of the package bothers
them.

Honestly, threads like this bug me so much that I'm half-tempted to
take over maintainership of one of these packages just to be a test
case...  Ugh - time for an email break...

Rich


  reply	other threads:[~2013-02-01 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 13:53 [gentoo-dev] Removals reply (I am not going to figure out which tread of those all should i reply to) Tomáš Chvátal
2013-02-01 14:52 ` Rich Freeman [this message]
2013-02-01 17:00   ` Tomáš Chvátal
2013-02-01 17:05     ` Diego Elio Pettenò
2013-02-02 19:35 ` [gentoo-dev] Removals reply - please write adequate log messages! Andreas K. Huettel

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='CAGfcS_mdmCHOQHi-a==QhkbjkZBQPTo9+ySJcLbh7gsgBNLPhQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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