Re: maintainer roles

From: Date: Mon, 16 Feb 2004 15:25:35 +0000
Subject: Re: maintainer roles
References: 1  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-103@lists.php.net to get a copy of this message
Hi, Don't forget people who have contributed major patches, but otherwise are not involved, and documentors. I think we should use contributor for those swat team developers (appears, delivers an excellent patch, disappears), and add the documentor role, helper can go byebye. Greg Lukas Smith wrote:
Hi, what exactly is the different between the different maintainer roles? They are not really described in the dtd. I remember we once had the issue of how to deal with people that have constributed to the package in the past, but are no longer involved with the package for some reason or another. How about this (this may be somewhat PEAR specific as we regulate commiting to packages a bit more): 1) lead: may package releases, obviously can commit to CVS and may give anyone else temporary or permament permission to commit 2) developer: may commit to the package 3) contributor: someone who contributed code but is no longer active in development At the same time it would be even better if pearweb would store the lead and developer mantainters set at a given release as an automatic credit history. I guess we dont even need the contributor role then anymore but this way we would have an easy to read indication of who is and who used to be involved with the package. Please note that alot of people who are actually developers are set as role constributor atm. However for example with MDB I set Tomas, Stig and Manuel as contributors and they keep getting my MDB bug reports (then again they never complained). regards Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07


« previous php.pear.core (#103) next »