Based on this information (, does not participate actively,
or has been inactive for an extended period), I would like to remove the
following committers from the project:
tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Friday, August 10, 2007 8:49
To: Tools PMC mailing list
Subject: Re: [tools-pmc] Removing
Committer from the Project
There are provisions in the Tools charter for removing.
"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
basically the project lead/team should suggest to the PMC that someone be
removed as a committer and the PMC can sanction the action.
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.
08/06/2007 03:59 PM
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
"Tools PMC mailing list"
[tools-pmc] Removing Committer from the
do I remove committers from the project?
do you think we should position a QA engineer “just” testing the
project with a need for full Bugzilla actions but no source modification?
Manager, Development Tools
PDT Project Leader
yossi@xxxxxxxx http://www.zend.com/ +1-646-919-1456
tools-pmc mailing list