Return-Path: Delivered-To: apmail-struts-commits-archive@locus.apache.org Received: (qmail 61946 invoked from network); 7 Feb 2008 05:22:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2008 05:22:24 -0000 Received: (qmail 14757 invoked by uid 500); 7 Feb 2008 05:22:15 -0000 Delivered-To: apmail-struts-commits-archive@struts.apache.org Received: (qmail 14719 invoked by uid 500); 7 Feb 2008 05:22:15 -0000 Mailing-List: contact commits-help@struts.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@struts.apache.org Delivered-To: mailing list commits@struts.apache.org Received: (qmail 14710 invoked by uid 99); 7 Feb 2008 05:22:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 21:22:15 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 05:21:54 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id ABC0A1A9832; Wed, 6 Feb 2008 21:22:01 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r619268 - in /struts/site/src/site: site.xml xdoc/dev/bylaws.xml xdoc/dev/minutes.xml xdoc/dev/site.xml xdoc/dev/volunteers.xml Date: Thu, 07 Feb 2008 05:22:00 -0000 To: commits@struts.apache.org From: husted@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20080207052201.ABC0A1A9832@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: husted Date: Wed Feb 6 21:22:00 2008 New Revision: 619268 URL: http://svn.apache.org/viewvc?rev=619268&view=rev Log: SITE-23 From charter, remove sections that overlap "How it works" and incorporate "How it works" by reference. Mention that release plans can also be posted in documentation. Add Sandbox section. Modified: struts/site/src/site/site.xml struts/site/src/site/xdoc/dev/bylaws.xml struts/site/src/site/xdoc/dev/minutes.xml struts/site/src/site/xdoc/dev/site.xml struts/site/src/site/xdoc/dev/volunteers.xml Modified: struts/site/src/site/site.xml URL: http://svn.apache.org/viewvc/struts/site/src/site/site.xml?rev=619268&r1=619267&r2=619268&view=diff ============================================================================== --- struts/site/src/site/site.xml (original) +++ struts/site/src/site/site.xml Wed Feb 6 21:22:00 2008 @@ -106,23 +106,28 @@ /> + + and the direction of the ASF Board.

- - - -

- The roles and responsibilities that people can assume in - the project - are based on merit. Everybody can help no matter what - their role. - Those who have been longterm or valuable contributors to - the project - can earn the right to commit directly to the source - repository and to - cast binding votes during the decision-making process. -

- -

- Users. - Users are the people who use the products of the Project. - People in - this role aren't contributing code, but they are using the - products, - reporting bugs, making feature requests, and such. This is - by far - the most important category of people as, without users, - there is no - reason for the Project. When a user starts to contribute - code or - documentation patches, they become a Contributor. -

- -

- Contributors. - Contributors are the people who write code or - documentation patches or - contribute positively to the project in other ways. When a - volunteer's - patch is applied, the contribution is recognized in the - version control - log. -

- -

- Committers. - Contributors who give frequent and valuable contributions - to a - subproject of the Project can have their status promoted - to that of - a " - Committer - " for that subproject. A Committer - has write access to the source code repository. Committer - status is - granted by the Project Management Committee by majority - vote. -

- -

- Project Management Committee (PMC). - Committers and other volunteers who frequently participate - with - valuable contributions may have their status promoted to - that of a - " - Project Management Committee Member - ". The PMC - is responsible for the day-to-day management of the - Project. -

- -
+ +

+ The Project Charter incorporates by reference + the current version of + + How the ASF works, with the additional guidelines + and clarifications found herein. +

@@ -184,17 +122,18 @@

+

- All Volunteers are encouraged to participate in decisions, - but the - decision itself is made by the Project Management + All + Volunteers + (Users, Developers, Committers, PMC Members) are encouraged to + participate in the + decision-making process, but binding + decisions are made only by the Project Management Committee. - The Project is a " - Minimum Threshold Meritocracy - ".

@@ -202,118 +141,15 @@

- Any subscriber to the list may vote on any issue or action - item. - Votes from Contributors and Committers are especially + Any subscriber to the list may + vote + on any issue or action item. + Votes from Developers and Committers are especially welcome. However, the only binding votes are those cast by a PMC Member.

-

- The act of voting carries certain obligations. Voters are - not only - stating their opinion, they are also agreeing to help do - the work. -

- -

Each vote can be made in one of three flavors:

- - - - - - - - - - - - - - - - - -
- +1 - - "Yes," "Agree," or "the - action should be - performed." On some issues this is only - binding if the voter - has tested the action on their own system(s). -
- +/-0 - - "Abstain," "no opinion". An - abstention may - have detrimental effects if too many people - abstain. -
- -1 - -

- "No." On issues where consensus is - required, this vote - counts as a - veto - . All vetos must contain an - explanation of why the veto is appropriate. - Vetos with no - explanation are void. A veto cannot be - overruled. If you disagree - with the veto, you should lobby the person who - cast the veto. - Voters intending to veto an action item should - make their opinions - known to the group immediately so that the - problem can be remedied - as early as possible. -

-

- If a Committer tries to "override" a veto by - restoring a vetoed - change, the PMC may ask the infrastructure - group to revoke that - Committer's write privileges. -

-
- -

- An action requiring consensus approval must receive at - least - 3 binding +1 - votes and - no binding - vetos - . An action requiring majority approval must receive - at least - 3 binding +1 - votes and more - +1 - votes than - -1 - votes. All other - action items are considered to have lazy approval until - somebody - votes - -1 - , after which point they are decided by - either consensus or majority vote, depending on the type - of action - item. -

-

- Voting represent consensus and votes are never final. - Circumstances - change, and so may votes. A veto may be converted to a +1 - after - discussion, and likewise a +1 may be converted to a -1. - By convention, Committers should allow a vote to circulate - for 72 - hours before taking action. -

@@ -329,7 +165,7 @@
  • Long Term Plans
  • Short Term Plans
  • Product Changes
  • -
  • Showstoppers
  • +
  • Showstoppers (or "blockers")
  • Release Plan
  • Release Grade
  • @@ -342,7 +178,7 @@ Long term plans are simply announcements that group members are working on particular issues related to the Project. These - are not + items are not voted on, but Committers and PMC Members who do not agree with a particular plan, or think that an alternative plan would @@ -380,12 +216,12 @@

    Showstoppers are issues that require a fix be in place before the - next public release. They are listed in the status file in - order to + next public release. They are designated as "blockers" in + the issue tracker in order to focus special attention on these problems. An issue becomes a - showstopper when it is listed as such in the status file - and remains + showstopper when it is designated as such in the issue tracker + by a PMC member and remains so by lazy consensus.

    @@ -403,8 +239,9 @@ other assorted information to keep volunteers from tripping over each other. A release - plan must be announced to the DEV list. Lazy majority - decides each issue + plan must be incorporated into the product documentation, + or otherwise announced to the DEV list. + Lazy majority decides each issue in a release plan.

    @@ -429,10 +266,39 @@

    + + + +

    + Pursuant to the + "Rules for Revolutionaries", + any committer may submit experimental material to the Sandbox area + of the repository at his or her own discretion. +

    + +

    + Material must be moved from the sandbox to the main repository before + it can be released. +

    + +

    + If a sandbox whiteboard becomes dormant for six or more months, + it may be moved to the archive section of the repository. +

    + +

    + Experimental material that is outside the scope of the Struts project + may also be submitted to the + Apache Labs. +

    + + +
    +

    Next: - Volunteers + Project Minutes

    Modified: struts/site/src/site/xdoc/dev/minutes.xml URL: http://svn.apache.org/viewvc/struts/site/src/site/xdoc/dev/minutes.xml?rev=619268&r1=619267&r2=619268&view=diff ============================================================================== --- struts/site/src/site/xdoc/dev/minutes.xml (original) +++ struts/site/src/site/xdoc/dev/minutes.xml Wed Feb 6 21:22:00 2008 @@ -835,14 +835,9 @@
    -

    - For more about volunteers at the ASF, visit - - people.apache.org. -

    Next: - Our Blogs + Volunteers

    Modified: struts/site/src/site/xdoc/dev/site.xml URL: http://svn.apache.org/viewvc/struts/site/src/site/xdoc/dev/site.xml?rev=619268&r1=619267&r2=619268&view=diff ============================================================================== --- struts/site/src/site/xdoc/dev/site.xml (original) +++ struts/site/src/site/xdoc/dev/site.xml Wed Feb 6 21:22:00 2008 @@ -47,6 +47,11 @@ href="bylaws.html" /> + + Modified: struts/site/src/site/xdoc/dev/volunteers.xml URL: http://svn.apache.org/viewvc/struts/site/src/site/xdoc/dev/volunteers.xml?rev=619268&r1=619267&r2=619268&view=diff ============================================================================== --- struts/site/src/site/xdoc/dev/volunteers.xml (original) +++ struts/site/src/site/xdoc/dev/volunteers.xml Wed Feb 6 21:22:00 2008 @@ -1471,7 +1471,7 @@

    Next: - Project Minutes + Our Blogs