Folks, Here's something (see below) that i had sent to a the board mailing list a few years back (added one more item from the original draft). So I'd ask the Existing WS PMC Members to consider for example
- How many commits they made in the recent past - How may releases they reviewed in the recent past - How many discussions they engaged in the recent past - How many JIRA's they raised/resolved in the recent past - .... You can do this very simply by using the excellent Apache/MarkMail tool, See example searches for svn commit activity. http://apache.markmail.org/search/?q=subject%3A%22svn+commit%22+from%3Aglen+order%3Adate-backward http://apache.markmail.org/search/?q=subject%3A%22svn+commit%22+from%3Adeepal+order%3Adate-backward http://apache.markmail.org/search/?q=subject%3A%22svn+commit%22+from%3Asanjiva+order%3Adate-backward http://apache.markmail.org/search/?q=subject%3A%22svn+commit%22+from%3Asamisa+order%3Adate-backward http://apache.markmail.org/search/?q=subject%3A%22svn+commit%22+from%3Adims+order%3Adate-backward Then make a determination on whether they should still continue to be PMC members or not for themselves. There is a thread going on in the [EMAIL PROTECTED] for cleaning up of the PMC member list. I am sure this email will help people make up their minds a bit more. thanks, -- dims =========================================== Folks, Am trying to come up with bullet items (which can be expanded later) on what the board expects from a PMC and its members. Does anyone know if there is a document that already has this kind of list? Can folks please help refine/expand this list. (May be each line item should start with "Thou Shalt" :)=20 #1: Timely and accurate reports based on the rotation schedule in the foundation svn module #2: Create and maintain a charter that governs the PMC/project(s) #3: Take decisions affecting progress and health of the projects(s), ensure smooth functioning and create a conducive work atmosphere for everyone in the community. #4: Focus efforts more on community building rather than on code. #5: Ensure all community members (not just PMC members) participate in decision-making processes (ex: limit IRC usage, ban private lists for dev related decisions) #6: Work with Infrastructure to meet day-to-day requirements of community members. #7: Interact with other PMC's/Projects to learn best practices, reuse code, increase synergy, avoid duplication of effort. #8: Work with the board for refining policies and practices to better serve the needs of the community. #9: Work hard to add new individuals to the community, provide mentoring and enable them to join the PMC. 10: Keep strict watch on legal issues w.r.t copyrights, patents and licenses. Work proactively with our legal resources to avoid problems to folks who use our projects. 11: Be active and hands on contributor whether it is commits or JIRA's or answering questions on user or dev mailing list. =========================================== -- Davanum Srinivas :: http://davanum.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
