Re: [tools-pmc] Removing Committer from the Project

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

There are provisions in the Tools charter
for removing.  Check ou
        http://www.eclipse.org/tools/eclipsetools-charter.php
particularly
        "Committer
that is disruptive, does not participate actively, or has been inactive
for an extended 
        period
may have his or her commit status removed by the PMC."
So basically the project lead/team should
suggest to the PMC that someone be removed as a committer and the PMC can
sanction the action.

As for the QA engineer it seems you
are pushing on the fact that non-committers do not have full bugzilla capabilities?
 This has been a long standing issue.  There are people in various
"roles" who we would like to have full bugzilla access but not
necessarily commit access.  In fact, one could see getting bugzilla
access is one of the steps to becoming a committer.  contributing
to bug triage and management is just as important a contribution as many
code contributions.  So, I am fully in support of this idea.

Jeff

"Yossi Leon" <yossi@xxxxxxxx>
Sent by: tools-pmc-bounces@xxxxxxxxxxx

08/06/2007 03:59 PM

Please respond to
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>

To	"Tools PMC mailing list" <tools-pmc@xxxxxxxxxxx>
cc
Subject	[tools-pmc] Removing Committer from the Project

Hi All,
 
1. How do I remove committers from the project?
2. How do you think we should position a
QA engineer “just” testing the project with a need for full Bugzilla
actions but no source modification?
 
Thanks,
--
Yossi Leon
Product Manager, Development Tools
& PDT Project Leader
yossi@xxxxxxxx http://www.zend.com/
+1-646-919-1456
 
http://blogs.zend.com/author/yossi/

 _______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc