From: "Tomáš Chvátal" <tomas.chvatal@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [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 14:53:19 +0100 [thread overview]
Message-ID: <CA+Nrkpd2E6KQQOt6FEN9eVdzcw9kpr06gbzUBOcFSj5rPbKPXw@mail.gmail.com> (raw)
Hello guys,
just to be sure here "Removals are completely up to the maintainer to
decide", with expection of QA removal where the package must be
already broken to get punted.
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]).
For dead upstream packages there are quite few problems you, who
support keeping it in tree, seem not to notice. The distro patches
will blob up (with each distro having different stuff) as things break
with shiny new updates (and no saying it builds with older xyz does
not make it work), users have no chance to report problems with the
package elsewhere than to our bugzilla, etc, etc. This is the reason
why the fedorahosted.org was fired up. So if you care about the
package, take your time, fire up VCS/homepage/tracker there and try to
work on it or find someone else interested to help you with becaming
at least pseodo-upstream.
Cheers
Tom
next reply other threads:[~2013-02-01 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 13:53 Tomáš Chvátal [this message]
2013-02-01 14:52 ` [gentoo-dev] Removals reply (I am not going to figure out which tread of those all should i reply to) Rich Freeman
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=CA+Nrkpd2E6KQQOt6FEN9eVdzcw9kpr06gbzUBOcFSj5rPbKPXw@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