You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by mc...@apache.org on 2003/10/26 15:42:09 UTC
cvs commit: avalon-sandbox/mavenized-site/xdocs/platform navigation.xml
mcconnell 2003/10/26 06:42:09
Modified: mavenized-site/xdocs navigation.xml news.xml
mavenized-site/xdocs/community navigation.xml
mavenized-site/xdocs/community/history navigation.xml
mavenized-site/xdocs/community/who navigation.xml
mavenized-site/xdocs/components navigation.xml
mavenized-site/xdocs/containers navigation.xml
mavenized-site/xdocs/platform navigation.xml
Added: mavenized-site/xdocs/community/process code-standards.xml
development.xml index.xml mission.xml
navigation.xml patches.xml pmc-votes.xml pmc.xml
release.xml
Removed: mavenized-site/xdocs mission.xml
mavenized-site/xdocs/community code-standards.xml
development.xml patches.xml pmc-votes.xml pmc.xml
release.xml
Log:
CLeaning-up the community section - small restructuring and improved navigation.
Revision Changes Path
1.2 +3 -4 avalon-sandbox/mavenized-site/xdocs/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/navigation.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- navigation.xml 25 Oct 2003 20:50:43 -0000 1.1
+++ navigation.xml 26 Oct 2003 14:42:08 -0000 1.2
@@ -15,10 +15,9 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html"/>
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html"/>
</menu>
<menu name="Products">
1.3 +5 -9 avalon-sandbox/mavenized-site/xdocs/news.xml
Index: news.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/news.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- news.xml 26 Oct 2003 12:58:49 -0000 1.2
+++ news.xml 26 Oct 2003 14:42:08 -0000 1.3
@@ -5,18 +5,17 @@
<title>Apache Avalon</title>
</properties>
<body>
+
<section name="News and Information">
- <table>
- <tr>
- <td>
-<p><b>26-SEP-2003: Merlin 3.0 beta 1</b></p>
+ <subsection name="26-SEP-2003: Merlin 3.0 beta 1">
+
<p>The Avalon Team is proud to announce the release of Merlin 3.0 Beta 1. Merlin is an advanced component and service management solution that simplifies and enhances component development, assembly and service deployment concerns.</p>
<p>Merlin 3.0 binaries can be downloaded from the following site:</p>
<p><a href="http://www.apache.org/dist/avalon/merlin/binaries/">http://www.apache.org/dist/avalon/merlin/binaries/</a></p>
-<p><b>Key Product Features:</b></p>
+<p>Key Product Features:</p>
<ul>
<li>auto assembly</li>
<li>muli-layer configuration management</li>
@@ -32,10 +31,7 @@
</ul>
<p>Product documentation, tutorials and specifications are available on the <a href="http://avalon.apache.org/merlin">Merlin Home</a> site or the download link referenced above.</p>
-
- </td>
- </tr>
- </table>
+ </subsection>
</section>
</body>
</document>
1.2 +5 -13 avalon-sandbox/mavenized-site/xdocs/community/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/community/navigation.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- navigation.xml 25 Oct 2003 20:50:44 -0000 1.1
+++ navigation.xml 26 Oct 2003 14:42:08 -0000 1.2
@@ -15,20 +15,12 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html">
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html">
<item name="Who We Are" href="/community/who/index.html"/>
- <item name="Project Charter" href="/mission.html"/>
- <item name="Project History" href="/community/history/index.html"/>
- <item name="PMC" href="/community/pmc.html"/>
- <item name="PMC Voting Process" href="/community/pmc-votes.html"/>
- <item name="Development Process" href="/community/development.html">
- <item name="Coding Standards" href="/community/code-standards.html"/>
- <item name="Release Management" href="/community/release.html"/>
- <item name="Patches and Bugs" href="/community/patches.html"/>
- </item>
+ <item name="Process" href="/community/process/index.html"/>
+ <item name="History" href="/community/history/index.html"/>
</item>
</menu>
1.2 +7 -15 avalon-sandbox/mavenized-site/xdocs/community/history/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/community/history/navigation.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- navigation.xml 25 Oct 2003 20:50:44 -0000 1.1
+++ navigation.xml 26 Oct 2003 14:42:08 -0000 1.2
@@ -15,23 +15,15 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html">
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html">
<item name="Who We Are" href="/community/who/index.html"/>
- <item name="Project Charter" href="/mission.html"/>
- <item name="Project History" href="/community/history/index.html">
+ <item name="Process" href="/community/process/index.html"/>
+ <item name="History" href="/community/history/index.html">
<item name="Call To Vote" href="/community/history/call-to-vote.html"/>
- <item name="Need For Avalon" href="/community/history/need-for-avalon.html"/>
- <item name="What is a Server?" href="/community/history/what-is-a-server.html"/>
- </item>
- <item name="PMC" href="/community/pmc.html"/>
- <item name="PMC Voting Process" href="/community/pmc-votes.html"/>
- <item name="Development Process" href="/community/development.html">
- <item name="Coding Standards" href="/commmunity/code-standards.html"/>
- <item name="Release Management" href="/community/release.html"/>
- <item name="Patches and Bugs" href="/community/patches.html"/>
+ <item name="Need For Avalon" href="/community/history/need-for-avalon.html"/>
+ <item name="What is a Server?" href="/community/history/what-is-a-server.html"/>
</item>
</item>
</menu>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/code-standards.xml
Index: code-standards.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Coding Standards</title>
</properties>
<body>
<section name="Coding Standards">
<p>This document describes a list of coding conventions that are required
for code submissions to the project. By default, the coding conventions
for most Open Source projects should follow the existing coding conventions
in the code that you are working on. For example, if the bracket is on
the same line as the if statement, then you should write all your code
to follow that convention.</p>
<p><strong>Please follow these conventions closely. It makes life so much
easier.</strong></p>
<p>Brackets should begin and end on a new line. Examples:</p>
<source>
if( foo )
{
// code here
}
try
{
// code here
}
catch( final Exception bar )
{
// code here
}
finally
{
// code here
}
while( true )
{
// code here
}
</source>
<p>The preference is to include extra spaces between parenthesis and expression.
For example;
</p>
<source>
if( foo )
</source>
<p>4 spaces. <strong>NO</strong> tabs. Period. We understand that a lot of you like
to use tabs, but the fact of the matter is that in a distributed development
environment, when the cvs commit messages get sent to a mailing list, they
are almost impossible to read if you use tabs.</p>
<p>In Emacs-speak, this translates to the following command:</p>
<source>(setq-default tab-width 4 indent-tabs-mode nil)</source>
<p>In vim, having the following in your .vimrc will help:</p>
<source>
set tabstop=4
set expandtab
set list
set listchars=tab:>.
</source>
<p>Unix linefeeds for all .java source code files. Other platform specific
files should have the platform specific linefeeds.</p>
<p>Javadoc <strong>SHOULD</strong> exist on all your methods. Also, if you are working
on existing code and there currently isn't a javadoc for that method/class/variable
or whatever, then you should contribute and add it. This will improve the
project as a whole.</p>
<p>The Jakarta Apache/Avalon License <strong>MUST</strong> be placed at the top
of each and every file.</p>
<p>If you contribute to a file (code or documentation), add yourself to the
top of the file. For .java files the preferred Javadoc format is:</p>
<source>
@author <a href="mailto:user@domain.com">John Doe</a>
</source>
<p>Indent comments on an 80 column basis and the code on a
100 column basis, using two more indents when a line must be wrapped.</p>
<p>We focus on readability over performance, at least initially. Source code
optimization is the last thing to be done to increase performance.
If the code is not performing then it is better to re-engineer it rather
than to expand loops, take out variable declarations etc. When the code
is stable and has a well defined purpose and interface it may be appropriate
to do source code optimization.</p>
<p>Try to javadoc all methods and variables, especially public, protected
and default access methods and member variables. Also add code comments
when you think it's necessary (like assumptions).</p>
<p>Variables are declared in the inner scope.</p>
<source>
while( myListIterator.hasNext() )
{
final String myString = (String)myListIterator.next();
}
</source>
<p>Variables should be descriptive and ideally English words. The exceptions
being loop counters (usually use i, j and k), exceptions (use concatenation
of word separating characters - i.e. SocketException is abbreviated as se) and
other commonly used abbreviations (i.e. sb for StringBuffer).</p>
<source>
try
{
for( int i = 0; i < 10; i++ )
{
// some stuff
}
}
catch( final FileNotFoundException fnfe )
{
// some stuff
}
catch( final IndexOutOfBoundsException ioobe )
{
// some stuff
}
</source>
<p>
Use String concatenation except in extremely performance sensitive
sections. This leaves StringBuffer optimization to the compiler.
So use:</p>
<source>
final String myString = "test " + "for " + "performances";
</source>
<p>Try not to declare a method as 'synchronized'. If a method accesses
a shared resource then surround accesses to that resource with
a synchronized block. Ideally the synchronized block should surround
the smallest possible area. For example:</p>
<source>
public void sharedMethod()
{
String display = null;
synchronized( this )
{
display = mySharedObject.getHelloWorld();
}
System.out.println( display );
}
</source>
<p>If you are within a static method, then you may have to create
a static object whose sole purpose in life is to provide the
lock you need. Alternatively you could use the Class object for
the class you are in. That is, if you're in class MyClass, use
"MyClass.class".</p>
<p>Have the names of all member instance fields start with the prefix "m_".
Example:</p>
<source>
class MyClass
{
Class m_class = MyClass.class;
int m_users;
}
</source>
<p>Don't chain method calls. The below:</p>
<source>
Thing thing = (MyThing)myObject.doSomething().doSomethingElse().getMyThing();
</source>
<p>is considered bad practice because it hides problems relating to
synchronization, resource management, etc. The example above might
become:</p>
<source>
final MySomething something = myObject.doSomething();
final MyElse somethingElse = something.doSomethingElse();
Thing thing = somethingElse.getMyThing();
</source>
<p>The extra typing will help keep the code bug-free.</p>
<p>Thanks for your cooperation.</p>
<p>-The Avalon Team</p>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/development.xml
Index: development.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Apache Avalon</title>
</properties>
<body>
<section name="Avalon Development Process">
<p>
The following documents describe the development practices in
use by the Avalon community. When contributing to the project,
please follow these guidelines.
</p>
<ul>
<li><a href="code-standards.html">Coding Standards</a></li>
<li><a href="release.html">Release Guidelines</a></li>
<li><a href="patches.html">Patch Policies</a></li>
</ul>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/index.xml
Index: index.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Apache Avalon: Community</title>
</properties>
<body>
<section name="The Avalon Community">
<p>
Welcome to the Avalon community!
</p>
<p>
Avalon, like all other projects at Apache, is a
<em>meritocracy</em> and follows the <em>Apache Way</em> of
community and project management. The following documents
help define these terms and form the guidelines by which Avalon operates.
</p>
<ul>
<li><a href="http://jakarta.apache.org/site/decisions.html">
Meritocracy</a></li>
<li><a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheWay">
The Apache Way</a></li>
<li><a href="http://jakarta.apache.org/site/roles.html">Roles
and Responsibilities</a></li>
<li><a href="http://jakarta.apache.org/site/guidelines.html">
Jakarta Project Guidelines</a></li>
<li><a href="http://incubator.apache.org/index.html">
The Apache Incubator Project</a></li>
<li><a href="http://apache.org/foundation/">The Apache Software
Foundation</a> (ASF)</li>
<li><a
href="http://incubator.apache.org/forms/ASF_Contributor_License_2_form.pdf">
Contributor license Agreement</a> [PDF]</li>
<li><a href="http://james.apache.org/contribute.html">Getting Involved</a></li>
</ul>
</section>
<section name="Opening up Avalon's Repositories">
<p>
Avalon continually looks at ways to cooperate better with
other projects, especially here at Apache. Recently, the
Avalon team decided to open up the "avalon-excalibur"
repository to the Apache Cocoon community. The response has
been favorable as the libraries there now have a wider group
of supporting developers. As a result, the Avalon team decided
to take this process one step further and open up the
"avalon-components" repository to both the Apache Cocoon and
Apache JAMES projects.
</p>
<p>
If you are from another Apache project, and would like all the
committers from your project to have access to the Avalon
Repositories, all you need to do is ask the Avalon PMC
(pmc@avalon.apache.org). The repositories that are available
for wider access are:
</p>
<ul>
<li>avalon-components</li>
<li>avalon-excalibur</li>
<li>avalon-sandbox</li>
</ul>
<p>
The PMC will let you know if your request is accepted or
not. If you are interested in commit privileges, but are not
part of one of the Apache projects, then you have to do it
the old fashioned way and participate on the mailing lists
and post patches, etc. We are taking advantage of the Apache
infrastructure to make this happen.
</p>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/mission.xml
Index: mission.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Apache Avalon: Mission</title>
</properties>
<body>
<section name="Apache Avalon Mission">
<source>
Apache Avalon is a collaborative software development project dedicated
to providing a high-quality freely available component architecture
according to the principles of the Apache Software Foundation [ASF].
This charter briefly describes the mission, history, organization, and
processes of the Apache Avalon project.
MISSION
=======
Apache Avalon exists to promote and facilitate Component Based Design.
Component Based Design is a proven practice that helps create systems
that are loosely coupled and easy to maintain. Component Based Design
requires a rigid software framework to function properly.
Apache Avalon provides a specification for such a framework, an
implementation of that specification and a compliance testing suite,
and tools and components to facilate development using that framework.
The software developed by the Apache Avalon project must be high
performance, reliable, secure, and easy to use. The individual software
components must be part of an underlying architectural orchestration
that will allow them to work together without major negotiations or
breakage.
The process followed for the development of Apache Avalon software is
the same as the process followed by other ASF projects: individuals and
corporations collaborate on the best possible infrastructure, APIs,
code, testing, and release cycles.
In order to achieve a coherent architecture between Apache Avalon
components and other components and applications, standards (formal or
de facto) will be used as much as possible for both protocols and APIs.
We will also allow the innovation of new protocols, APIs, and components
in order to seed new concepts not yet defined by standards.
HISTORY
=======
This project was established under the direction of the Apache Software
Foundation in November 2002 to facilitate joint open-source development.
Prior to November 2002, Apache Avalon has been a part of the Apache Java
project and the Apache Jakarta project.
THE PROJECT MANAGEMENT COMMITTEE
================================
The Apache Avalon project is managed by a small, core group of
contributors known as the Project Management Committee [PMC]. The PMC
must have at least one ASF Officer, who will also be the PMC Chairperson
and who will report to the ASF Board. See
http://www.apache.org/foundation/bylaws.html for reference.
The PMC has the following responsibilities:
o Facilitating code or other donations by individuals or companies.
o Resolving license issues and other legal issues.
o Approving new committers.
o Ensuring that administrative and infrastructure work is completed.
o Overseeing Apache Avalon to ensure that the mission defined in
this document is being fulfilled.
o Resolving conflicts within the project.
To become a member of the PMC, an individual must be nominated by a
contributor, unanimously approved by all PMC members, and approved by a
two-thirds majority of committers. In most cases, developers will have
actively contributed to development for at least six months before being
considered for membership on the PMC.
The PMC is responsible for maintaining and updating this charter.
Development must follow the process outlined in this charter, so any
change to the development process necessitates a change to the charter.
Changes must be unanimously approved by all members of the PMC. A
contributor may challenge a change to the charter at any time and ask
for a vote of all committers, in which case a two-thirds majority must
approve the change.
COMMITTERS
==========
Committers are developers who have read/write access priviledges to the
source code repository. New committers are added when a developer is
nominated by a committer and approved by at least 50 percent of the
existing committers with no opposing votes. In most cases, new
committers will already be participating in the development process by
submitting suggestions and/or fixes via the bug report page or mailing
lists.
CONTRIBUTORS
============
Anyone is allowed and encouraged to participate in the development of
the Apache Avalon software products. Occasional contributors will be
able to report bugs, participate in the mailing lists, and submit
patches.
Specific changes to a product proposed for discussion or voting on the
appropriate development mailing list should be presented in the form of
patches. When sent to the mailing list, the message should contain a
subject beginning with [PATCH] and include a clear summary that
describes the effect of that patch.
Like all Apache projects, the Avalon project is a meritocracy -- the
more work you do, the more you are allowed to do. Developers who make
regular and substantial contributions may become committers as described
above.
LICENSING
=========
All contributions to the Apache Avalon project adhere to the "ASF Source
Code License." All contributions must be made under those terms. All
contributions must contain the following copyright notice and license:
============================================================================
The Apache Software License, Version 1.1
============================================================================
Copyright (C) 1997-2003 The Apache Software Foundation.
All rights reserved.
Redistribution and use in source and binary forms, with or without modifica-
tion, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must
include the following acknowledgment: "This product includes software
developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear.
4. The names "Apache", "Avalon", "Excalibur", "Fortress", "Phoenix",
"Merlin" and "Apache Software Foundation" must not be used to endorse or
promote products derived from this software without prior written
permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", nor may
"Apache" appear in their name, without prior written permission of the
Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals
on behalf of the Apache Software Foundation. For more information on the
Apache Software Foundation, please see http://www.apache.org/.
THE DEVELOPMENT PROCESS
=======================
The development process is intentionally lightweight and follows the
same guidelines as other ASF projects. The project committers decide
which changes may be committed to the repository. Three +1 ('yes' votes)
with no -1 ('no' votes or vetoes) are needed to approve a code change.
For efficiency, some code changes from some contributors (e.g. feature
additions, bug fixes) may be approved in advance, in which case they may
be committed first and changed as needed, with conflicts resolved by
majority vote of the committers.
PRODUCT REQUIREMENTS
====================
All software products developed by Apache Avalon must have a set of
requirments as well as an up-to-date release plan and architecture
design. All software products developed by Apache Avalon must have a
test system to verify their correct functioning and are ideally subject
to continous integration testing, regression testing and unit testing.
RELATIONSHIP TO OTHER APACHE PROJECTS
=====================================
The Apache Avalon project should work closely with other Apache
projects, such as Jakarta and Apache HTTP Server, to avoid redundancy
and achieve a coherent architecture among Apache Avalon and these
projects.
</source>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/navigation.xml
Index: navigation.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<project>
<title>Apache Avalon</title>
<body>
<links>
<item name="Apache" href="http://apache.org/"/>
<item name="Avalon" href="http://avalon.apache.org/"/>
<item name="Containers" href="http://avalon.apache.org/containers/"/>
<item name="Platform" href="http://avalon.apache.org/platform/"/>
<item name="Components" href="http://avalon.apache.org/components/"/>
</links>
<menu name="Project">
<item name="Overview" href="/index.html"/>
<item name="Latest News" href="/news.html"/>
<item name="Community" href="/community/index.html">
<item name="Who We Are" href="/community/who/index.html"/>
<item name="Process" href="/community/process/index.html">
<item name="Project Charter" href="/community/process/mission.html"/>
<item name="Management Committee" href="/community/process/pmc.html"/>
<item name="PMC Procedures" href="/community/process/pmc-votes.html"/>
<item name="Coding Standards" href="/community/process/code-standards.html"/>
<item name="Release Management" href="/community/process/release.html"/>
<item name="Patches and Bugs" href="/community/process/patches.html"/>
</item>
<item name="History" href="/community/history/index.html"/>
</item>
</menu>
<menu name="Products">
<item name="Overview" href="products.html"/>
<item name="Containers" href="containers/"/>
<item name="Platform" href="platform/"/>
<item name="Components" href="components/"/>
<item name="Related" href="related.html"/>
</menu>
<menu name="Documentation">
<item name="FAQ" href="http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonFAQ"/>
<item name="Glossary" href="http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonGlossary"/>
<item name="Articles" href="articles.html"/>
<item name="WikiWikiWeb" href="http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonProjectPages"/>
</menu>
<menu name="Resources">
<item name="License" href="license.html"/>
<item name="Downloads" href="downloads.cgi"/>
<item name="CVS" href="cvs.html"/>
<item name="Sandbox" href="sandbox/"/>
<item name="Mailing Lists" href="mailing-lists.html"/>
<item name="Bug Database" href="http://nagoya.apache.org/bugzilla/reports.cgi?product=Avalon&output=most_doomed&links=1&banner=1&quip=0"/>
</menu>
</body>
</project>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/patches.xml
Index: patches.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Patches</title>
</properties>
<body>
<section name="Bugzilla!">
<p>It's not perfect. But it is the issue tracking system we use, and
we ask that you do, too.<br/>
<br/>
<a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Avalon&version=unspecified&rep_platform=all&op_sys=all&assigned_to=dev@avalon.apache.org"><strong>Enter a bug</strong></a><br/>
<br/>
but please make sure the bug you're reporting doesn't exist yet, you include
all relevant information, etc. See
<a href="http://nagoya.apache.org/wiki/apachewiki.cgi?HowDoISubmitUsefulBugReports">this page</a>
for more on how to submit bug reports, or try Google.</p>
</section>
<section name="Submitting patches">
<p>Generate patches using <code>cvs diff -u</code>, or <code>diff -u</code>.
Please create your patches relative to the root of the cvs module the patch
should be applied to. Please compile changes to multiple files
in a single patch file. Make sure the patch adheres to the coding standards,
and includes appropriate javadoc.</p>
<p>When you've built the patch, file a new bug report in Bugzilla if one
does not exist yet, explain the reason behind the patch, how the patch fixes
the issues, and add the patch as an attachment.</p>
<p>If your patch is not getting applied or there is no response, start nagging
the developers (politely, please :D) on the developers mailing list.</p>
<section name="Documentation patches">
<p>Please submit documentation patches against the xml sourcefiles used
for generating the documentation, and not against the documentation
itself.</p>
</section>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/pmc-votes.xml
Index: pmc-votes.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Apache Avalon</title>
</properties>
<body>
<section name="Voting Procedures">
<p>This document details how the Avalon PMC has agreed to handle voting.</p>
<subsection name="People Involved in the Voting Process">
<subsection name="The Proposer">
<p>
The proposer is the one who comes up with the
discussion that needs to be addressed. Any
member of the Avalon community may start the
discussion. The proposer must follow the
procedures listed under the heading "Prior to
the Vote".</p>
</subsection>
<subsection name="The Vote Administrator">
<p>The vote administrator is the person who
tallies the votes and reports the results.
The person who actually puts a proposal up for
vote is usually the vote administrator,
although this task can be taken on by someone
else.</p>
</subsection>
<subsection name="The Voter">
<p>A voter is someone who expresses support,
opposition or abstention for the subject being
voted on. A voter must be an Avalon PMC
member. Input is appreciated from committers
and all other members of the community, but
only votes from PMC members are counted.</p>
</subsection>
</subsection>
<subsection name="Prior to the Vote">
<p>Before any vote can take place, the subject must be
discussed. All such discussions take place on the
Avalon developer or PMC mailing list, and have the
text "[PROPOSAL]" in the subject line. That
practice alerts members to the fact that you
eventually intend to call a vote on the
subject.</p>
</subsection>
<subsection name="The Vote">
<p>When the proposal is ready to be adopted by the
community, the Proposer will call for a vote on
the Avalon developers or PMC mailing list. The
call for vote must have the text "[PMC:VOTE]" in
the subject line. That practice alerts the
members to the fact that the prior proposal is now
ready to vote on, and discussion should stop for
the proposal.</p>
<subsection name="How to Vote">
<p>The voter responds to the call for vote with an
expression of support, opposition, or
abstention. The exact way to express the
voter's position is listed below:</p>
<ul>
<li>+1 a vote supporting the subject</li>
<li>+0 a vote abstaining from the subject (but showing some support).</li>
<li> 0 a vote abstaining from the subject.</li>
<li>-0 a vote abstaining from the subject (but showing disapproval).</li>
<li>-1 a vote opposing the subject</li>
</ul>
</subsection>
<subsection name="Counting Votes">
<p>The vote administrator will count only the last
vote from each voter. That means a voter may
change their vote at any time during the
duration of the vote. All votes (+1, -1, +0,
-0 and 0) count toward quorum, but +0, -0 and
0 do not count when determining majority.</p>
</subsection>
<subsection name="Types of Votes">
<p>There are two classes of votes: a Qualified
Majority Vote and a Normal Majority Vote. In
both types of votes, only +1 and -1 votes
count toward majority.</p>
<subsection name="Qualified Majority Vote">
<p>Any vote that affects the texts "Avalon PMC
Charter" or "Avalon PMC Policies and
Procedures" is a Qualified Majority
Vote. For this type of vote to pass, it
requires that there are more than twice as
many +1 votes as -1 votes.</p> </subsection>
<subsection name="Normal Majority Vote">
<p>All votes that do not fall under the
heading of Qualified Majority Vote are
handled as a Normal Majority Vote. If
there are more +1 votes than -1 votes,
then the vote has passed.</p> </subsection>
</subsection>
<subsection name="Voting Qualifications">
<p>In order for any vote to be considered binding
it must have quorum, and be held for the
proper amount of time.</p>
</subsection>
<subsection name="Quorum">
<p>For all votes, there must be at least three (3)
voters and half (1/2) of the PMC must cast a
vote. When determining quorum, all votes (+1,
-1, +0, -0 and 0) count.</p> </subsection>
<subsection name="Duration">
<p>All votes will be open for an initial period of
one week. The Vote Administrator may close
the vote at any time after that period if
quorum has been achieved. If quorum could not
be reached within the initial one-week period,
the vote will remain open for one additional
week. If the vote still has not achieved
quorum, then it is considered failed. The
proposer can choose to bring it up later when
quorum can be reached.</p> </subsection>
</subsection>
<subsection name="After the Vote">
<p>When the vote is closed, the results of the vote
are summarized by the Vote Administrator. The
vote administrator will send an email to the
Avalon developers or PMC list with the text
"[PMC:VOTE-RESULT]" in the subject that has the
summary. The summary will include the count of
all +1, +0, 0, -0, and -1 responses, and the final
verdict of whether the subject passed.</p>
</subsection>
<subsection name="Disagreements">
<p>Disagreements concerning voting may be directed to
the Chair. The Chair's opinion shall be final and
binding upon the PMC.</p>
</subsection>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/pmc.xml
Index: pmc.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Apache Avalon PMC</title>
</properties>
<body>
<section name="Informative material only">
<p>These pages exist only to provide some down-to-earth insight
in how things work at the ASF. They're informative only, not
normative. They may contain errors or inadequacies. IANAL.</p>
</section>
<section name="So what is this PMC thing?">
<p>Apache is a legal entity, i.e. a real non-profit organisation,
with a charter, members, a board, a president, etc. You can
read all about that
<a href="http://www.apache.org/foundation/">here</a></p>
<p>A PMC, Project Management Committee, is a group of people
appointed with the task of managing something that fits with the
Apache Software Foundation goals. The Avalon PMC, for example,
is tasked with managing Avalon.</p>
</section>
<section name="What, management?! We've already got plenty of those at work!">
<p>We're all programmers, and that is what we want to occupy us
with. We like to share and work on our software together, which
is why we make it free software. However, there is always some
stuff which still requires management.</p>
<p>For example, in order to protect ourselves and our users, all
software hosted at Apache must be properly copyrighted to the ASF,
and licensed under the ASF license. This is something the PMC is
responsible for.</p>
<p>Also, remember that the PMC consists of the same people that do
the development work. There's no "bossing around" here. The PMC
exists only to facilitate free software developers in "doing their
thing", just like the ASF exists "to provide organizational, legal,
and financial support for the Apache Open Source software
projects".</p>
</section>
<section name="he PMC Chair and Officer of the Foundation">
<p>The position of Avalon PMC chair is an important one; the PMC
chair has special responsibilities and privileges as detailed in
the ASF bylaws.</p>
</section>
<section name="So, who's on the PMC?">
<p>
This information is contained in the Avalon STATUS
file, and also <a
href="whoweare/index.html">on this page</a>.
</p>
</section>
</body>
</document>
1.1 avalon-sandbox/mavenized-site/xdocs/community/process/release.xml
Index: release.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Release Management</title>
</properties>
<body>
<section name="Not written yet....">
<p>We haven't got our release process written down yet.</p>
</section>
<section name="Relevant links">
<ul>
<li><a href="http://jakarta.apache.org/site/decisions.html">Jakarta decision process</a></li>
<li><a href="http://httpd.apache.org/dev/release.html">HTTPD release policy</a></li>
<li><a href="http://nagoya.apache.org/bugzilla/reports.cgi?product=Avalon&output=most_doomed&links=1&banner=1&quip=0">Bug summary</a></li>
<li><a href="http://cvs.apache.org/~bodewig/mirror.html">Distribution Mirroring HOWTO</a></li>
<li><a href="http://cvs.apache.org/builds/">Nightly builds</a></li>
<li><a href="http://gump.covalent.net/jars/latest/">Nightly builds: jars@covalent</a></li>
<li><a href="http://freshmeat.net/articles/view/392/">Freshmeat on software builds</a></li>
<li><a href="http://java.sun.com/docs/books/tutorial/jar/sign/signing.html">Java tutorial: jar signing</a></li>
<li><a href="http://java.sun.com/j2se/1.4/docs/tooldocs/tools.html#security">JDK Security tool docs</a></li>
<li><a href="http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt">Tomcat 4 release plan</a></li>
</ul>
</section>
<section name="Noel's thoughts">
<p>Noel J. Bergman wrote to avalon-dev:</p>
<source>
Q: "Is the Avalon PMC able to define a coordinated Release of all the A4
modules such that we know that they all work together?"
My primary concern is not the code, but whether or not the Avalon PMC is
ready to act on its responsibilities, and do a coordinated Release of A4. I
firmly believe that the Avalon PMC has a responsibility to determine a
consistent set of packages that work together, rather than leave it as a
Chinese menu for users to figure out.
My suggestion is that the Avalon Community make it a priority to take stock
of A4, put together a Release Plan, designate a Release Manager, and act as
a group to do a Release. Here are a few items to consider for the Release
Plan:
1) Identify bugs and incompatibilities.
2) Decide which ones will be fixed.
3) Decide what other changes are necessary, e.g., packaging.
4) Make the code changes.
5) Test
6) Update the documentation and web site.
The documentation on the web site doesn't appear to reflect the past year's
changes. And I'm still bemused over how a COP platform that "is a framework
that allows components of varying scale to be created, managed [and] used"
is going to explain why Component is deprecated. But
Here are a few useful links:
Jakarta: http://jakarta.apache.org/site/decisions.html
Apache HTTPD release policies: http://httpd.apache.org/dev/release.html
Avalon bug summary:
http://nagoya.apache.org/bugzilla/reports.cgi?product=Avalon&output=most_doo
med&links=1&banner=1&quip=0
Mirroring: http://cvs.apache.org/~bodewig/mirror.html
Subsequent to the Release, I would suggest that the Avalon Community
consider how best to focus its resources. From what I seem to be hearing
from Paul and others regarding the state of the code and the possibilities
for proper interoperation between A4 containers, I am beginning to believe
that the best option is for the Community to put A4 in maintenance mode, and
focus on A5. But, again, that is something for the Avalon Community to
decide after doing a Release.
--- Noel
</source>
</section>
</body>
</document>
1.3 +7 -14 avalon-sandbox/mavenized-site/xdocs/community/who/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/community/who/navigation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- navigation.xml 26 Oct 2003 12:58:49 -0000 1.2
+++ navigation.xml 26 Oct 2003 14:42:09 -0000 1.3
@@ -15,11 +15,10 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html">
- <item name="Overview" href="/community/who/index.html"/>
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html">
+ <item name="Who We Are" href="/community/who/index.html">
<item name="Mr. Federico Barbieri" href="/community/who/fede.html"/>
<item name="Mr. Pier Fumagalli" href="/community/who/pier.html"/>
<item name="Mr. Roberto Lo Giacco" href="/community/who/roberto.html"/>
@@ -28,7 +27,7 @@
<item name="Mr. Eung-ju Park" href="/community/who/eungju.html"/>
<item name="Mr. Leo Simons" href="/community/who/lsimons.html"/>
<item name="Mr. Leif Mortenson" href="/community/who/leif.html"/>
- <item name="Mr. Stephen McConnell" href="/community/who/mcconnell.html"/>
+ <item name="Stephen McConnell" href="/community/who/mcconnell.html"/>
<item name="Mr. Carsten Ziegeler" href="/community/who/cziegeler.html"/>
<item name="Mr. Jeff Turner" href="/community/who/jturner.html"/>
<item name="Mr. Peter Royal" href="/community/who/proyal.html"/>
@@ -37,14 +36,8 @@
<item name="Mr. Neeme Praks" href="/community/who/neeme.html"/>
<item name="Mr. J Aaron Farr" href="/community/who/farra.html"/>
</item>
- <item name="Project Charter" href="/mission.html"/>
- <item name="Project History" href="/community/history/index.html"/>
- <item name="PMC" href="/community/pmc.html"/>
- <item name="PMC Voting Process" href="/community/pmc-votes.html"/>
- <item name="Development Process" href="/community/development.html">
- <item name="Coding Standards" href="/commmunity/code-standards.html"/>
- <item name="Release Management" href="/community/release.html"/>
- <item name="Patches and Bugs" href="/community/patches.html"/>
+ <item name="Process" href="/community/process/index.html"/>
+ <item name="History" href="/community/history/index.html"/>
</item>
</menu>
1.2 +3 -4 avalon-sandbox/mavenized-site/xdocs/components/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/components/navigation.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- navigation.xml 25 Oct 2003 20:50:44 -0000 1.1
+++ navigation.xml 26 Oct 2003 14:42:09 -0000 1.2
@@ -15,10 +15,9 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html"/>
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html"/>
</menu>
<menu name="Products">
1.2 +3 -4 avalon-sandbox/mavenized-site/xdocs/containers/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/containers/navigation.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- navigation.xml 25 Oct 2003 20:50:44 -0000 1.1
+++ navigation.xml 26 Oct 2003 14:42:09 -0000 1.2
@@ -15,10 +15,9 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html"/>
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html"/>
</menu>
<menu name="Products">
1.2 +3 -4 avalon-sandbox/mavenized-site/xdocs/platform/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/mavenized-site/xdocs/platform/navigation.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- navigation.xml 25 Oct 2003 20:50:45 -0000 1.1
+++ navigation.xml 26 Oct 2003 14:42:09 -0000 1.2
@@ -15,10 +15,9 @@
</links>
<menu name="Project">
- <item name="Overview" href="index.html"/>
- <item name="Mission" href="mission.html"/>
- <item name="News" href="news.html"/>
- <item name="Community" href="community/index.html"/>
+ <item name="Overview" href="/index.html"/>
+ <item name="Latest News" href="/news.html"/>
+ <item name="Community" href="/community/index.html"/>
</menu>
<menu name="Products">
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org