harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nadi...@apache.org
Subject svn commit: r517682 [1/5] - in /harmony/standard/site/xdocs: ./ subcomponents/classlibrary/ subcomponents/drlvm/
Date Tue, 13 Mar 2007 13:17:31 GMT
Author: nadinem
Date: Tue Mar 13 06:17:30 2007
New Revision: 517682

URL: http://svn.apache.org/viewvc?view=rev&rev=517682
Log:
fix for HARMONY-3364: formatting of source webpages in coding style and presentation layout

Modified:
    harmony/standard/site/xdocs/downloads.xml
    harmony/standard/site/xdocs/faq.xml
    harmony/standard/site/xdocs/hdk.xml
    harmony/standard/site/xdocs/index.xml
    harmony/standard/site/xdocs/issue_resolution_guideline.xml
    harmony/standard/site/xdocs/mailing.xml
    harmony/standard/site/xdocs/newshistory.xml
    harmony/standard/site/xdocs/roadmap.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/ASN1Framework.html
    harmony/standard/site/xdocs/subcomponents/classlibrary/compat.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/pkgnaming.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/ser_testing.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/status.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml
    harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html
    harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.html
    harmony/standard/site/xdocs/svn.xml

Modified: harmony/standard/site/xdocs/downloads.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/downloads.xml?view=diff&rev=517682&r1=517681&r2=517682
==============================================================================
--- harmony/standard/site/xdocs/downloads.xml (original)
+++ harmony/standard/site/xdocs/downloads.xml Tue Mar 13 06:17:30 2007
@@ -52,47 +52,47 @@
 
     <p>
         We offer the following
-        <a href="http://people.apache.org/builds/harmony/snapshots/">snapshots</a> : 
+        <a href="http://people.apache.org/builds/harmony/snapshots/">snapshots</a>:
     </p>
 
     <p class="note">Note</p>
     <p class="notetext">
-    These are <i>snapshot</i> builds - untested builds provided for your convenience.  They
+    These are <i>snapshot</i> builds - untested builds provided for your convenience. They
     have not been tested, and are not official releases of the Apache Harmony project or
     the Apache Software Foundation.
     </p>
 
-    <strong>Java Development Kit (JDK)</strong>
+    <h3>Java Development Kit (JDK)</h3>
 
     <p>
-        The JDK lets you build and run your Java programs.  It include javac and other standard JDK tools.
-        Note that it's safest to set JAVA_HOME to the root directory
-        of the distribution, and put the bin/ directory on your PATH.
-    </p>
+        The JDK lets you build and run your Java programs. It include javac and other standard JDK tools.
+        Note that it's safest to set <code>JAVA_HOME</code> to the root directory
+        of the distribution, and put the <code>bin/</code> directory on your <code>PATH</code>.
+</p>
 
-    <ul>
-        <li>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz">Latest 32-bit Linux JDK (tar.gz)</a>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz.md5">(MD5)</a>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz.sha">(SHA)</a>
-        </li>
-        <li>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86_64.tar.gz">Latest 64-bit Linux JDK (tar.gz)</a>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86_64.tar.gz.md5">(MD5)</a>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86_64.tar.gz.sha">(SHA)</a>
-        </li>
-        <li>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip">Latest 32-bit Windows JDK (zip)</a>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip.md5">(MD5)</a>
-            <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip.sha">(SHA)</a>
-        </li>
-    </ul>
+<ul>
+    <li>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz">Latest 32-bit Linux JDK (tar.gz)</a>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz.md5">(MD5)</a>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz.sha">(SHA)</a>
+    </li>
+    <li>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86_64.tar.gz">Latest 64-bit Linux JDK (tar.gz)</a>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86_64.tar.gz.md5">(MD5)</a>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86_64.tar.gz.sha">(SHA)</a>
+    </li>
+    <li>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip">Latest 32-bit Windows JDK (zip)</a>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip.md5">(MD5)</a>
+        <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip.sha">(SHA)</a>
+    </li>
+</ul>
 
-    <strong>Java Runtime Environment (JRE)</strong>
+<h3>Java Runtime Environment (JRE)</h3>
 
-    <p>
-        The JRE lets you run your Java programs.  Note that it's safest to set JAVA_HOME to the root directory
-        of the distribution, and put the bin/ directory on your PATH.
+<p>
+    The JRE lets you run your Java programs. Note that it's safest to set <code>JAVA_HOME to</code> the root directory
+of the distribution, and put the <code>bin/</code> directory on your <code>PATH</code>.
     </p>
 
     <ul>
@@ -113,10 +113,10 @@
         </li>
     </ul>
 
-    <strong>Harmony Development Kit (HDK)</strong>
+    <h3>Harmony Development Kit (HDK)</h3>
 
     <p>
-        The HDK is targetted at Harmony developers.  It includes the pre-built class library and VM binaries,
+        The HDK is targetted at Harmony developers. It includes the pre-built class library and VM binaries,
         necessary include files, test cases, and dependencies. It is not a replacement for the common JDK.
     </p>
 
@@ -140,7 +140,7 @@
 
 <p>
     These are not official releases of the Apache Software Foundation, nor are they
-    complete or compatible with the Java specification.  They are snapshots provided
+    complete or compatible with the Java specification. They are snapshots provided
     to make testing and experimentation easier.
 </p>
 
@@ -154,6 +154,8 @@
 </section>
 </body>
 </document>
+
+
 
 
 

Modified: harmony/standard/site/xdocs/faq.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/faq.xml?view=diff&rev=517682&r1=517681&r2=517682
==============================================================================
--- harmony/standard/site/xdocs/faq.xml (original)
+++ harmony/standard/site/xdocs/faq.xml Tue Mar 13 06:17:30 2007
@@ -1,12 +1,11 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!--
-
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
   
        http://www.apache.org/licenses/LICENSE-2.0
   
@@ -16,191 +15,202 @@
     See the License for the specific language governing permissions and
     limitations under the License.
 -->
-  
+
 <document>
 
- <properties>
-  <title>Frequently Asked Questions</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
- <body>	
-  <section name="General">
-
-     <ol start="0">
-	<li>
-		<strong>How do I subscribe to the mail list?</strong>
-		<br />
-		You can subscribe by sending an email to dev-subscribe@harmony.apache.org
-		you will receive a confirmation request that you must respond to.
-		After that, you can post to the dev list dev@harmony.apache.org. 
-		Please see our <a href="mailing.html">mailing list</a> page for 
-		more information.
-		</li>
-	</ol>	
-  </section>
-  
-  <section name="Technical">
-  
-     <ol start="0">
-	<li>
-	<strong>When building the classlibrary, ant crashes with a compiler error, a
-	heap error, or a reflection error.</strong>
-	<br/>
-	These problems are all symptomatic of running out of java heap for ant.  The 
-	solution is to set the ANT_OPTS environment variable to something bigger than
-	the default.  At the time of this writing, best practice is to set 
-	<blockquote>
-	set ANT_OPTS="-Xmx256M"
-	</blockquote>
-	</li>  
-	</ol>  
-  </section>
-  
-  
-  <section name="Original FAQ Questions from Project Launch">
-     <ol start="0">
-     <li>
-		<strong>Why are you doing this?</strong>
-		<br />
-		We believe that there is broad community interest in coming together to create and use an open source,
-		compatible implementation of J2SE 5, the latest version of the Java 2 Standard Edition specification.
-		</li>
-	<li>
-		<strong>What version of Java will you be implementing?</strong>
-		<br />
-		We are starting with Java SE 5, as that is the first version of Java SE for which the 
-		licensing allows an open source implementation, but we'll continue with Java SE 6 and
-		any subsequent versions that follow.
-	</li>
-	<li>
-		<strong>Why haven't you done this before?</strong>
-		<br />
-		While the Java Community Process has allowed open source implementations of JSRs for a few years now, 
-		Java 5 is the first of the J2SE specs that we are able to do due to licensing reasons.
-	</li>
-	<li>
-		<strong>Are you doing this to attack Sun?</strong>
-		<br />
-		No, of course we aren't. Apache doesn't support projects that attack any entity, corporate or otherwise.
-		<br />
-		Sun has been a long-time supporter of Apache and Apache projects, and Apache has a wide variety of projects 
-		that are implementations of Java specifications, such as Apache Geronimo, Apache Tomcat, Pluto, taglibs, etc.
-		<br />
-		This project is open to every interested member of the Java community, and every interested member is welcome
-		to participate in whatever manner they choose.
-	</li>
-	<li>
-		<strong>Are you doing this because Sun refuses to release their source for J2SE under an open source license?</strong>
-		<br />
-		Not really.  We would welcome Sun doing that (as well as anyone else w/ a J2SE implementation!) as it would save us a 
-		lot of time, and we wholeheartedly encourage them to do so ;)  but Sun has the right to do what it chooses with it's intellectual property.
-		Since we started the project, Sun has announced that they will be open sourcing their implementation, and they've
-		started the process.  Of course, we'll continue to develop Apache Harmony - multiple independent implelentations
-		of Java SE is good for the Java ecosystem.
-	</li>
-	<li>
-		<strong>Will your implementation be compatible with the specification?</strong>
-		<br />
-		Yes
-	</li>
-	<li>
-		<strong>How will you know?</strong>
-		<br />
-		We are going to test it with the TCK from Sun.
-	</li>
-	<li>
-		<strong>How will you license the TCK from Sun.  Isn't it expensive?</strong>
-		<br />
-		Sun offers scholarships to qualified non-profits, academics and individuals. 
-		Apache is a qualified non-profit, and has benefitted from this scholarship before, 
-		with the J2EE 1.4 TCK license and support for the Apache Geronimo project, among others.
-		<br />
-		We will apply for the scholarship, and hope that Sun will grant us the license and support needed for us to do a good job.
-	</li>
-	<li>
-		<strong>How long will it take?</strong>
-		<br />
-		It will be done when it's done :)  This will take a long time, but we hope that contributions from around the community will help us along the way.
-	</li>
-	<li>
-		<strong>Do you have any code to start?</strong>
-		<br />
-		No, we don't.  We didn't want to "bless" any given implementation that might be donated 
-		(if such a thing could happen) but would rather let the community decide how it will create and develop the platform.
-	</li>
-	<li>
-		<strong>Will you accept SWT if IBM offers it?</strong>
-		<br />
-		Apache is always grateful for contributions from wherever they come, and IBM has a record of contributions 
-		to open source,  but it would up to the project community to decide whether any particular contribution was used in the project.
-	</li>
-	<li>
-		<strong>Why are you going to have an architecture thread?</strong>
-		<br />
-		We wanted a way that we could bring together people from all over the Java community, 
-		even other open-source projects that are related.  We welcome everyone to the discussion,
-		no matter what license they choose to implement under, be it a free software license, 
-		an open source license or a proprietary license.  We are here to open discussion and learning, 
-		and to design a great architecture for J2SE platforms.
-		<br />
-		At Apache, we think that a strong, diverse, meritocratic community is what makes a good open source project, 
-		and we want to be sure that everyone can participate in some way.
-	</li>
-	<li>
-		<strong>Does this compete with Kaffe and Classpath?</strong>
-		<br />
-		People from Kaffe and Classpath are helping start this project! 
-		Their experience in the open source VM and class library is invaluable, 
-		and they bring problems that the larger architecture community discussion can help solve.
-		<br />
-		We will have an implementation under the Apache License, but we think of this as complementary rather than competitive. 
-		And when we solve a few small license interoperability issues, we expect we'll be able to complement each other even more.
-	</li>
-	<li>
-		<strong>How will you ensure that the intellectual property of Sun and others is respected?</strong>
-		<br />
-		Good question - this is a very important issue for us.  There are several ways, but this will be a topic
-		 for the community to work on at the beginning.  So far we've thought of :
-		<ol>
-			<li>We shall ask any person that would be a committer to declare what kind of non-open-source class library 
-			or VM source code they have been exposed to, and allow us to keep them from participating in the related parts 
-			of the codebase where they may inadvertently violate the IP rights of someone else.
-			</li> 
-			<li> We shall require that any code contribution that isn't a new, original work of authorship created expressly 
-			for the Apache Harmony project be subject to the standard Apache process for provenance and licensing to ensure 
-			that we have an accurate record of every contribution that wasn't created expressly inside the Apache Harmony project.
-			</li>
-			<li>We would like to perform continuous "surveillance" on the codebase we are building, and compare to class library
-			 and VMs from elsewhere, like Sun, IBM, BEA, Kaffe, etc to ensure that no code from those efforts become part of Apache Harmony
-			 without our knowledge.  We do this to protect ourselves, our users, and of course those other efforts.  
-			 We don't know yet how to do this, but are exploring ideas such as having a third party such as Black Duck or 
-			 an existing licensee (or Sun!) do this for us.  This, like all the topics herein, are open for discussion an change by the community.
-			</li> 
-			<li>Anything anyone can think of!
-			</li>
-		</ol>
-	</li>
-	<li>
-		<strong>Won't this lead to fragmentation in the Java community?</strong>
-		<br />
-		We don't think so.  Our intent is to bring people together, let us share what we know, 
-		solve common problems, and collaborate on things where we can.  A diverse Java community is a healthy Java community.  
-		Multiple implementations of the Java specifications show the value of Java - that we do have a specification, 
-		that anyone is free to make a compatible implementation, and that users of Java have the opportunity to run 
-		their Java code in more places, on more platforms.  This is the central promise of Java, and we think that our efforts support this.
-	</li> 
-	<li>
-		<strong>How can I get involved and help influence and shape this proposal? Or is it too late?</strong>
-		<br />
-		Join the community and participate!  It's never too late!   We're just getting started, and everything is open
-		to discussion - the community will change what the community wants to change.   What we do in this project is decided
-		by those participating in the project.  This is the Apache Software Foundation - collaborative, meritocratic, and community-based.
-	</li>
-</ol>
+    <properties>
+        <title>Frequently Asked Questions</title>
+        <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    </properties>
+
+    <body>
+        <section name="General">
+           <dl><dt>How do I subscribe to the mail list?</dt>
+                    <dd>
+                        You can subscribe by sending an email to
+                        <a href="mailto:dev-subscribe@harmony.apache.org">dev-subscribe@harmony.apache.org</a>.
+                        You will receive a confirmation request that you must respond to.
+                        After that, you can post to the dev list
+                        <a href="mailto:dev@harmony.apache.org">dev@harmony.apache.org</a>.
+                        Please see our <a href="mailing.html">mailing list</a> page for
+                        more information.
+         </dd>
+               </dl>
+        </section>
+        <section name="Technical">
+            <dl>
+                <dt>When building the classlibrary, ant crashes with a compiler error, a
+                            heap error, or a reflection error.</dt>
+                    <dd>
+                        These problems are all symptomatic of running out of java heap for ant. The
+                        solution is to set the <code>ANT_OPTS</code> environment variable to something bigger than
+                        the default. At the time of this writing, best practice is to set:
+                     <pre>set ANT_OPTS="-Xmx256M"</pre>
+                </dd>
+            </dl>
+        </section>
+        <section name="Original FAQ Questions from Project Launch">
+            <dl>
+                <dt>Why are you doing this?</dt>
+                    <dd>
+                        We believe that there is broad community interest in coming together to create
+                        and use an open source, compatible implementation of J2SE 5, the latest version
+                        of the Java 2 Standard Edition specification.
+                    </dd>
+                               <dt>What version of Java will you be implementing?</dt>
+                   <dd>
+                        We are starting with Java SE 5, as that is the first version of Java SE for which the
+                        licensing allows an open source implementation, but we'll continue with Java SE 6 and
+                        any subsequent versions that follow.
+                    </dd>
+                <dt>Why haven't you done this before?</dt>
+                   <dd>
+                        While the Java Community Process has allowed open source implementations of JSRs
+                        for a few years now, Java 5 is the first of the J2SE specs that we are able to do
+                        due to licensing reasons.
+                    </dd>
+                <dt>Are you doing this to attack Sun?</dt>
+                   <dd>
+                        No, of course we aren't. Apache doesn't support projects that attack any entity,
+                        corporate or otherwise. Sun has been a long-time supporter of Apache and Apache projects,
+                        and Apache has a wide variety of projects that are implementations of Java specifications,
+                        such as Apache Geronimo, Apache Tomcat, Pluto, taglibs, etc.<br />
+                        This project is open to every interested member of the Java community, and every
+                        interested member is welcome to participate in whatever manner they choose.
+                    </dd>
+                <dt>Are you doing this because Sun refuses to release their source for J2SE
+                            under an open source license?
+                    </dt>
+                    <dd>
+                        Not really. We would welcome Sun doing that (as well as anyone else w/ a J2SE implementation!)
+                        as it would save us a lot of time, and we wholeheartedly encourage them to do so ;) but Sun
+                        has the right to do what it chooses with it's intellectual property.
+                        Since we started the project, Sun has announced that they will be open sourcing their implementation, and they've
+                        started the process. Of course, we'll continue to develop Apache Harmony - multiple independent implelentations
+                        of Java SE is good for the Java ecosystem.
+                    </dd>
+               
+                   <dt>
+                        Will your implementation be compatible with the specification?
+                    </dt>
+                    <dd>
+                        Yes
+                    </dd>
+                                    <dt>How will you know?
+                    </dt>
+                    <dd>
+                        We are going to test it with the TCK from Sun.
+                </dd>
+                    <dt>How will you license the TCK from Sun.  Isn't it expensive?</dt>
+                    <dd>
+                        Sun offers scholarships to qualified non-profits, academics and individuals.
+                        Apache is a qualified non-profit, and has benefitted from this scholarship before,
+                        with the J2EE 1.4 TCK license and support for the Apache Geronimo project, among others.
+                   <br />
+                    We will apply for the scholarship, and hope that Sun will grant us the license
+                    and support needed for us to do a good job.
+                </dd>
+                    <dt>
+                        How long will it take?
+                    </dt>
+                    <dd>
+                        It will be done when it's done :) This will take a long time, but we hope that
+                        contributions from around the community will help us along the way.
+                    </dd>
+                    <dt>Do you have any code to start?
+                    </dt>
+                    <dd>
+                        No, we don't. We didn't want to "bless" any given implementation that might be donated
+                        (if such a thing could happen) but would rather let the community decide how it will
+                        create and develop the platform.
+                    </dd>
+                    <dt>Will you accept SWT if IBM offers it?</dt>
+                    <dd>
+                        Apache is always grateful for contributions from wherever they come, and IBM has a record
+                        of contributions to open source, but it would up to the project community to
+                        decide whether any particular contribution was used in the project.
+                    </dd>
+                
+                                  <dt>Why are you going to have an architecture thread?</dt>
+                    <dd>
+                        We wanted a way that we could bring together people from all over the Java community,
+                        even other open-source projects that are related. We welcome everyone to the discussion,
+                        no matter what license they choose to implement under, be it a free software license,
+                        an open source license or a proprietary license. We are here to open discussion and learning,
+                        and to design a great architecture for J2SE platforms.
+                    <br />
+                    At Apache, we think that a strong, diverse, meritocratic community is what makes a good
+                    open source project, and we want to be sure that everyone can participate in some way.
+                </dd>
+                <dt>Does this compete with Kaffe and Classpath?</dt>
+                    <dd>
+                        People from Kaffe and Classpath are helping start this project!
+                        Their experience in the open source VM and class library is invaluable,
+                        and they bring problems that the larger architecture community discussion can help solve.
+                    <br />
+                    We will have an implementation under the Apache License, but we think of this as
+                    complementary rather than competitive. And when we solve a few small license
+                    interoperability issues, we expect we'll be able to complement each other even more.
+                </dd>
+                <dt>How will you ensure that the intellectual property of Sun and others is respected?</dt>
+                                        <dd>
+                        Good question - this is a very important issue for us. There are several ways, but this
+                        will be a topic for the community to work on at the beginning. So far we've thought of:
+                                        <ul>
+                        <li>
+                            We shall ask any person that would be a committer to declare what kind of
+                            non-open-source class library or VM source code they have been exposed to,
+                            and allow us to keep them from participating in the related parts
+                            of the codebase where they may inadvertently violate the IP rights of someone else.
+                        </li>
+                        <li>
+                            We shall require that any code contribution that isn't a new, original work of
+                            authorship created expressly for the Apache Harmony project be subject to the
+                            standard Apache process for provenance and licensing to ensure that we have
+                            an accurate record of every contribution that wasn't created expressly inside
+                            the Apache Harmony project.
+                        </li>
+                        <li>
+                            We would like to perform continuous "surveillance" on the codebase we are building,
+                            and compare to class library and VMs from elsewhere, like Sun, IBM, BEA, Kaffe,
+                            etc to ensure that no code from those efforts become part of Apache Harmony
+                            without our knowledge. We do this to protect ourselves, our users, and of course
+                            those other efforts. We don't know yet how to do this, but are exploring ideas
+                            such as having a third party such as Black Duck or an existing licensee (or Sun!)
+                            do this for us. This, like all the topics herein, are open for discussion an change
+                            by the community.
+                        </li>
+                        <li>
+                            Anything anyone can think of!
+                        </li>
+                    </ul>
+                </dd>
+                    <dt>Won't this lead to fragmentation in the Java community?
+                    </dt>
+                    <dd>
+                        We don't think so. Our intent is to bring people together, let us share what we know,
+                        solve common problems, and collaborate on things where we can. A diverse Java community
+                        is a healthy Java community. Multiple implementations of the Java specifications show
+                        the value of Java - that we do have a specification, that anyone is free to make
+                        a compatible implementation, and that users of Java have the opportunity to run their Java
+                        code in more places, on more platforms. This is the central promise of Java, and we
+                        think that our efforts support this.
+                    </dd>
+                        <dt>
+                            How can I get involved and help influence and shape this proposal?
+                            Or is it too late?
+                        </dt>
+                    <dd>
+                        Join the community and participate! It's never too late! We're just getting started,
+                        and everything is open to discussion - the community will change what the
+                        community wants to change. What we do in this project is decided by those participating
+                        in the project. This is the Apache Software Foundation - collaborative, meritocratic,
+                        and community-based.
+                    </dd>
+              </dl>
 
-</section>
+        </section>
 
-</body>
+    </body>
 </document>
-   
+

Modified: harmony/standard/site/xdocs/hdk.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/hdk.xml?view=diff&rev=517682&r1=517681&r2=517682
==============================================================================
--- harmony/standard/site/xdocs/hdk.xml (original)
+++ harmony/standard/site/xdocs/hdk.xml Tue Mar 13 06:17:30 2007
@@ -1,13 +1,11 @@
 <?xml version="1.0" encoding="UTF-8"?>
-
 <!--
-
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
@@ -20,118 +18,133 @@
 
 <document>
 
- <properties>
-  <title>Harmony Development Kit for the Apache Harmony Class Library</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
-<body>
-
-<section name="Harmony Development Kit for the Apache Harmony Class Library">
-	<p>
-		The Harmony Development Kit (HDK) allows a Harmony developer to 
-		rebuild	any module of the Harmony Classlib in a standalone way by providing all the 
-		necesary supplementary binaries and header files. This document describes the layout 
-		of such an HDK and its contents.
-	</p>
-
-<subsection name="Layout of the HDK">
-	<p>
-		An HDK contains all the header files and binaries, both native and Java, required
-		for a Harmony classlib developer to build against. The directory structure for an
-		HDK is as follows:
-		<blockquote>
-		<pre>
-&lt;hdkbase&gt;
-     |
-     |---build
-     |     |---make
-     |     |---patternsets
-     |     \---test
-     |
-     |---jdk
-     |    |---jre
-     |    \---include
-     |
-     |---include
-     |
-     \---lib
-     
-		</pre>
-		</blockquote>
-		
-		The directories laid out above are used in the following manner:
-		
-		<ul>
-			<li><code>&lt;hdkbase&gt;/build/make</code> - this directory contains include
-			files used by native makefiles.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/build/patternsets</code> - this directory contains
-			patternsets describing jar content.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/build/test</code> - this directory contains test
-			support classes, bundled up into a jar file.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/jdk/jre</code> - this directory contains the standard
-			jre layout, including <code>bin</code> and <code>lib</code> directories.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/jdk/include</code> - this directory contains the standard
-			jdk header files. For example, jni.h is held here.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/include</code> - this directory contains header files that
-			are Harmony specific and are used across multiple classlib modules.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/lib</code> - this directory is used in HDKs on Windows for
-			.lib files and on Linux for .a files necessary for linking during compilation of 
-			classlib natives.
-			</li>
-		</ul>
-	</p>		
-</subsection>
-<subsection name="Building Classlib Against an HDK">
-	<p>
-		<i>Note: The HDK and relevant build system changes are work in progress. 
-		Not all of the Ant targets/properties described	exist yet, and thus not 
-		all of what is described below currently works. This disclaimer will be 
-		removed once work on the HDK is completed.</i><br/>
-		<br/>
-		The Harmony Class Library can be built at the global or modular level.
-		At the modular level, there are three ways to build:
-		<ul>
-			<li><b>Building the default target</b> - An HDK is not required here, and the class
-			library is built against and into the default (deploy) directory. This is the
-			standard way to build, and is what happens when you just run "ant" at the
-			command line.</li>
-			<li><b>Building against an HDK</b> - The location of an HDK must be specified at
-			the Ant command line, and the ouptut will be built into the default (deploy)
-			directory. The command line for this is "ant -DHY.HDK=path/to/HDK".</li>
-			<li><b>Building against an HDK and into a target directory</b> - The location of
-			an HDK and of a target directory must be specified on the Ant command line.
-			The Class Library code will be compiled against the libraries contained in
-			the HDK, and the output of those compiles will be placed into the specified
-			target directory. The command line for this is "ant -DHY.HDK=path/to/HDK
-			-DHY.TARGET=path/to/target".</li>
-		</ul>
-		
-		So, for example, if you wanted to build only the luni module against
-		an HDK, and put the resulting artifacts into a separate target directory,
-		you would do the following:
-		<ol>
-			<li>Checkout the luni module</li>
-			<li>cd into the root directory of the module</li>
-			<li>Execute "ant -DHY.HDK=path/to/hdk -DHY.TARGET=path/to/target"</li>
-		</ol>
-		The luni Java and native code will be built against the HDK location
-		specified, and all produced binaries placed under the target directory, laid
-		out in the HDK structure described at the top of this page.
-	</p>
-</subsection>
-</section>
-</body>
-</document>
\ No newline at end of file
+    <properties>
+        <title>Harmony Development Kit for the Apache Harmony Class Library</title>
+        <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    </properties>
+
+    <body>
+
+        <section name="Harmony Development Kit for the Apache Harmony Class Library">
+            <p>
+                The Harmony Development Kit (HDK) allows a Harmony developer to
+                rebuild any module of the Harmony Classlib in a standalone way by providing all the
+                necesary supplementary binaries and header files. This document describes the layout
+                of such an HDK and its contents.
+            </p>
+
+            <subsection name="Layout of the HDK">
+                <p>
+                    An HDK contains all the header files and binaries, both native and Java, required
+                    for a Harmony classlib developer to build against. The directory structure for an
+                    HDK is as follows:
+                    <pre>
+                    &lt;hdkbase&gt;
+                        |
+                        |---build
+                        |     |---make
+                        |     |---patternsets
+                        |     \---test
+                        |
+                        |---jdk
+                        |    |---jre
+                        |    \---include
+                        |
+                        |---include
+                        |
+                        \---lib
+                    </pre>
+
+                    The directories laid out above are used in the following manner:
+
+                    <ul>
+                        <li>
+                            <code>&lt;hdkbase&gt;/build/make</code> - this directory contains include
+                            files used by native makefiles.
+                        </li>
+
+                        <li>
+                            <code>&lt;hdkbase&gt;/build/patternsets</code> - this directory contains
+                            patternsets describing jar content.
+                        </li>
+
+                        <li>
+                            <code>&lt;hdkbase&gt;/build/test</code> - this directory contains test
+                            support classes, bundled up into a jar file.
+                        </li>
+
+                        <li>
+                            <code>&lt;hdkbase&gt;/jdk/jre</code> - this directory contains the standard
+                            jre layout, including <code>bin</code> and <code>lib</code> directories.
+                        </li>
+
+                        <li>
+                            <code>&lt;hdkbase&gt;/jdk/include</code> - this directory contains the standard
+                            jdk header files. For example, jni.h is held here.
+                        </li>
+
+                        <li>
+                            <code>&lt;hdkbase&gt;/include</code> - this directory contains header files that
+                            are Harmony specific and are used across multiple classlib modules.
+                        </li>
+
+                        <li>
+                            <code>&lt;hdkbase&gt;/lib</code> - this directory is used in HDKs on Windows for
+                            .lib files and on Linux for .a files necessary for linking during compilation of
+                            classlib natives.
+                        </li>
+                    </ul>
+                </p>
+            </subsection>
+            <subsection name="Building Classlib Against an HDK">
+                <p>
+                    <i>
+                        Note: The HDK and relevant build system changes are work in progress.
+                        Not all of the Ant targets/properties described exist yet, and thus not
+                        all of what is described below currently works. This disclaimer will be
+                        removed once work on the HDK is completed.
+                    </i><br/>
+                    <br/>
+                    The Harmony Class Library can be built at the global or modular level.
+                    At the modular level, there are three ways to build:
+                    <ul>
+                        <li>
+                            <b>Building the default target</b> - An HDK is not required here, and the class
+                            library is built against and into the default (deploy) directory. This is the
+                            standard way to build, and is what happens when you just run <code>ant</code> at the
+                            command line.
+                        </li>
+                        <li>
+                            <b>Building against an HDK</b> - The location of an HDK must be specified at
+                            the Ant command line, and the ouptut will be built into the default (deploy)
+                            directory. The command line for this is <code><nobr>ant -DHY.HDK=path/to/HDK</nobr></code>.
+                        </li>
+                        <li>
+                            <b>Building against an HDK and into a target directory</b> - The location of
+                            an HDK and of a target directory must be specified on the Ant command line.
+                            The Class Library code will be compiled against the libraries contained in
+                            the HDK, and the output of those compiles will be placed into the specified
+                            target directory. The command line for this is <code><nobr>ant -DHY.HDK=path/to/HDK
+                            -DHY.TARGET=path/to/target</nobr>
+                            </code>.
+                        </li>
+                    </ul>
+
+                    So, for example, if you wanted to build only the luni module against
+                    an HDK, and put the resulting artifacts into a separate target directory,
+                    you would do the following:
+                    <ol>
+                        <li>Checkout the luni module</li>
+                        <li>cd into the root directory of the module</li>
+                        <li>Execute <code>
+                            <nobr>ant -DHY.HDK=path/to/hdk -DHY.TARGET=path/to/target</nobr>
+                        </code></li>
+                    </ol>
+                    The luni Java and native code will be built against the HDK location
+                    specified, and all produced binaries placed under the target directory, laid
+                    out in the HDK structure described at the top of this page.
+                </p>
+            </subsection>
+        </section>
+    </body>
+</document>

Modified: harmony/standard/site/xdocs/index.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/index.xml?view=diff&rev=517682&r1=517681&r2=517682
==============================================================================
--- harmony/standard/site/xdocs/index.xml (original)
+++ harmony/standard/site/xdocs/index.xml Tue Mar 13 06:17:30 2007
@@ -2,11 +2,11 @@
 
 <!--
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
@@ -19,133 +19,132 @@
 
 <document>
 
-<properties>
-  <title>Open Source Java SE</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
-</properties>
-
-<body>
-
-  <section name="Welcome to Apache Harmony - Open Source Java SE">
-
-    <p>
-      <big>Welcome to Apache Harmony - Open Source Java SE.</big>
-    </p>
-    
-    <p>
-        Apache Harmony is
-        the Java SE project of the
-      <a href="http://www.apache.org/">Apache Software Foundation</a>.
-      Please help us make this a world class, certified implementation of the
-      Java Platform Standard Edition!
-    </p>
-
-   <p>
-      The aim of the project is to produce a large and healthy community
-      of those interested in runtime platforms tasked with creation of :
-   </p>
-   <ul>
-      <li>
-          A compatible, independent implementation of the Java SE 5
-          JDK under the Apache License v2
-      </li>
-      <li>
-          A community-developed modular runtime (VM and class library)
-          architecture.
-      </li>
-   </ul>
-
-   <p>
-       We aim to support wide range of different platforms.  The main criteria
-       for whether a particular platform is supported or not is the involvement
-       of people in running tests on regular base, reporting build status, finding
-       and fixing bugs for that platform, and so on.  We have
-       <a href="http://wiki.apache.org/harmony/Platforms_to_Run_Harmony_Development_Kit_on">a
-       list of platforms</a> we are actively maintaining at the moment.
-   </p>
-
-   <p>
-       Please see the following "Getting Started" guides :
-   </p>
-
-   <ul>
-       <li>
-           <a href="quickhelp_users.html">Getting Started for Harmony Users</a> : for those
-           that wish to use <a href="downloads.html">pre-built snapshots</a> of Apache Harmony
-       </li>
-       <li>
-           <a href="quickhelp_contributors.html">Getting Started for Harmony Contributors</a> : for those
-           that wish to checkout and build the source of Apache Harmony.
-       </li>
-   </ul>
-</section>
-
-    <section name="Harmony News">
-        <p>
-            <strong>Harmony Classlib Enabled Version of JRockit VM Available for Project Use</strong>
-            <blockquote>
-                BEA announced the <a href="http://dev2dev.bea.com/jrockit/jrockitVM">availability</a> of
-                an evaluation version of JRockit, their world-class JVM,  that works
-                with the Apache Harmony class library.  Distibuted by BEA under a binary, evaluation-only
-                license, this not only demonstrates the portablity of the 
-                <a href="subcomponents/classlibrary/index.html">Apache Harmony class library</a>, 
-                it also adds a valuable tool to help us as we continue building our independent implementation
-                of Java SE. 
-                (<i>2007-01-30</i>)
-            </blockquote>
-        </p>
-        <p>
-            <strong>JDK Snapshot Available</strong>
-            <blockquote>
+    <properties>
+        <title>Open Source Java SE</title>
+        <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    </properties>
+
+    <body>
+
+        <section name="Welcome to Apache Harmony - Open Source Java SE">
+
+            <p>
+                <big>Welcome to Apache Harmony - Open Source Java SE.</big>
+            </p>
+
+            <p>
+                Apache Harmony is
+                the Java SE project of the
+                <a href="http://www.apache.org/">Apache Software Foundation</a>.
+                Please help us make this a world class, certified implementation of the
+                Java Platform Standard Edition!
+            </p>
+
+            <p>
+                The aim of the project is to produce a large and healthy community
+                of those interested in runtime platforms tasked with creation of:
+            </p>
+            <ul>
+                <li>
+                    A compatible, independent implementation of the Java SE 5
+                    JDK under the Apache License v2
+                </li>
+                <li>
+                    A community-developed modular runtime (VM and class library)
+                    architecture.
+                </li>
+            </ul>
+
+            <p>
+                We aim to support wide range of different platforms. The main criteria
+                for whether a particular platform is supported or not is the involvement
+                of people in running tests on regular base, reporting build status, finding
+                and fixing bugs for that platform, and so on. We have
+                <a href="http://wiki.apache.org/harmony/Platforms_to_Run_Harmony_Development_Kit_on">
+                    a
+                    list of platforms
+                </a> we are actively maintaining at the moment.
+            </p>
+
+            <p>
+                Please see the following "Getting Started" guides:
+            </p>
+
+            <ul>
+                <li>
+                    <a href="quickhelp_users.html">Getting Started for Harmony Users</a>: for those
+                    that wish to use <a href="downloads.html">pre-built snapshots</a> of Apache Harmony
+                </li>
+                <li>
+                    <a href="quickhelp_contributors.html">Getting Started for Harmony Contributors</a>: for those
+                    that wish to checkout and build the source of Apache Harmony.
+                </li>
+            </ul>
+        </section>
+
+        <section name="Harmony News">
+            <h3>Harmony Classlib Enabled Version of JRockit VM Available for Project Use</h3>
+                <p>
+                    BEA announced the <a href="http://dev2dev.bea.com/jrockit/jrockitVM">availability</a> of
+                    an evaluation version of JRockit, their world-class JVM, that works
+                    with the Apache Harmony class library. Distibuted by BEA under a binary, evaluation-only
+                    license, this not only demonstrates the portablity of the
+                    <a href="subcomponents/classlibrary/index.html">Apache Harmony class library</a>,
+                    it also adds a valuable tool to help us as we continue building our independent implementation
+                    of Java SE.
+                    (<i>2007-01-30</i>)
+                </p>
+            <h3>JDK Snapshot Available</h3>
+            <p>
                 Apache Harmony now has a JDK snapshot available, that includes javac, keytool,
-                and others.  While not complete, it's our first step towards the standard
-                JDK distribution format expected by developers.  For more information, please
+                and others. While not complete, it's our first step towards the standard
+                JDK distribution format expected by developers. For more information, please
                 see our <a href="downloads.html">downloads</a> page.
                 (<i>2006-12-27</i>)
-            </blockquote>
-        </p>
-        <p>
-            <strong>Linux x86-64 (64-bit) Snapshots Available</strong>
-            <blockquote>
-                We now are including support for the x86-64 architecture under Linux. 
+            </p>
+            <h3>Linux x86-64 (64-bit) Snapshots Available</h3>
+            <p>
+                We now are including support for the x86-64 architecture under Linux.
                 For more information, please
                 see our <a href="downloads.html">downloads</a> page.
                 (<i>2006-12-14</i>)
-            </blockquote>
-        </p>
-        <p>
-            <strong>Apache Harmony: Top-Level Project of the Apache Software Foundation</strong>
-            <blockquote>
-                Apache Harmony is now a top-level project of the Apache Software Foundation. 
-                On October 25th, the Board of Directors voted to make Apache Harmony a
-                top-level project, and on October 29th the Apache Incubator PMC voted to
-                graduate Harmony from the Apache Incubator, having satisfied the Incubator's
-                requirements for community governance and IP oversight.  We're in the process
-                of transitioning our resources and infrastructure over, so please be patient
-                while we do our move.
-                (<i>2006-10-29</i>)
-            </blockquote>
-        </p>
-  <p>
-  <i>Archived articles are <a href="newshistory.html">here</a></i>.
-  </p>
-</section>
-
-<section name="Project Status">
-
-    <p>
-        How are we doing?  We're making steady progress : 
-    </p>
-
-    <ol>
-        <li>JRE and HDK snapshots <a href="http://people.apache.org/builds/harmony/snapshots/">available</a> </li>
-        <li>
-            JRE can run popular programs like Apache Tomcat, Eclipse, Maven, Derby, Ant
-        </li>
-        <li>More than 95% of Java 5 API complete. (not compatible, just completed)</li>
-        <li>More than 1.25 Million Lines of Code</li>
-    </ol>
-</section>
+            </p>
+            <h3>Apache Harmony: Top-Level Project of the Apache Software Foundation</h3>
+                <p>
+                    Apache Harmony is now a top-level project of the Apache Software Foundation.
+                    On October 25th, the Board of Directors voted to make Apache Harmony a
+                    top-level project, and on October 29th the Apache Incubator PMC voted to
+                    graduate Harmony from the Apache Incubator, having satisfied the Incubator's
+                    requirements for community governance and IP oversight. We're in the process
+                    of transitioning our resources and infrastructure over, so please be patient
+                    while we do our move.
+                    (<i>2006-10-29</i>)
+                </p>
+                        <p>
+                <i>
+                    Archived articles are <a href="newshistory.html">here</a></i>.
+            </p>
+        
+        
+        </section>
+
+        <section name="Project Status">
+
+            <p>
+                How are we doing?  We're making steady progress :
+            </p>
+
+            <ol>
+                <li>
+                    JRE and HDK snapshots <a href="http://people.apache.org/builds/harmony/snapshots/">available</a>
+                </li>
+                <li>
+                    JRE can run popular programs like Apache Tomcat, Eclipse, Maven, Derby, Ant
+                </li>
+                <li>More than 95% of Java 5 API complete. (not compatible, just completed)</li>
+                <li>More than 1.25 Million Lines of Code</li>
+            </ol>
+        </section>
 
-</body>
+    </body>
 </document>

Modified: harmony/standard/site/xdocs/issue_resolution_guideline.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/issue_resolution_guideline.xml?view=diff&rev=517682&r1=517681&r2=517682
==============================================================================
--- harmony/standard/site/xdocs/issue_resolution_guideline.xml (original)
+++ harmony/standard/site/xdocs/issue_resolution_guideline.xml Tue Mar 13 06:17:30 2007
@@ -19,13 +19,13 @@
 <document>
 
 <properties>
-	<title>Good Issue Resolution Guideline</title>
-	<author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    <title>Good Issue Resolution Guideline</title>
+    <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
 </properties>
 
 <body>
 
-	<section name="Good Issue Resolution Guideline">
+    <section name="Good Issue Resolution Guideline">
     <p>
       This guideline provides step-by-step instructions on reporting, resolving 
       and closing issues. If you cannot do one of the steps, then write a comment to the issue.

Modified: harmony/standard/site/xdocs/mailing.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/mailing.xml?view=diff&rev=517682&r1=517681&r2=517682
==============================================================================
--- harmony/standard/site/xdocs/mailing.xml (original)
+++ harmony/standard/site/xdocs/mailing.xml Tue Mar 13 06:17:30 2007
@@ -1,12 +1,11 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-
 <!--
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
@@ -19,175 +18,200 @@
 
 <document>
 
- <properties>
-  <title>Apache Harmony Mailing Lists</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
-<body>
-<section name="Apache Harmony Mailing Lists">
-
-<p>
-Apache Harmony mailing lists operate under the following terms :
-</p>
-
-<blockquote>
-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.
-</blockquote>
->
- 
-<p>
-Further :
-</p>
-
-<blockquote>
-<ul>
-<li>
-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.
-</li>
-<li>
-Do not post any code that is not your original work, or code that you do not have 
-clear authorization to contribute.
-</li>
-<li>
-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.
-</li>
-<li>
-Under no circumstances will any committer accept code for inclusion in our SVN 
-repository contributed on the mailing list unless
-it is from an
-<a href="contribution_policy.html">Authorized Contributor</a>.
-</li>
-</ul>
-</blockquote>
-<p>
-There are currently three publicly available mailing lists for Harmony :
-</p>
-
-<subsection name="Developer Mailing List">
-
-<p>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
-    <a href="get-involved.html#irc-channel">IRC</a> as
-well.</p>
-<ul>
-  <li><a href="mailto:dev-subscribe@harmony.apache.org">Subscribe</a> to dev@harmony.apache.org</li>
-  <li><a href="mailto:dev-unsubscribe@harmony.apache.org">Unsubscribe</a> from dev@harmony.apache.org</li>
-  <li>View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/">harmony-dev@incubator.apache.org archives (May 2005 - Oct 2006)</a></li>
-  <li>View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/">dev@harmony.apache.org archives (Nov 2006 onwards)</a></li>
-</ul>
-
-<p>
-    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.
-</p>
-<p>
-    In order to help people sort and make sense of the traffic, please prefix your
-    subject line with an appropriate token :
-</p>
-    <ul>
-        <li>
-            [general] - for things of general interest
-        </li>
-        <li>
-            [announce] - announcements
-        </li>
-        <li>
-            [legal] - discussion about legal issues
-        </li>
-        <li>
-            [classlib]<i>[module]</i> - for classlibrary-related
-             issues (and you can optionally specify the specific module)
-        </li>
-        <li>
-            [drlvm]<i>[module]</i> - for DRLVM-related
-             issues (and you can optionally specify the specific module)
-        </li>
-        <li>
-            [jchevm]<i>[module]</i> - for jchevm-related
-             issues (and you can optionally specify the specific module)
-        </li>
-        <li>
-            [bootvm]<i>[module]</i> - for bootvm-related
-             issues (and you can optionally specify the specific module)
-        </li>
-        <li>
-            [doc] - for documentation-related issues
-        </li>
-        <li>
-            [tools] - for tools-related issues
-        </li>
-        <li>
-            [testing] or [qa] - for tools-related issues
-        </li>
-    </ul>
-
-    <p>
-        Simply add the token to the start of your subject line.  For example :
-   </p>
-
-    <source>
-        To : dev@harmony.apache.org
-        From : harmony_user@openjava.org
-        Subject : [classlib][io] Problem with java.io.OutputSocket
-
-        ....
-    </source>
-</subsection>
-
-<subsection name="Source Control Mailing List">
-
-<p>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
-<a href="http://issues.apache.org/jira/browse/HARMONY">JIRA issue tracking system</a>.</p>
-<ul>
-  <li><a href="mailto:commits-subscribe@harmony.apache.org">Subscribe</a> to commits@harmony.apache.org</li>
-  <li><a href="mailto:commits-unsubscribe@harmony.apache.org">Unsubscribe</a> from commits@harmony.apache.org</li>
-  <li>View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-harmony-commits/">harmony-commits@incubator.apache.org archives (May 2005 -Oct 2006)</a></li>
-  <li>View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-commits/">commits@harmony.apache.org archives (Nov 2006 onwards)</a></li>
-</ul>
-
-</subsection>
-
-<subsection name="Alerts Mailing List">
-
-<p>
-This list receives alerts from the various community-run build systems.  These alerts contain
-information on failed builds and test runs.
-</p>
-<ul>
-  <li><a href="mailto:alerts-subscribe@harmony.apache.org">Subscribe</a> to alerts@harmony.apache.org</li>
-  <li><a href="mailto:alerts-unsubscribe@harmony.apache.org">Unsubscribe</a> from alerts@harmony.apache.org</li>
-  <li>View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-alerts/">alerts@harmony.apache.org archives</a></li>
-</ul>
-
-</subsection>
-
-<subsection name="Other Mailing Lists">
-
-<p>The Harmony PMC has a mailing list to resolve any administrative issues,
-This list is limited to PMC members (most committers on the project).</p>
-
-</subsection>
-</section>
-</body>
+    <properties>
+        <title>Apache Harmony Mailing Lists</title>
+        <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    </properties>
+
+    <body>
+        <section name="Apache Harmony Mailing Lists">
+
+            <p>
+                Apache Harmony mailing lists operate under the following terms :
+            </p>
+            <ul>
+                <li>
+                    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).
+                </li>
+                <li>
+                    All communication intentionally submitted to the Foundation on this
+                    forum is considered a Contribution to the Foundation unless otherwise
+                    noted in the communication.
+                </li>
+                <li>
+                    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.
+                </li>
+                <li>
+                    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.
+                </li>
+                <li>
+                    Do not post any code that is not your original work, or code that you do not have
+                    clear authorization to contribute.
+                </li>
+                <li>
+                    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.
+                </li>
+                <li>
+                    Under no circumstances will any committer accept code for inclusion in our SVN
+                    repository contributed on the mailing list unless it is from an
+                    <a href="contribution_policy.html">Authorized Contributor</a>.
+                </li>
+            </ul>
+            <p>
+                There are currently three publicly available mailing lists for Harmony :
+            </p>
+
+            <subsection name="Developer Mailing List">
+
+                <p>
+                    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
+                    <a href="get-involved.html#irc-channel">IRC</a> as
+                    well.
+                </p>
+                <ul>
+                    <li>
+                        <a href="mailto:dev-subscribe@harmony.apache.org">Subscribe</a> to dev@harmony.apache.org
+                    </li>
+                    <li>
+                        <a href="mailto:dev-unsubscribe@harmony.apache.org">Unsubscribe</a> from dev@harmony.apache.org
+                    </li>
+                    <li>
+                        View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/">harmony-dev@incubator.apache.org archives (May 2005 - Oct 2006)</a>
+                    </li>
+                    <li>
+                        View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/">dev@harmony.apache.org archives (Nov 2006 onwards)</a>
+                    </li>
+                </ul>
+
+                <p>
+                    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.
+                </p>
+                <p>
+                    In order to help people sort and make sense of the traffic, please prefix your
+                    subject line with an appropriate token:
+                </p>
+                <ul>
+                    <li>
+                        [general] - for things of general interest
+                    </li>
+                    <li>
+                        [announce] - announcements
+                    </li>
+                    <li>
+                        [legal] - discussion about legal issues
+                    </li>
+                    <li>
+                        [classlib]<i>[module]</i> - for classlibrary-related
+                        issues (and you can optionally specify the specific module)
+                    </li>
+                    <li>
+                        [drlvm]<i>[module]</i> - for DRLVM-related
+                        issues (and you can optionally specify the specific module)
+                    </li>
+                    <li>
+                        [jchevm]<i>[module]</i> - for jchevm-related
+                        issues (and you can optionally specify the specific module)
+                    </li>
+                    <li>
+                        [bootvm]<i>[module]</i> - for bootvm-related
+                        issues (and you can optionally specify the specific module)
+                    </li>
+                    <li>
+                        [doc] - for documentation-related issues
+                    </li>
+                    <li>
+                        [tools] - for tools-related issues
+                    </li>
+                    <li>
+                        [testing] or [qa] - for tools-related issues
+                    </li>
+                </ul>
+
+                <p>
+                    Simply add the token to the start of your subject line. For example :
+                </p>
+
+                <source>
+                    To : dev@harmony.apache.org
+                    From : harmony_user@openjava.org
+                    Subject : [classlib][io] Problem with java.io.OutputSocket
+
+                    ....
+                </source>
+            </subsection>
+
+            <subsection name="Source Control Mailing List">
+
+                <p>
+                    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
+                    <a href="http://issues.apache.org/jira/browse/HARMONY">JIRA issue tracking system</a>.
+                </p>
+                <ul>
+                    <li>
+                        <a href="mailto:commits-subscribe@harmony.apache.org">Subscribe</a> to commits@harmony.apache.org
+                    </li>
+                    <li>
+                        <a href="mailto:commits-unsubscribe@harmony.apache.org">Unsubscribe</a> from commits@harmony.apache.org
+                    </li>
+                    <li>
+                        View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-harmony-commits/">harmony-commits@incubator.apache.org archives (May 2005 -Oct 2006)</a>
+                    </li>
+                    <li>
+                        View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-commits/">commits@harmony.apache.org archives (Nov 2006 onwards)</a>
+                    </li>
+                </ul>
+
+            </subsection>
+
+            <subsection name="Alerts Mailing List">
+
+                <p>
+                    This list receives alerts from the various community-run build systems. These alerts contain
+                    information on failed builds and test runs.
+                </p>
+                <ul>
+                    <li>
+                        <a href="mailto:alerts-subscribe@harmony.apache.org">Subscribe</a> to alerts@harmony.apache.org
+                    </li>
+                    <li>
+                        <a href="mailto:alerts-unsubscribe@harmony.apache.org">Unsubscribe</a> from alerts@harmony.apache.org
+                    </li>
+                    <li>
+                        View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-alerts/">alerts@harmony.apache.org archives</a>
+                    </li>
+                </ul>
+
+            </subsection>
+
+            <subsection name="Other Mailing Lists">
+
+                <p>
+                    The Harmony PMC has a mailing list to resolve any administrative issues,
+                    This list is limited to PMC members (most committers on the project).
+                </p>
+
+            </subsection>
+        </section>
+    </body>
 </document>
+
+
 
 



Mime
View raw message