svn commit: r72 - trunk/www
robertbray at osgeo.org
robertbray at osgeo.org
Wed Oct 25 16:50:28 EDT 2006
Author: robertbray
Date: 2006-10-25 20:50:28+0000
New Revision: 72
Added:
trunk/www/psc.html
Modified:
trunk/www/developer.html
Log:
FDO230
Modified: trunk/www/developer.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/developer.html?view=diff&rev=72&p1=trunk/www/developer.html&p2=trunk/www/developer.html&r1=71&r2=72
==============================================================================
--- trunk/www/developer.html (original)
+++ trunk/www/developer.html 2006-10-25 20:50:28+0000
@@ -7,18 +7,14 @@
<body>
<h1>FDO Open Source - Getting Involved as a Contributor</h1>
-<p><strong>NOTE: All of the information on this page is subject to change as the Open Source Geospatial Foundation makes decisions regarding its governance.</strong></p>
-
<p>There are three different levels of involvement for developers interested in contributing to FDO Open Source. These levels of involvement are as follows:</p>
<ul type="square">
<li><strong>Project Contributor</strong> - A Project Contributor is a developer who contributes patches, code, and/or documentation through the Project Tracker tool. Project Contributors do not have Subversion check-in access. Integration of a developer's contributions is at the discretion of the FDO Open Source Project Steering Comittee (PSC) and individuals in the Project Developer role. This is typically an iterative, communicative process.</li>
<li><strong>Project Developer</strong> - A Project Developer has full commit access to the trunk of the source tree and has a signed Contributor License Agreement on file with OSGeo. Project Developers can directly make changes to the source base of the development branch, from which the nightly builds are made. Project Developers review and accept code submitted by Project Contributors. Project Developers are elected by the PSC.</li>
- <li><strong>Project Steering Committee (PSC) Member </strong>– The FDO Open Source PSC is the entity that manages the project. A PSC Member is a Project Developer that was elected to the FDO Open Source PSC due to the developer’s merit and active participation in the project. PSC Members have full commit access to the code repository, the right to vote for project-related decisions, and the right to propose individuals for Project Developer status.</li>
+ <li><strong>Project Steering Committee (PSC) Member </strong>– The FDO Open Source PSC is the entity that manages the project. A PSC Member is a Project Developer or an end user of FDO that was elected to the FDO Open Source PSC due to the developer’s merit and active participation in the project. PSC Members have the right to vote for project-related decisions and the right to nominate individuals for Project Developer status. Note that most PSC members are also Project Developers, but they do not have to be. </li>
</ul>
-<p>All developers on the project start out as Project Contributors. A developer who has sent in solid, useful patches can be elevated to the Project Developer role by the Project Steering Committee (PSC). To become a Project Contributor use the <a href="https://fdo.osgeo.org/servlets/ProjectMembershipRequest">Request project membership/role</a> link at the top of the FDO Open Source project home page and request the Project Contributor role. </p>
-<p>Please note that the Open Source Geospatial Foundation is currently defining its governance model and intellectual property policies, including the policy under which the OSGeo accepts code contributions from developers. Until these policies are fully defined, we cannot grant Project Developer status to any individual. It is expected that developers will be asked to sign a Contributor License Agreement similar to what Apache Software Foundation requires before becoming a Project Developer or PSC Member.<br />
+<p>All developers on the project start out as Project Contributors. A developer who has sent in solid, useful patches can be elevated to the Project Developer role by the Project Steering Committee (PSC). To become a Project Contributor use the <a href="https://fdo.osgeo.org/servlets/ProjectMembershipRequest">Request project membership/role</a> link at the top of the FDO Open Source project home page and request the Project Contributor role.<br />
</p>
-
<div class="h2">
<h2>Join the Mailing Lists</h2>
<p>Join the mailing lists to participate in development activities. The dev at fdo.osgeo.org is the primary channel of communication for developers working on the project. You can also sign up for the issues at fdo.osgeo.org or commits at fdo.osgeo.org mailing lists to watch development activity. If you are a registered user, <a href="https://fdo.osgeo.org/servlets/ProjectMailingListList">click here to sign up</a> to sign up for one or more of these lists. </p>
@@ -28,11 +24,14 @@
<h2>Developer Resources</h2>
<p>The following resources are available to help developers get started working on FDO Open Source:</p>
<ul type="square">
- <li>Development Process [Coming Soon]</li>
+ <li><a href="psc.html">Project Steering Committee</a> [DRAFT]</li>
+ <li>FDO RFCs [TBD] </li>
+ <li>Contributor Agreement [TBD] </li>
+ <li>Development Process [TBD]</li>
<li><a href="projectartifacts.html">Project Artifacts</a></li>
<li><a href="artifactlifecycle.html">Artifact Lifecycle</a></li>
- <li>Contributing Patches [Coming Soon]</li>
- <li>Coding Guidelines [Coming Soon]</li>
+ <li>Contributing Patches [TBD]</li>
+ <li>Coding Guidelines [TBD]</li>
<li><a href="subversionconfig.html">Subversion Client Configuration</a></li>
</ul>
</div>
Added: trunk/www/psc.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/psc.html?view=auto&rev=72
==============================================================================
--- (empty file)
+++ trunk/www/psc.html 2006-10-25 20:50:28+0000
@@ -0,0 +1,115 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>MapGuide Open Source - Project Steering Committee</title>
+</head>
+
+<body>
+<h1>FDO Open Source - Project Steering Committee [DRAFT]</h1>
+
+<div class="h2">
+<h2><a name="summary" id="summary">Summary</a></h2>
+<p>The Project Steering Committee (PSC) is the official governing body of the FDO Open Source Project and is responsible
+ for all aspects of managing the project. The PSC is made up of individuals based on merit and is responsible for setting the overall direction of the project and releases, determining what
+ features go in and when, and how those features are implemented. As a user or developer this document provides insight into how the project is managed and how you can enhance and influence it. In particular this document describes the structure of the PSC, the process by which is makes decisions on project issues (both technical and non-technical), and the
+ responsibilities of the PSC and its members.</p>
+<p>The definition of the FDO Open Source PSC derives from the guidelines already developed for the
+ <a href="http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1/" target="_blank">MapServer Technical Steering Committee</a>, the
+ <a href="http://docs.codehaus.org/display/GEOSDOC/0+Project+Steering+Committee" target="_blank">GeoServer PSC</a>, and the
+ <a href="http://docs.codehaus.org/display/MAP/Contributers+Guide" target="_blank">MapBuilder PSC</a>.
+</p>
+</div>
+
+<div class="h2">
+<h2><a name="structure" id="structure">Structure</a></h2>
+<p>The PSC is made up of individuals consisting of developers and users. Members are elected to participate in the
+ PSC based on merit irrespective of their organizational ties. It is desirable but not strictly required for the PSC to be made up of an odd number of members (5 or more)
+ to prevent ties in the voting process. One member of the PSC is appointed Chair, who has additional responsibilities to
+ organize regular meetings and to resolve tie votes should they occur. The Chair is the ultimate adjudicator should the
+ process ever breakdown entirely.</p>
+<h3>Current PSC</h3>
+<ul>
+ <li>Greg Boone </li>
+ <li>Bob Bray (Chair)</li>
+ <li>Orest Halustchak </li>
+ <li>Mateusz Loskot</li>
+ <li>Frank Warmerdam</li>
+ <li>TBD - Open </li>
+ <li>TBD - Open</li>
+ </ul>
+<h3>Adding Members</h3>
+<p>Any member of the PSC or the FDO-dev mailing list may nominate someone for committee membership at any time. Only
+ existing PSC members may vote on new members. Nominees must receive a majority vote from existing members to be added to
+ the PSC.</p>
+<h3>Stepping Down </h3>
+<p>Turnover within the PSC is allowed and expected as people move from one project to another or simply move on to a
+ different role. If for any reason a PSC member is not able to fully participate then they are free to step down. If a
+ member is not active (e.g. no voting, mailing list, or IRC participation) for a period of two months then the PSC
+reserves the right to remove that member from the PSC via a motion from a PSC member and a majority vote. Likewise should a member of the PSC begin to act counter to the goals of the project as a whole on a recurring basis, then a PSC member can raise a motion to remove that member from the PSC. Again in this case a majority vote is required to pass the motion thus removing that member from the PSC. In both cases the PSC is then free to seek nominations to fill that position.</p>
+</div>
+
+<div class="h2">
+<h2><a name="decisionmaking" id="decisionmaking">Process</a></h2>
+<p>The primary role of the PSC is to make decisions relating to the management of the project. The decision making process is based on reaching democratic consensus by having open discussion followed by a vote. </p>
+<ol>
+ <li>Proposals can be brought forth by any interested party on the fdo-psc or fdo-dev mailing lists, or in an IRC meeting. Depending on what is being proposed it may be informal (e-mail or IRC description sufficient) or based on an <a href="#rfcs">RFC</a>. After open discussion of the proposal, a motion to vote on it must be made within one week. </li>
+ <li>All voting is based on a motion made either on the fdo-psc mailing list or in an IRC meeting.
+ <ol type="a">
+ <li>If the motion is made on the mailing list a deadline of at least two working days and preferably one week must be given. </li>
+ <li>If the motion is made in an IRC meeting there must be a 2/3 quorum in attendance in order to vote. Members not present can still veto within 24 hours of the meeting minutes being posted and distributed on the fdo-psc mailing list.</li>
+ </ol>
+ </li>
+ <li value="3">PSC members can vote "+1" to indicate support for the change request and a willingness to support implementation.</li>
+ <li>PSC members can vote "-1" to veto a proposal, but must provide clear reasons and alternate approaches to solving the problem.</li>
+ <li>A "-0" vote indicates mild disagreement but has no effect, a "0" vote indicates no opinion, and a "+0" indicates mild support but has no effect. </li>
+ <li>Anyone may comment or provide input to motions, but only PSC member votes will be counted.</li>
+ <li>A motion will be accepted if it receives "+2" (including the proposer if applicable) and no veto's "-1". </li>
+ <li>If a motion is vetoed, and it cannot be revised to satisfy all parties, then it can be resubmitted for an override vote in which a majority of all PSC members must vote "+1" in order to pass it. </li>
+ <li>Upon completion of the discussion and voting the proposer should announce whether they are proceeding (motion accepted) or are withdrawing their motion (vetoed).</li>
+ <li>Addition and removal of PSC members and Project Developers is handled as a motion, however a majority vote is required in these cases. </li>
+ <li>The Chair gets a vote and is responsible for adjudicating should there be a voting dispute. </li>
+</ol>
+<h3><a name="rfcs" id="rfcs">FDO RFCs</a></h3>
+<p>RFCs are more formal documents that are required for significant technology, process, or political changes to the project. They typically include both the motivation behind the proposal and a detailed description of the change. Any interested party can write an RFC not just PSC members and developers. Once written they are posted to the project site and an announcement made to the fdo-psc mailing list. Technical RFCs should also be announced on the fdo-dev mailing list. The author should incorporate and/or respond to all comments recieved within one week and repost an updated copy of the RFC. At that point a motion can be brought to the PSC for a vote to either accept or reject the RFC. </p>
+<p>An RFC is required when:</p>
+<ul>
+ <li>Significant new features are added to the project.</li>
+ <li>Changes affect the architecture of the software or component interaction. </li>
+ <li>Changes require API, XML schema, or file format modification.</li>
+ <li>Changes may impact backward compatibility.</li>
+ <li>Changes to project policies or procedures. </li>
+ <li>Anything that establishes or effects relationships with external entities such as OSGeo. </li>
+ </ul>
+<p>An RFC is not required for bug fixes or minor enhancements that do not rework any substantial amount of code. After reading this if you are not sure whether an RFC is required or not, ask the PSC via e-mail and we will decide. </p>
+</div>
+
+<div class="h2">
+<h2><a name="responsibilities" id="responsibilities">Responsibilities</a></h2>
+<p>The PSC is responsible for all aspects of managing the FDO Open Source project including setting the overall
+ direction of the project and releases, determining what features go in and when, and how those features are implemented.
+ This section outlines the responsibilities of the PSC as a whole and responsibilities of its members.</p>
+<h3>Committee Responsibilities</h3><br />
+<em>Feature Development and Release Management</em>
+<p>The PSC is responsible for defining the project roadmap, deciding which new features and significant code changes are accepted into the project, and into which release the change will appear. Deciding what features are accepted and when is a multi-faceted decision, but the roadmap will always have a strong influence. New project features and/or functionality is proposed to the PSC via an <a href="#rfcs">RFC</a>. Once the request is submitted, the PSC uses the decision making <a href="#decisionmaking">Process</a> to decide if the change will be accepted and which release it will go into. In addition the PSC determines when a branch enters the stabilization phase and ultimately when it is ready for release. </p>
+<em>Project Policies and Procedures</em>
+<p>The PSC is responsible for defining the policies and procedures for the FDO Open Source project, including: </p>
+<ul>
+ <li>Code Reviews</li>
+ <li>Documentation Requirements</li>
+ <li>Granting and Revoking Commit Access</li>
+ <li>Testing Requirements</li>
+ <li>Branch Practice</li>
+ <li>Release Schedule (Frequency and Timing)</li>
+ <li>Version Numbering</li>
+</ul>
+<h3>Member Responsibilities</h3><br />
+<em>Guiding Development Efforts</em>
+<p>PSC members should take an active role guiding the development of new features they feel passionate about. Once a change request has been accepted and given a green light to proceed does not mean the PSC members are free of their obligation. PSC members voting "+1" for a change request are expected to to stay engaged and ensure the change is implemented and documented in a way that is most beneficial to users. Note that this applies not only to change requests that affect code, but also those that affect the web site, procedures, and policies. </p>
+<em>Weekly IRC Meeting Attendance</em>
+<p>PSC members who are also Project Developers are expected to participate in the weekly IRC development meeting. If known in advance that a member cannot attend a meeting, the member should let the other members of the fdo-dev e-mail alias know via e-mail. Continuously missing the IRC meeting may result in the member being asked to step down to make way for a more active member. Non Project Developer PSC members are expected to review the fdo-dev IRC meeting minutes. </p>
+<em>Mailing List Participation</em>
+<p>PSC members are expected to be active on both the user and developer mailing lists, subject to open source mailing list etiquette. Non-developer members of the PSC are not expected to respond to coding level questions on the developer mailing list, however they are expected to provide their thoughts and opinions on user level requirements and compatibility issues when Change Request discussions take place. </p>
+</div>
+</body>
+</html>
More information about the Fdo-commits
mailing list