On 6 December 2012 11:02, Ben de Groot <yng...@gentoo.org> wrote: > > > > On 5 December 2012 02:51, Markos Chandras <hwoar...@gentoo.org> wrote: >> >> On 4 December 2012 17:28, Rick "Zero_Chaos" Farina <zeroch...@gentoo.org> >> wrote: >> > On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote: >> >> 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.. >> > >> > >> > 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. >> > > Actually, as I have been arguing elsewhere, scattering policies over > multiple documents is not helpful. So this should be documented in > devmanual. > > -- > Cheers, > > Ben | yngwin > Gentoo developer > Gentoo Qt project lead, Gentoo Wiki admin
This policy is for the bug-wranglers project, which someone must read before he attempts to do any bug-wrangling. I see no reason to move this to devmanual. However, it is possible to add a note on metadata.xml section in devmanual to explain how to structure a metadata.xml file for proxy maintainers. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
