Stig et all, > * give developers a sense of ownership in their modules by: > ** assigning _one_ lead maintainer to each module > ** mailing module bug summaries to maintainers > ** making maintainers more publicly visible > ** separately list maintainer[s] in credits (maintainer[s] and > developers) > ** making statistics for each module showing the "performance" of the > maintainer in terms of bug fix ratio etc. > ** assign a person responsible for testing during RCs
I'll have to throw in a +1 on this idea. While it will definately show us some possibly dark sides of PHP (like which modules receive the least attention) it should also help end users the most. >---------------------------------------------------------------< Dan Kalowsky "Tonight I think I'll walk alone. http://www.deadmime.org/~dank I'll find soul as I go home." [EMAIL PROTECTED] - "Temptation", New Order -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
