[Mageia-dev] maintainer groups

Mon Oct 25 22:35:38 CEST 2010

Ahmad Samir a écrit :
+> On 25 October 2010 19:44, Michael Scherer<misc at zarb.org>  wrote:
+>    
+>> Le lundi 25 octobre 2010 à 19:29 +0200, Luca Berra a écrit :
+>>      
+>>> this is a suggestion i already made with mandriva but it landed nowhere,
+>>> let's try again.
+>>>
+>>> At the moment we have 1to1 relationship in all tools between maintainer
+>>> and package. But for some packages we have more than one people willing
+>>> to work on that package. Besides, for some critical package it may be
+>>> useful having more than one person responsible for it.
+>>> Also someone might be interested in helping on package foo, but feels
+>>> too much inexperienced to take full reponsability for it. Peer review is
+>>> important.
+>>>
+>>> The idea is not associating a package with a single maintainer, but
+>>> associate each package to a maintainer-group, say
+>>> NAME at packages.mageia.org, and let maintainers subscribe to package
+>>> maintenance.
+>>>
+>>> this would result that in case a ticket is opened in bugzilla vs
+>>> package, all interested parties would be notified, and start working on
+>>> a solution. (this might require a bit of coordination, but maybe just
+>>> assigning the bug to a real person is enough to note someone is taking
+>>> care of the problem)
+>>>        
+>> +1 to the idea.
+>> I just wonder how it articulate on bugzilla side ( ie, we should try to
+>> avoid having a patch on bugzilla side, as this is usually causing
+>> trouble ).
+>> Ie, if I want to take care of a bug report, I would likely assign it to
+>> me, no ?
+>>
+>> Wouldn't it better to use cc for that ?
+>> --
+>> Michael Scherer
+>>
+>>
+>>      
+> Well, if a maintainer changes to status to ASSIGNED, we can assume
+> he's working on it.
+>
+> QA team, lately, had a sort of a rule, when one of them was working on
+> a bug he'd post to the report to say so so as not to duplicate work;
+> the same was with sec team. That's a good way IMHO.
+>    
+
+Good idea.  This approach is also used by transators in various projects.
+It also might be a good to have a designated principle maintainer, in 
+the maintainer group for a package.
+