On 4 December 2012 17:28, Rick "Zero_Chaos" Farina <zeroch...@gentoo.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote: >> On 04/12/2012 08:01, Rick "Zero_Chaos" Farina wrote: >>> I feel the description field is already overloaded when there is a proxy >>> situation, maybe it would be best to define a field for this. Also >>> english isn't primary language for everyone in the world so if the >>> policy could actually be specific on this it would benefit everyone. >> >> Or maybe we can just agree that common sense rules all, and we always >> set the proxied maintainer as assignee, and the proxy maintainer as CC.. >> because, you know, that's the only way a proxy maintainer can >> close/change a bug at all. >> > That is a very good point. But being that it's a very good point it > obviously never occurred to me that it shouldn't be spelled out in the > metadata. Is there a policy for this as well that I am unaware of? 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.
Bug-wranglers are supposed to do that by default. When you see a non-gentoo developer in metadata.xml, the default action is to assume his is the real maintainer and the bugs should be assigned to him. Such guidance should be documented in the bug-wranglers project page and not on the proxy-maintainers one. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
