Return-Path: Delivered-To: apmail-geronimo-scm-archive@www.apache.org Received: (qmail 1439 invoked from network); 25 Jul 2006 01:37:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2006 01:37:29 -0000 Received: (qmail 15394 invoked by uid 500); 25 Jul 2006 01:37:28 -0000 Delivered-To: apmail-geronimo-scm-archive@geronimo.apache.org Received: (qmail 14895 invoked by uid 500); 25 Jul 2006 01:37:26 -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 14814 invoked by uid 99); 25 Jul 2006 01:37:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2006 18:37:26 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2006 18:37:20 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id 0478F1A9825; Mon, 24 Jul 2006 18:37:00 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r425251 [5/10] - in /geronimo/site/trunk: docs/ docs/images/ xdocs/ xdocs/images/ xdocs/stylesheets/ Date: Tue, 25 Jul 2006 01:36:55 -0000 To: scm@geronimo.apache.org From: jdillon@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20060725013700.0478F1A9825@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Modified: geronimo/site/trunk/docs/guidelines.html URL: http://svn.apache.org/viewvc/geronimo/site/trunk/docs/guidelines.html?rev=425251&r1=425250&r2=425251&view=diff ============================================================================== --- geronimo/site/trunk/docs/guidelines.html (original) +++ geronimo/site/trunk/docs/guidelines.html Mon Jul 24 18:36:54 2006 @@ -1,366 +1,278 @@ - - - - - - - - + + - - - - - - - - - - Apache Geronimo - + + + + + + + + Apache Geronimo + - + - - - - - - - - - - - + + + + + + + + + + +
- - -   - - - - - - - - - - - - - -
+ + +   + + + + + + + + + + + + +
- - - - - - - - - - + + + + + + + +
- - - - - - - - - - - - - -   -
+ + + + + + + + + + +   +
- + - - +
+ - - + - - - - - - - -
- - - + +
- - - + + + + +
+ + + + - -
+ + + - - - - - - - -
-  Quick Links +  Quick Links -
- - -     Home -
- -     License -
- -     ASF -
- -     Downloads -
- -
-
+
+     Home +
+     License +
+     ASF +
+     Downloads +
+
+
- - - - + +
- - - + + + + +
+ + + - -
+ + + - - - - - - - -
-  Community +  Community -
- - -     Events -
- -     Get Involved -
- -     Committers -
- -     Mailing Lists -
- -     Powered By -
- -     Documentation -
- -     FAQ -
- -     Wiki -
- -     Found a Bug? -
- -
-
+
+     Events +
+     Get Involved +
+     Committers +
+     Mailing Lists +
+     Powered By +
+     Documentation +
+     FAQ +
+     Wiki +
+     Found a Bug? +
+
+
- - - - + +
- - - + + + + +
+ + + - -
+ + + - - - - - - - -
-  Development +  Development -
- - -     Javadoc -
- -     XML Schemas -
- -     Source Code -
- -     Coding Standards -
- -     JIRA -
- -     Related Projects -
- -
-
+
+     Javadoc +
+     XML Schemas +
+     Source Code +
+     Coding Standards +
+     JIRA +
+     Related Projects +
+
+
- - - - + +
- - - + + + + +
+ + + - -
+ + + - - - - - - - -
-  Subprojects +  Subprojects -
- - -     Development Tools -
- -     GBuild -
- -     XBean -
- -
-
+
+     Development Tools +
+     GBuild +
+     XBean +
+
+
+ 		- - - - - - +
-
- Project Guidelines -
- -

-

+

+ + + + + + - - - - -
+
+ 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 +

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 -
- -

-

+

+
+
+
+ + + + + + - - - - -
+
+ 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 @@ -419,28 +331,26 @@
- -

-
-
-
- - - - - - + + + + +
-
- 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 @@ -449,34 +359,32 @@ 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 +

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. +

+
+
+
+ + + + + + - - - - -
+
+ 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 @@ -485,15 +393,15 @@ 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 +

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:

-
+

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 @@ -514,7 +422,7 @@ 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 @@ -523,30 +431,28 @@ 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 +

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 -
- -

-

+

+
+
+
+ + + + + + - - - - -
+
+ 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. @@ -614,35 +520,33 @@ 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 @@ -651,168 +555,142 @@ 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 +

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 +

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 +

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 +

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 +

+
+
+
+ + + + + + - - - - -
+
+ 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 +

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 + 

    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 +

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

-
    + 
        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-2006, The Apache Software Foundation   -
-
- - - - - - + + + + + + + + + + +
+
+ Copyright © 2003 - 2006, The Apache Software Foundation   +
+
+ + + + - - - - - - - - - - - Modified: geronimo/site/trunk/docs/index.html URL: http://svn.apache.org/viewvc/geronimo/site/trunk/docs/index.html?rev=425251&r1=425250&r2=425251&view=diff ============================================================================== --- geronimo/site/trunk/docs/index.html (original) +++ geronimo/site/trunk/docs/index.html Mon Jul 24 18:36:54 2006 @@ -1,353 +1,267 @@ - - - - - - - - + + - - - - - - - - - - Apache Geronimo - + + + + + + + + Apache Geronimo + - + - - - - - - - - - - - + + + + + + + + + + +
- - -   - - - - - - - - - - - - - -
+ + +   + + + + + + + + + + + + +
- - - - - - - - - - + + + + + + + +
- - - - - - - - - - - - - -   -
+ + + + + + + + + + +   +
- + - - +
+ - - + - - - - - - - -
- - - + +
- - - + + + + +
+ + + + - -
+ + + - - - - - - - -
-  Quick Links +  Quick Links -
- - -     Home -
- -     License -
- -     ASF -
- -     Downloads -
- -
-
+
+     Home +
+     License +
+     ASF +
+     Downloads +
+
+
- - - - + +
- - - + + + + +
+ + + - -
+ + + - - - - - - - -
-  Community +  Community -
- - -     Events -
- -     Get Involved -
- -     Committers -
- -     Mailing Lists -
- -     Powered By -
- -     Documentation -
- -     FAQ -
- -     Wiki -
- -     Found a Bug? -
- -
-
+
+     Events +
+     Get Involved +
+     Committers +
+     Mailing Lists +
+     Powered By +
+     Documentation +
+     FAQ +
+     Wiki +
+     Found a Bug? +
+
+
- - - - + +
- - - + + + + +
+ + + - -
+ + + - - - - - - - -
-  Development +  Development -
- - -     Javadoc -
- -     XML Schemas -
- -     Source Code -
- -     Coding Standards -
- -     JIRA -
- -     Related Projects -
- -
-
+
+     Javadoc +
+     XML Schemas +
+     Source Code +
+     Coding Standards +
+     JIRA +
+     Related Projects +
+
+
- - - - + +
- - - + + + + +
+ + + - -
+ + + - - - - - - - -
-  Subprojects +  Subprojects -
- - -     Development Tools -
- -     GBuild -
- -     XBean -
- -
-
+
+     Development Tools +
+     GBuild +
+     XBean +
+
+
+ 		- - - - - - +
-
- Welcome to Apache Geronimo -
- -

-

+

+ + + + + + + + + + +
+
+ Welcome to Apache Geronimo +
+

+

Welcome to Apache Geronimo, the J2EE server project of the Apache Software Foundation. Please help us make this a world class, certified J2EE container!

-

+

The aim of the project is to produce a large and healthy community of J2EE developers tasked with the development of an open-source, certified J2EE server that:

-
    +
    • is licensed under the Apache License
    • passes Sun's TCK for J2EE 1.4
    • reuses the best ASF/BSD licensed code available today, with new ASF code to complete the J2EE stack.
    - - - - - - - - - - + + + + + + + +
    - Geronimo News -
    -
    -
    -

    + + + + + + - - - - -
    + Geronimo News +
    +
    +
    +

    2006-07-18
    Geronimo Eclipse Plugin Version 1.1.0 is now Available

    @@ -357,8 +271,7 @@

    - -

    +

    2006-06-26
    Geronimo 1.1 Released and Available

    @@ -370,8 +283,7 @@

    - -

    +

    2006-02-23
    Geronimo Eclipse Plugin Version 1.0.0 is now Available

    @@ -380,8 +292,7 @@

    - -

    +

    2006-02-17
    Covalent Extends Support Offerings for Apache Geronimo

    @@ -389,8 +300,7 @@

    - -

    +

    2006-01-05
    Geronimo Version 1.0 is now Available

    @@ -398,85 +308,63 @@

    - -
    -
    -
    -
    - - -

    -
    -
    -
    +
    +
    + +

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