From: Sergey Popov <pinkbyte@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds)
Date: Tue, 04 Dec 2012 22:35:26 +0400 [thread overview]
Message-ID: <50BE426E.5070702@gentoo.org> (raw)
In-Reply-To: <50BE32B9.6010205@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
04.12.2012 21:28, Rick "Zero_Chaos" Farina wrote:
> A quick "site:devmanual.gentoo.org proxy" search indicates no
> documentation of this at all.
>
> http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml?style=printable
>
> This page exists, but doesn't really mention anything about proper bug
> assignment. I know a lot of you have been doing this a very long time
> and there is a 'standard' way of doing things, but for us new guys if
> there is no documentation there is no policy.
>
Agreed. I add description field to metadata for proxying packages, cause
i see such field in other packages' metadata. That is it. But it would
be better when this became official policy. At least - define actual
maintainer first, even if he is not developer - this would never confuse
scripts for automated bug filing
--
Best regards, Sergey Popov
Gentoo Linux Developer
Desktop-effects project lead
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2012-12-04 18:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 15:21 [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-02 15:38 ` Rich Freeman
2012-12-02 19:30 ` Markos Chandras
2012-12-04 1:18 ` Ben de Groot
2012-12-04 7:43 ` Ian Whyman
2012-12-04 9:19 ` Markos Chandras
2012-12-04 15:42 ` Alec Warner
2012-12-04 18:54 ` Markos Chandras
2012-12-06 10:53 ` Ben de Groot
2012-12-04 8:10 ` Rick "Zero_Chaos" Farina
2012-12-04 9:23 ` Markos Chandras
2012-12-04 16:01 ` Rick "Zero_Chaos" Farina
2012-12-04 17:06 ` Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds) Diego Elio Pettenò
2012-12-04 17:28 ` Rick "Zero_Chaos" Farina
2012-12-04 18:35 ` Sergey Popov [this message]
2012-12-04 18:48 ` Diego Elio Pettenò
2012-12-04 18:51 ` Markos Chandras
2012-12-06 11:02 ` Ben de Groot
2012-12-06 13:28 ` Markos Chandras
2012-12-06 15:27 ` Peter Stuge
2012-12-06 15:54 ` Ian Stakenvicius
2012-12-06 16:04 ` Peter Stuge
2012-12-06 19:07 ` Markos Chandras
2012-12-08 17:48 ` Jeroen Roovers
2012-12-04 17:01 ` [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-04 17:17 ` Rick "Zero_Chaos" Farina
2012-12-04 17:32 ` hasufell
2012-12-04 17:46 ` Rick "Zero_Chaos" Farina
2012-12-04 18:17 ` hasufell
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=50BE426E.5070702@gentoo.org \
--to=pinkbyte@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