From scm-return-10477-apmail-geronimo-scm-archive=geronimo.apache.org@geronimo.apache.org Mon Feb 13 19:43:19 2006 Return-Path: Delivered-To: apmail-geronimo-scm-archive@www.apache.org Received: (qmail 90088 invoked from network); 13 Feb 2006 19:43:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Feb 2006 19:43:16 -0000 Received: (qmail 35028 invoked by uid 500); 13 Feb 2006 19:43:12 -0000 Delivered-To: apmail-geronimo-scm-archive@geronimo.apache.org Received: (qmail 34743 invoked by uid 500); 13 Feb 2006 19:43:10 -0000 Mailing-List: contact scm-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list scm@geronimo.apache.org Received: (qmail 34193 invoked by uid 99); 13 Feb 2006 19:43:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2006 11:43:07 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 13 Feb 2006 11:42:57 -0800 Received: (qmail 89659 invoked by uid 65534); 13 Feb 2006 19:42:36 -0000 Message-ID: <20060213194236.89657.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r377474 [3/8] - in /geronimo/site: ./ docs/ docs/devtools/ xdocs/ xdocs/stylesheets/ Date: Mon, 13 Feb 2006 19:42:29 -0000 To: scm@geronimo.apache.org From: bsnyder@apache.org X-Mailer: svnmailer-1.0.6 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Modified: geronimo/site/docs/faq.html URL: http://svn.apache.org/viewcvs/geronimo/site/docs/faq.html?rev=377474&r1=377473&r2=377474&view=diff ============================================================================== --- geronimo/site/docs/faq.html (original) +++ geronimo/site/docs/faq.html Mon Feb 13 11:42:25 2006 @@ -1,147 +1,243 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Apache Geronimo - Apache Geronimo - Frequently Asked Questions - - - - - - - - - -
- -Apache Geronimo -
- - - - - - - + +
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -

Subprojects

- - 		- - - + + + + +
- - General - -
-
-

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + Apache Geronimo + + + + + + + + + + + + + + + + +
+ + +   + + + + + + + + + + + + + +
+ + + + + + + + + + + +
+ + + + + + + + + + + + + +   +
+ + + + + + + + + + + + + - - - - - -
+ + + + + + + + + + + +
+ + Quick Links + +
+ +
+ + + + + + + + + + + + +
+ + Community + +
+ +
+ + + + + + + + + + + + +
+ + Development + +
+ +
+ + + 		+ + + + + + - -
+
+ General +
+ +

+

What is Geronimo?

Geronimo is Apache's ASF-licensed J2EE server project. Please see the Overview for more information.
-

-

+

+

I'd like to find out more about the project and possibly contribute. What do I do next? @@ -155,8 +251,8 @@ If you want to help, just join the mailing list, see what needs to be done, and do it. Welcome! -

-

+

+

Where is the mailing list, and how can I subscribe? @@ -174,8 +270,8 @@ mailing list archive. -

-

+

+

Does this project use a wiki?

@@ -186,45 +282,75 @@ visit the recent changes page.
-

- -

-

-
-
-
-
- Copyright © 2003-2005, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - +

+ +

+
+
+
+
+ + + + + + + + + + + + + + + + + + +
+
+ Copyright © 2003-2006, The Apache Software Foundation   +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Modified: geronimo/site/docs/get-involved.html URL: http://svn.apache.org/viewcvs/geronimo/site/docs/get-involved.html?rev=377474&r1=377473&r2=377474&view=diff ============================================================================== --- geronimo/site/docs/get-involved.html (original) +++ geronimo/site/docs/get-involved.html Mon Feb 13 11:42:25 2006 @@ -1,145 +1,241 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Apache Geronimo - Apache Geronimo - - - - - - - - - -
- -Apache Geronimo -
- - - - - - - + +
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -

Subprojects

- - 		- - - + + + + +
- - How do I contribute, give feedback, fix bugs and so on? - -
-
-

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + Apache Geronimo + + + + + + + + + + + + + + + + +
+ + +   + + + + + + + + + + + + + +
+ + + + + + + + + + + +
+ + + + + + + + + + + + + +   +
+ + + + + + + + + + + + + - - - - - -
+ + + + + + + + + + + +
+ + Quick Links + +
+ +
+ + + + + + + + + + + + +
+ + Community + +
+ +
+ + + + + + + + + + + + +
+ + Development + +
+ +
+ + + 		+ + + + + + - -
+
+ How do I contribute, give feedback, fix bugs and so on? +
+ +

+

The Apache Geronimo project really needs and appreciates any contributions, including documentation help, source code and feedback. Suggested changes should come in the form of source code and/or very detailed and constructive feedback. -

-
    +

    +
    • Discussion occurs on the Geronimo mailling lists
      • @@ -165,45 +261,75 @@ Additional documentation and discussion can be found on the project wiki -
    - -

    -

-
-
-
-
- Copyright © 2003-2005, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - + + +

+
+
+
+
+ + + + + + + + + + + + + + + + + + +
+
+ Copyright © 2003-2006, The Apache Software Foundation   +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Modified: geronimo/site/docs/guidelines.html URL: http://svn.apache.org/viewcvs/geronimo/site/docs/guidelines.html?rev=377474&r1=377473&r2=377474&view=diff ============================================================================== --- geronimo/site/docs/guidelines.html (original) +++ geronimo/site/docs/guidelines.html Mon Feb 13 11:42:25 2006 @@ -1,168 +1,272 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Apache Geronimo - Apache Geronimo - Project Guidelines - - - - - - - - - -
- -Apache Geronimo -
- - - - - - - + +
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -

Subprojects

- - 		- - - + + + + +
- - Project Guidelines - -
-
-

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + Apache Geronimo + + + + + + + + + + + + + + + + +
+ + +   + + + + + + + + + + + + + +
+ + + + + + + + + + + +
+ + + + + + + + + + + + + +   +
+ + + + + + + + + + + + + - - - - - -
+ + + + + + + + + + + +
+ + Quick Links + +
+ +
+ + + + + + + + + + + + +
+ + Community + +
+ +
+ + + + + + + + + + + + +
+ + Development + +
+ +
+ + + 		+ + + + + + - -
+
+ Project Guidelines +
+ +

+

NOTE : The following guidelines are PROPOSED for discussion only. They will need to be discussed by the Geronimo community and a final version approved by a vote by the Apache Geronimo PMC. These guidelines were adopted from the Apache HTTPD project. -

-

This document defines the guidelines for the +

+

This document defines the guidelines for the Apache Geronimo Project. It includes definitions of how conflict is resolved by voting, who is able to vote, and the procedures to follow for proposing and -making changes to the Apache products.

-

The objective here is to avoid unnecessary conflict over changes and +making changes to the Apache products.

+

The objective here is to avoid unnecessary conflict over changes and continue to produce a quality system in a timely manner. Not all conflict can be avoided, but at least we can agree on the procedures for conflict -to be resolved.

- -

-

- - - + + + + +
- - People, Places, and Things - -
-
-
+to be resolved.

+ +

+
+
+
+ + + + + + - -
+
+ People, Places, and Things +
+ +

+

Apache Geronimo Project Management Committee
The group of volunteers who are responsible for managing the Apache Geronimo Project. This includes deciding what is distributed @@ -220,21 +324,29 @@ mail lists for the project.
-
- -

-

- - - + + + + +
- - STATUS - -
-
-

Each of the Apache Geronimo's active source code repositories contain a + + +

+
+
+
+ + + + + + - -
+
+ STATUS +
+ +

+

Each of the Apache Geronimo's active source code repositories contain a file called "STATUS" which is used to keep track of the agenda and plans for work within that repository. The STATUS file includes information about release plans, a summary of code changes committed since the last @@ -242,27 +354,35 @@ notes about items that individual developers are working on or want discussion about, and anything else that might be useful to help the group track progress. The active STATUS files are automatically posted -to the mailing list each week.

-

Many issues will be encountered by the project, each resulting in +to the mailing list each week.

+

Many issues will be encountered by the project, each resulting in zero or more proposed action items. Issues should be raised on the mailing list as soon as they are identified. Action items must be raised on the mailing list and added to the relevant STATUS file. All action items may be voted on, but not all -of them will require a formal vote.

- -

-

- - - + + + + +
- - Voting - -
-
-

Any of the Apache Developers may vote on any issue or action item. +of them will require a formal vote.

+ +

+
+
+
+ + + + + + - -
+
+ Voting +
+ +

+

Any of the Apache Developers may vote on any issue or action item. However, the only binding votes are those cast by active members of the Apache Geronimo PMC; if the vote is about a change to source code or documentation, the primary author of what is being changed may also @@ -270,16 +390,16 @@ All developers are encouraged to participate in decisions, but the decision itself is made by those who have been long-time contributors to the project. In other words, the Apache Geronimo Project is a -minimum-threshold meritocracy.

-

The act of voting carries certain obligations -- voting members are +minimum-threshold meritocracy.

+

The act of voting carries certain obligations -- voting members are not only stating their opinion, they are agreeing to help do the work of the Apache Geronimo Project. Since we are all volunteers, members often become inactive for periods of time in order to take care of their "real jobs" or devote more time to other projects. It is therefore unlikely that the entire group membership will vote on every issue. To account for this, -all voting decisions are based on a minimum quorum.

-

Each vote can be made in one of three flavors:

-
+all voting decisions are based on a minimum quorum.

+

Each vote can be made in one of three flavors:

+
+1
Yes, agree, or the action should be performed. On some issues, this vote is only binding if the voter has tested the action on @@ -299,8 +419,8 @@ an action item should make their opinions known to the group immediately, so that the problem can be remedied as early as possible.
-
-

An action item requiring consensus approval must receive +

+

An action item requiring consensus approval must receive at least 3 binding +1 votes and no vetos. An action item requiring majority approval must receive at least 3 binding +1 votes and more +1 @@ -308,23 +428,31 @@ quorum of three positive votes). All other action items are considered to have lazy approval until someone votes -1, after which point they are decided by either consensus or a majority vote, -depending upon the type of action item.

-

Votes are tallied within the STATUS file, adjacent to the action -item under vote. All votes must be sent to the mailing list.

- -

-

- - - + + + + +
- - Types of Action Items - -
-
-
+depending upon the type of action item.

+

Votes are tallied within the STATUS file, adjacent to the action +item under vote. All votes must be sent to the mailing list.

+ +

+
+
+
+ + + + + + - -
+
+ Types of Action Items +
+ +

+

Long Term Plans
Long term plans are simply announcements that group members are working on particular issues related to the Apache software. @@ -391,28 +519,36 @@ to lazy consensus. All product changes to a prior-branch (old version) repository require consensus before the change is committed.

-
- -

-

- - - + + + + +
- - When to Commit a Change - -
-
-

Ideas must be review-then-commit; patches can be commit-then-review. + + +

+
+
+
+ + + + + + - -
+
+ When to Commit a Change +
+ +

+

Ideas must be review-then-commit; patches can be commit-then-review. With a commit-then-review process, we trust that the developer doing the commit has a high degree of confidence in the change. Doubtful changes, new features, and large-scale overhauls need to be discussed before being committed to a repository. Any major change must receive consensus approval on the mailing list before being committed. -

-

Each developer is responsible for notifying the mailing list and +

+

Each developer is responsible for notifying the mailing list and adding an action item to STATUS when they have an idea for a new feature or major change to propose for the product. The distributed nature of the Apache project requires an advance notice of 48 hours in order to properly @@ -420,123 +556,169 @@ specific patch is required before the change can be committed. Note that a committer might veto the concept (with an adequate explanation), but later rescind that veto if a specific patch satisfies their objections. -No advance notice is required to commit singular bug fixes.

-

Related changes should be committed as a group, or very closely +No advance notice is required to commit singular bug fixes.

+

Related changes should be committed as a group, or very closely together. Half-completed projects should not be committed unless doing so is necessary to pass the baton to another developer who has agreed to complete the project in short order. All code changes must be successfully compiled on the developer's platform before being -committed.

-

The current source code tree should be capable of complete compilation +committed.

+

The current source code tree should be capable of complete compilation at all times. However, it is sometimes impossible for a developer on one platform to avoid breaking some other platform when a change is committed, particularly when completing the change requires access to a special development tool on that other platform. If it is anticipated that a given change will break some other platform, the committer must -indicate that in the commit log.

-

The committer is responsible to follow the Apache Geronimo procedure +indicate that in the commit log.

+

The committer is responsible to follow the Apache Geronimo procedure for any third-party code or documentation they commit to the repository. All software committed to the repository must be covered by the Apache LICENSE or contain a copyright and license that allows redistribution under the same conditions -as the Apache LICENSE.

-

A committed change must be reversed if it is vetoed by one of the +as the Apache LICENSE.

+

A committed change must be reversed if it is vetoed by one of the voting committers and the veto conditions cannot be immediately satisfied by the equivalent of a "bug fix" commit. The veto must be rescinded before -the change can be included in any public release.

- -

-

- - - + + + + +
- - Patch Format - -
-
-

When a specific change to the software is proposed for discussion or +the change can be included in any public release.

+ +

+
+
+
+ + + + + + - -
+
+ Patch Format +
+ +

+

When a specific change to the software is proposed for discussion or voting on the mailing list, it should be presented in the form of input to the patch command. When sent to the mailing list, the message should contain a Subject beginning with [PATCH] and a distinctive one-line summary corresponding to the action item for that patch. Afterwords, the patch summary in the STATUS file should be -updated to point to the Message-ID of that message.

-

The patch should be created by using the diff -u +updated to point to the Message-ID of that message.

+

The patch should be created by using the diff -u command from the original software file(s) to the modified software -file(s). E.g.,

- 
    diff -u http_main.c.orig http_main.c >> patchfile.txt
-

or

- 
    cvs diff -u http_main.c >> patchfile.txt
-

All patches necessary to address an action item should be concatenated +file(s). E.g.,

+ 
    diff -u http_main.c.orig http_main.c >> patchfile.txt
+

or

+ 
    cvs diff -u http_main.c >> patchfile.txt
+

All patches necessary to address an action item should be concatenated within a single patch message. If later modification of the patch proves necessary, the entire new patch should be posted and not just the difference between two patches. The STATUS file entry should then -be updated to point to the new patch message.

-

The completed patchfile should produce no errors or prompts when the -command,

- 
    patch -s < patchfile
-

is issued in the target repository.

- -

-

- - - + + + + +
- - Addendum - -
-
-

Outstanding issues with this document

-
    +be updated to point to the new patch message.

    +

    The completed patchfile should produce no errors or prompts when the +command,

    + 
        patch -s < patchfile
    +

    is issued in the target repository.

    + +

    +
+
+
+ + + + + + - -
+
+ Addendum +
+ +

+

Outstanding issues with this document

+
  • We may need a better definition for "lazy consensus".
  • We should clarify under what conditions a veto can be rescinded or overridden.
  • Should we set a time limit on vetos of patches? Two weeks?
    • -
- -

-

-
-
-
-
- Copyright © 2003-2005, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - + + +

+
+
+
+
+ + + + + + + + + + + + + + + + + + +
+
+ Copyright © 2003-2006, The Apache Software Foundation   +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +