Index: xdocs/contributors.xml
===================================================================
--- xdocs/contributors.xml (revision 485548)
+++ xdocs/contributors.xml (working copy)
@@ -21,54 +21,220 @@
- If you would like to contribute to Harmony, please see the
- roadmap list to find areas where you can contribute.
+ Welcome to the Apache Harmony community! Everyone interested in the project and
+ aimed at making an impact in its development, can become a member of our
+ community.
+ If you would like to contribute to Harmony, please see the
+ roadmap list to find areas where you can contribute.
If there is nothing in there that suits your interest, but you still have
ideas, please feel free to suggest them on
- the mailing list.
+ the mailing list. For more information on
+ committers, contributors and their contributions, refer to the
+ Contribution Policy page. To figure out
+ how to resolve conflicts through voting, who is able to vote and make final
+ decisions, see the Voting page.
+ In the community you should distinguish among the following concepts:
+
+
+
-
+
- Name Organization Status
- Nathan Beyer Independent A
- Archie Cobbs Awarix A
- Oliver Deakin IBM UK A
- Tim Ellison IBM UK A
- George Harley IBM UK A
- Mark Hindess IBM UK A
- (Richard)Yanxuan Liang IBM CN A
- Mikhail Loenko Intel A
- Dan Lydick Independent A
- Geir Magnusson Jr. Intel A
- Stepan Mishura Intel A
- Nadya Morozova Intel A
- Alexey Petrenko Intel A
- Gregory Shimansky Intel A
- David Tanzer ? A
- Alexey Varlamov Intel Russia A
- Weldon Washburn Intel A
- (Paulex)Pu Yang IBM CN A
-Alexei Zakharov Intel A
+ Apache Harmony Contributors are all the volunteers contributing time, + code, documentation, or resources to the Apache Harmony Project. A + contributor that makes sustained, welcome contributions to the project + for over six months is usually invited to become a Committer, though + the exact timing of such invitations depends on many factors. +
+The Project Management Committee (PMC) is a group of volunteers + responsible for managing the Apache Harmony Project in the following way: +
Policy: +
Goals: +
Apache Harmony Committers are a group of volunteers + responsible for the technical aspects of the Apache Harmony + Project. This group has write access to the appropriate source + repositories and these volunteers may cast binding votes on + any technical discussion.
+Policy: +
Here is the list of present committers:
+| Name | +Organization | +Status | +
|---|---|---|
| Nathan Beyer | +Independent | +A | +
| Archie Cobbs | +Awarix | +A | +
| Oliver Deakin | +IBM UK | +A | +
| Tim Ellison | +IBM UK | +A | +
| George Harley | +IBM UK | +A | +
| Mark Hindess | +IBM UK | +A | +
| (Richard)Yanxuan Liang | +IBM CN | +A | +
| Mikhail Loenko | +Intel | +A | +
| Dan Lydick | +Independent | +A | +
| Geir Magnusson Jr. | +Intel | +A | +
| Stepan Mishura | +Intel | +A | +
| Nadya Morozova | +Intel | +A | +
| Alexey Petrenko | +Intel | +A | +
| Gregory Shimansky | +Intel | +A | +
| David Tanzer | +? | +A | +
| Alexey Varlamov | +Intel Russia | +A | +
| Weldon Washburn | +Intel | +A | +
| (Paulex)Pu Yang | +IBM CN | +A | +
| Alexei Zakharov | +Intel | +A | +
- Status : + Status:
+
One of the best ways to get involved in the Harmony project is to - create patches or additions and contribute them. All contributions - should be made via a new entry in our project + create patches or additions and contribute them. When you propose + a specific change to the software for discussion or voting on the + mailing list, you should present in the form of input to the patch + command. + All contributions should be made via a new entry in our project JIRA.
-- Here are some basic guidelines and suggestions : -
- Once you are sure you have tested/reviewed your changes, open a - new JIRA entry. Clearly describe the patch or enhancement, and - provide details, such as how to re-create if a bug, why the - change or enhancement is useful, etc. Then, attach all materials - to the JIRA entry via "Attach File". Please be sure to select - "Grant license to ASF for inclusion in ASF works...". Any patch - without this grant will be rejected. -
+- Please use the subversion 'diff' utility to create a patch as follows : - -
- svn diff file.java > file.patch -- - where 'file' is the filename that you have changed. This will produce a - nice patch file that can be added to the JIRA, which makes it easy for - the project committers to review and possibly accept your patch. - +
+ Once you are sure you have tested/reviewed your changes, do the following: +
+diff utility to create a patch as follows:
+ svn diff file.java > file.patch+ where
file is the filename that you have changed. This will produce a
+ nice patch file that can be added to the
+ JIRA, which makes it easy for
+ the project committers to review and possibly accept your patch.
+ [PATCH] and provide a distinctive one-line summary
+ corresponding to the action item for that patch.
+ diff -u command from the
+ original software file(s) to the modified software file(s).
+ Example
+diff -u http_main.c.orig http_main.c >> patchfile.txt+
or
+cvs diff -u http_main.c >> patchfile.txt+
patch -s < patchfile+ +
You are welcome to share all your ideas, ask questions and discuss plans + on the Apache Harmony mailing lists!
++ The Apache Harmony mailing lists operate under the following terms : +
-Apache Harmony mailing lists operate under the following terms : -
- --This forum has been created for public communication about projects -of The Apache Software Foundation (the "Foundation"), a Delaware -nonprofit corporation classified as a public charity under 501(c)(3). -All communication intentionally submitted to the Foundation on this -forum is considered a Contribution to the Foundation unless otherwise -noted in the communication. The terms and conditions that apply to -your Contributions are defined by either a contributor license -agreement (CLA) signed by you and/or your employer or, if no such CLA -is on file at the Foundation, by the terms and conditions of -Contributions as defined by the Apache License, Version 2.0. --> - -
-Further : -
- ----
- -If you do not wish your post to be a Contribution, we would prefer that you do not post it. However, in the -event that you do, please mark as "NOT A CONTRIBUTION" at the top of the posting. +There are currently three publicly available mailing lists for Harmony: +
-
- + Developer Mailing List - dev@harmony.apache.org
-- -Do not post any code that is not your original work, or code that you do not have -clear authorization to contribute. +
- Source Control Mailing List - commits@harmony.apache.org
-- -Do not engage in detailed discussion of any implementation that you have been exposed -to unless such implementation is available to everyone under an open source license or is -your own implementation. -
-- -Under no circumstances will any committer accept code for inclusion in our SVN -repository contributed on the mailing list unless -it is from an -Authorized Contributor. -
-
-There are currently three publicly available mailing lists for Harmony : +
The developer mailing list is used by the developers to discuss -plans, make decisions, vote on technical issues, etc. This -list has a higher volume, though some conversations take place on - IRC as -well.
-+ The developer mailing list is used by the contributors + to discuss plans, make decisions, vote on technical issues, etc. Subscription to + the list is open, but only subscribers can post directly to the list. This + list has a higher volume, though some conversations take place on + IRC as + well. +
+- Please note that at this time, we are keeping all developer traffic on one list, - for classlibrary, virtual machine, doc, site and tool development, in order to - help build one homogeneous community. It is expected that at some point in the - near future, we'll be splitting off into technical domains. -
-- In order to help people sort and make sense of the traffic, please prefix your - subject line with an appropriate token : -
+Note
++ Now we are keeping all developer traffic on one list, + for classlibrary, virtual machine, doc, site and tool development, in order to + help build one homogeneous community. It is expected that at some point in the + near future, we will be splitting off into technical domains. +
++ To help people sort and make sense of the traffic, please prefix your + subject line with an appropriate token: +
- Simply add the token to the start of your subject line. For example : -
+ Simply add the token to the start of your subject line. For example : +This list receives notifications (with diffs) every time a change is
-committed to the Harmony source tree. It also receives change notices
-for changes to the Harmony Wiki and whenever issues are added to or
+ All of the Apache projects are maintained in shared information
+ repositories using SVN. Only some of the Apache developers, the committers, have
+ write access to these repositories; everyone has read access via
+ anonymous SVN. The Apache Harmony PMC's private mailing list for discussion of issues
+ that are inappropriate for public discussion, such as legal, personal,
+ or security issues prior to a published fix. Subscription to the list
+ is only open to Apache Harmony PMC members. The Harmony PMC has a mailing list to resolve any administrative issues,
-This list is limited to PMC members (most committers on the project).
This list receives notifications (with diffs)
+ every time a change is committed to the Harmony source tree. It also receives
+ change notices for changes to the Harmony Wiki and whenever issues are added to or
updated in our
JIRA issue tracking system.
@@ -166,11 +147,12 @@