From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] proxy-maintainers herd as a backup herd for all the user-maintained packages
Date: Tue, 5 Mar 2013 09:09:47 +0000 [thread overview]
Message-ID: <CAG2jQ8g8z+bNQzu_3xqeB-HKUsPE1RVNkmH31jXakdQxxZV4rg@mail.gmail.com> (raw)
In-Reply-To: <20130305044147.6cb533dc@marga.jer-c2.orkz.net>
On 5 March 2013 03:41, Jeroen Roovers <jer@gentoo.org> wrote:
> On Sun, 03 Mar 2013 19:35:24 +0000
> Markos Chandras <hwoarang@gentoo.org> wrote:
>
>> A number of packages in the tree are maintained by a Gentoo developer
>> and a user. As a result of which, we are unable to monitor these
>> packages in bugzilla. This is useful in case one of the maintainers
>> goes MIA so we can find an alternative maintainer for them. So I am
>> kindly asking you to add the proxy-maintainers herd as a backup herd
>> for the packages that you proxy-maintain. I will go ahead and do it
>> myself in two weeks if you don't want to bother fixing your metadata.
>> If you want your packages to be excluded please let me know. This is
>> mainly for tracking purposes and we don't intend to take over the
>> maintainership of your packages (unless you want us to).
>
> Excellent idea. But how will proxy-maint@ devs know not to "take over"?
>
>
> jer
>
If there is at least one Gentoo developer in metadata.xml we assume
the package is properly maintained by him so
we never touch it.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
next prev parent reply other threads:[~2013-03-05 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 19:35 [gentoo-dev] proxy-maintainers herd as a backup herd for all the user-maintained packages Markos Chandras
2013-03-05 3:41 ` Jeroen Roovers
2013-03-05 9:09 ` Markos Chandras [this message]
2013-03-05 15:07 ` Jeroen Roovers
2013-03-17 13:47 ` Markos Chandras
2013-03-17 16:46 ` Markos Chandras
2013-04-22 9:21 ` Alexis Ballier
2013-04-22 9:25 ` Markos Chandras
2013-04-22 9:36 ` Alexis Ballier
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=CAG2jQ8g8z+bNQzu_3xqeB-HKUsPE1RVNkmH31jXakdQxxZV4rg@mail.gmail.com \
--to=hwoarang@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