From: "Tomáš Chvátal" <tomas.chvatal@gmail.com>
To: 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 18:00:59 +0100 [thread overview]
Message-ID: <CA+NrkpfF0fu5Rx1LjsmVfttwN0BwOrFbOR90_o4gXRbq8qeTUw@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_mdmCHOQHi-a==QhkbjkZBQPTo9+ySJcLbh7gsgBNLPhQ@mail.gmail.com>
2013/2/1 Rich Freeman <rich0@gentoo.org>:
> 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.
You my friend are slowly pissing me of as I read through all the
flames you cause on -dev.
There is no council vote required as it is already defined within qa
team specs (and glep too when i think of it, so yep there is glep for
you).
>
> 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.
No, they won't get anyone looking over their shoulder unless they
decide to neglect the bugs as few maintainers did.
I didn't see a lot forced removals caused by qa, did you?
The existence of the package usually does not bother anyone,
maintainer just decided that its burden so it will be removed, he
could've put it to m-n but its up to every maintainer to decide what
to do if the package has bugs he deem serious. If anyone else decide
to pick up where they left, it is his job to ensure the package gets
fixed and up-par to work nicely.
Bit ago we had this discussion about keeping broken shit in tree
masked or just prune it, and obvious solution was to remove it as
there is just few of us and if anyone wants to start where we left he
can pick out the ebuild from attic and put into his own overlay where
it might work for him or even put it back to tree fixed.
>
> 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...
>
Go for it, i wrote exactly what to do, create vcs/tracker/homepage and
it can stay.
next prev parent reply other threads:[~2013-02-01 17:01 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
2013-02-01 17:00 ` Tomáš Chvátal [this message]
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=CA+NrkpfF0fu5Rx1LjsmVfttwN0BwOrFbOR90_o4gXRbq8qeTUw@mail.gmail.com \
--to=tomas.chvatal@gmail.com \
--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