notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

svn commit: r1333 - in development/main/central/site/src/docs/about/community: . process

From: niclas AT netcompartner.com
To: notify-dpml AT lists.ibiblio.org
Subject: svn commit: r1333 - in development/main/central/site/src/docs/about/community: . process
Date: Fri, 31 Dec 2004 05:01:24 +0100

Author: niclas
Date: Fri Dec 31 05:01:24 2004
New Revision: 1333

Added:
development/main/central/site/src/docs/about/community/process/roles.xml
(contents, props changed)
Modified:
development/main/central/site/src/docs/about/community/index.xml
development/main/central/site/src/docs/about/community/process/index.xml
Log:
Created some more documentation about the community.

Modified: development/main/central/site/src/docs/about/community/index.xml
==============================================================================
--- development/main/central/site/src/docs/about/community/index.xml
(original)
+++ development/main/central/site/src/docs/about/community/index.xml Fri
Dec 31 05:01:24 2004
@@ -8,6 +8,43 @@

<body>
<section name="DPML Community">
+ 
+ The community initially started with a group from the Apache Avalon
+ community, spearheaded by Stephen McConnell, Peter Neubauer and
+ Niclas Hedhman. You can read more about the <a href="history.html">
+ history here</a>. The basic principles of the community includes;
+ 
+ <ul>
+ <li>
+ Lower the bar for people to participate. Open Participation
+ Software was coined, to communicate that everyone is welcome to
+ join in.
+ </li>
+ <li>
+ Flock of bird metaphor. If you are active in the community, we call
+ it "to fly". If you fly, you are part of the decision making
process
+ of where to head next.
+ </li>
+ <li>
+ Extreme commercial friendliness. Of course using the Apache License
+ for all products released, but also to work towards goals that are
+ of interest of companies, such as providing commercial support,
+ development engagement of particular features for
+ a fee and general consultancy around the products.
+ </li>
+ </ul>
+ 
+ The <a href="people/index.html">people</a> in the community is trying
+ to refine the <a href="process/index.html">process</a> as we go
+ along.
+ 
+ 
+ We are working towards the creation of a non-profit organization,
+ which we anticipate to get incorporated in Q1-2005. This will allow
+ us to engage in more formal activities and accept monetary
+ contributions, for instance to
+ establish better infrastructure, marketing materials and much more.
+ 
</section>
</body>
</document>

Modified:
development/main/central/site/src/docs/about/community/process/index.xml
==============================================================================
--- development/main/central/site/src/docs/about/community/process/index.xml
(original)
+++ development/main/central/site/src/docs/about/community/process/index.xml
Fri Dec 31 05:01:24 2004
@@ -1,17 +1,77 @@
<?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
- <author email="mcconnell AT dpml.net">Stephen McConnell</author>
+ <author email="niclas AT hedhman.org">Niclas Hedhman</author>
<title>DPML Central</title>
</properties>

<body>
<section name="Process">

+ Open Participation Software is a new process, and we are trying to
+ refine it as we go along. Please join the
+ <a href="../../resources/lists.xml">admin-dpml AT lists.ibiblio.org</a>
+ mailing list if you want to partake in the discussion.

-
-
+ <subsection name="Repository Access" >
+ 
+ Once we have established a working contractual agreement between
the
+ people who are part of the community, we can enable the full vision
+ of Open Participation Software, which includes the
self-registration
+ to get access to the source repository. The idea is that anyone who
+ have spent enough time to work out a patch is committed enough to
+ be a member (loose term) of the community. It is essentially no
+ different than self registration to issue tracking systems. In
fact,
+ we have tied the Scarab registration to the Subversion access
rights,
+ so your username and password are always synchronized between these
+ two fundamental systems.
+ 
+ 
+ We want to get tools in place to make it very easy to revert
+ individual commits that are made either maliciously or
+ unintentionally. It should only be a matter of running a
commandline
+ tool, which takes a revision number and undo that commit. This has
not
+ been done yet, and anyone with BASH, Perl or Python experience to
do
+ this are free to join in the fun and help out.
+ 
+ </subsection>
+ <subsection name="Coding Standard" >
+ 
+ We have a <a href="code.html">Coding Standard</a> that we require
+ everyone to follow. Remember that it is not difficult to write
code,
+ it is difficult to read it. So the Coding Standards are focussed on
+ improving readability, sometimes at the expense that it takes more
+ typing to do.
+ 
+ 
+ Checkstyle is used to validate the Coding Standard, and is very
+ unforgiving. Since Checkstyle was introduced fairly late in our
+ history, especially Metro has endless number of failures to comply.
+ If you want to join in the fun and help out, it is a pretty good
+ idea to start by helping fixing these Checkstyle reports. It gives
+ you an idea of how the code is written, and you get comfortable
+ with using the Subversion tool.
+ 
+ </subsection>
+ <subsection name="Code Ladder" >
+ 
+ We use an informal code ladder, which at the moment starts in the
+ Laboratory (<a
href="http://paris.dpml.net/svn/development/laboratory";>
+ /svn/development/laboratory</a>), then moves to Main, then QA and
+ finally Production. Laboratory is a place where new part or
subsystems
+ are added first. If the community feels comfortable with it, it is
+ moved to Main, where the bulk of the development occurs. When there
+ is time for a release, the Main (or part of it) is moved to QA,
where
+ the codebase is tested and ensured that it is in a releasable
state.
+ Only extremely small changes are made in QA, anything larger and
the
+ release process starts over in Main. Once the QA Team is happy with
+ the QA step, the Release Manager puts it into Production.
Production
+ is where most users will check out the code, without worrying about
+ stability. I.e. our primary release mechanism is through
+ Subversion and in source format. We are currently discussing which
+ other release formats should be 'official'.
+ 
+ </subsection>
</section>
</body>
</document>
-

Added:
development/main/central/site/src/docs/about/community/process/roles.xml
==============================================================================
--- (empty file)
+++ development/main/central/site/src/docs/about/community/process/roles.xml
Fri Dec 31 05:01:24 2004
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="niclas AT hedhman.org">Niclas Hedhman</author>
+ <title>DPML Central</title>
+ </properties>
+
+ <body>
+ <section name="Community Roles">
+ 
+ We are not very strict in the roles at this community, and you can
+ basically assign any role to yourself, with a few exceptions
mentioned
+ below. Below is a list of the formal roles, informal roles and
'teams'
+ that we consider this community to consist of.
+ 
+ <subsection name="User" >
+ 
+ The most important role in our community is the User. The people
who
+ actually use the products that we produce. If the user have a
+ question, it should be attended to as soon as possible. A happy
user
+ is the best advertising and free of charge. A non-happy user can
+ spoil our reputation.
+ 
+ </subsection>
+ <subsection name="Developer" >
+ 
+ The Developer is the backbone of the community. To become a
Devloper,
+ you only need to register yourself and jump in. You are required
+ to subscribe to the <a href="../../resources/lists.html">
+ dev-dpml AT lists.ibiblio.org</a> mailing list, and you should also
add
+ your bio into the <a href="../people/index.html">People</a> list,
+ preferably with photo. You also need to familiarize yourself with
+ the total <a href="index.html">Process</a>, especially the
+ <a href="code.html">Coding Standard</a>.
+ 
+ </subsection>
+ <subsection name="Documentation Team" >
+ 
+ The Documentation Team is the heroes of any Open Software
community,
+ but they are hard to find. Developers will support any
documentation
+ effort to the best of their abilities, so if you have a desire to
+ write, but doesn't know all the details required, please still
+ take on the challenge and ask around for the details.
+ 
+ </subsection>
+ <subsection name="Infrastructure Team" >
+ 
+ The Infrastructure Team is responsible for the DPML infrastructure,
+ i.e. the configuration, maintenance and operations of servers and
+ applications on those servers. The process of selecting the
+ Infrastructure Team is not yet determined, as we will need some
+ constraint on who have root access on these critical resources.
+ However, most applications should be configured to be configurable
+ through Subversion and operated through web interfaces, and
therefor
+ allow all developers to help out.
+ 
+ </subsection>
+ <subsection name="Public Relations Team" >
+ 
+ You can assign yourself to the Public Relations Team, simply by
+ subscribing to the <a href="../../resources/lists.html">
+ pr-dev AT lists.ibiblio.org</a> mailing list and announcing that you
want
+ to help out.
+ 
+ </subsection>
+ <subsection name="Quality Assurance Team" >
+ 
+ This is a formal team, which is selected by the
+ developers. Only people with a strong sense of
+ quality assurance should opt for this position. Only the QA Team
+ has access to the QA step on the code ladder, and high level of
+ scrutiny should be done for every commit in QA. If in doubt or
+ disagreement, the release process is aborted, and starts over in
+ Main.
+ 
+ </subsection>
+ <subsection name="Release Manager" >
+ 
+ This is a formal role, and it is assigned by the
+ QA Team. The Release Manager is responsible for the entire QA
process
+ and that the Production step in the code ladder is in perfect
shape.
+ Therefor, only the Release Manager(s) has commit access to
Production
+ 
+ </subsection>
+ </section>
+ </body>
+</document>

svn commit: r1333 - in development/main/central/site/src/docs/about/community: . process, niclas, 12/30/2004