Jump to: navigation, search

Difference between revisions of "WTP PMC Policies"

(initial PMC policies)
 
(Introduction)
 
(3 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
that are related to our PMC or project governance.  
 
that are related to our PMC or project governance.  
  
Eclipse has by-laws, and a development processes document that cover many aspects of
+
Eclipse has [http://www.eclipse.org/org/documents/Eclipse%20BYLAWS%202008_07_24%20Final.pdf by-laws],  
governance in Eclipse. In addition, of course, we have Project Charter, which  
+
and a [http://www.eclipse.org/projects/dev_process/development_process.php development processes document]
references the Eclipse Standard Charter, with some projects better described in a
+
and [http://www.eclipse.org/org/documents/ many other documents]
refactoring document.  
+
that  
 +
cover many aspects of
 +
governance in Eclipse. In addition, of course, we have our [http://www.eclipse.org/webtools/project-charter.html Web Tools Project Charter], which  
 +
builds on the [http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php Eclipse Standard Charter], with some projects better described in out [http://www.eclipse.org/webtools/devProcess/wtpProjects/WTP%20Projects.pdf WTP refactoring document].  
  
 
This document is not to replace or contradict any of
 
This document is not to replace or contradict any of
Line 21: Line 24:
  
 
They are nominated by and voted in by the other PMC members. They are
 
They are nominated by and voted in by the other PMC members. They are
typically Project Leads, but do not have to be. One thing that sets them
+
typically Project Leads, but do not have to be, and not all project leads are PMC members.  
apart is they all have committed to (and usually have a vested interest
+
One thing that sets PMC members apart from other leads or committers
 +
is they all have committed to (and usually have a vested interest
 
in) seeing all of WTP succeed, not just their specific project. One
 
in) seeing all of WTP succeed, not just their specific project. One
manifestation of this is they agree to take on a role that spans all WTP
+
manifestation of this is they agree to take on a larger, [[:Category:WTP_Roles|WTP role]] that spans all WTP
project, such as planning, education, architecture, requirements, etc.
+
projects, such as planning, education, architecture, requirements, etc.
  
 
== Can a PMC member vote on his own CQ or bug (when PMC review needed) ==
 
== Can a PMC member vote on his own CQ or bug (when PMC review needed) ==
Line 37: Line 41:
 
do recuse themselves, and ask for votes from other members. But, its felt
 
do recuse themselves, and ask for votes from other members. But, its felt
 
there are so many fairly trivial, obvious cases, that is speeds things up
 
there are so many fairly trivial, obvious cases, that is speeds things up
not to strictly always require forced review from all PMC members.
+
not to strictly always require forced review from all PMC members. The number
 +
of votes required are adjusted closer to deadlines, plus, as
 +
as documented [[WTP_PMC_Defect_Review]] we request all PMC members to be added
 +
to the pmc_approve field, so even if already approved, other PMC members can
 +
easily find approvals, and comment if they disagree or have additional questions.
 +
 
 +
 
 +
[[Category:Process and Policies| ]]

Latest revision as of 12:38, 6 April 2010

Introduction

This page is to document some of the agreements, policies, and clarifications that come up from time to time in the WTP PMC, that are related to our PMC or project governance.

Eclipse has by-laws, and a development processes document and many other documents that cover many aspects of governance in Eclipse. In addition, of course, we have our Web Tools Project Charter, which builds on the Eclipse Standard Charter, with some projects better described in out WTP refactoring document.

This document is not to replace or contradict any of those documents. Those documents have authority if contradictions found.

But all those rules and regulations do not cover everything. In fact, in many cases, they say, in effect, "... it is up to the PMC to decide ...". So, in this document, we try and capture some of those decisions that effect our PMC policies and governance in the form of a FAQ.

How does one become a member of the PMC?

They are nominated by and voted in by the other PMC members. They are typically Project Leads, but do not have to be, and not all project leads are PMC members. One thing that sets PMC members apart from other leads or committers is they all have committed to (and usually have a vested interest in) seeing all of WTP succeed, not just their specific project. One manifestation of this is they agree to take on a larger, WTP role that spans all WTP projects, such as planning, education, architecture, requirements, etc.

Can a PMC member vote on his own CQ or bug (when PMC review needed)

Yes. In WTP we have adopted that policy because we choose PMC members that have an overall view of WTP, and interest and commitment to seeing it succeed. Additionally, we choose members that are experienced and mature enough to be trusted that if something should be discussed, they would know that and bring it forward for discussion or clarification, before just blindly approving their own stuff. In some cases, PMC members do recuse themselves, and ask for votes from other members. But, its felt there are so many fairly trivial, obvious cases, that is speeds things up not to strictly always require forced review from all PMC members. The number of votes required are adjusted closer to deadlines, plus, as as documented WTP_PMC_Defect_Review we request all PMC members to be added to the pmc_approve field, so even if already approved, other PMC members can easily find approvals, and comment if they disagree or have additional questions.