incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r371723 [1/4] - in /incubator/public/trunk/site: ./ xdocs/ xdocs/ipclearance/ xdocs/projects/ xdocs/stylesheets/
Date Mon, 23 Jan 2006 23:58:43 GMT
Author: crossley
Date: Mon Jan 23 15:58:11 2006
New Revision: 371723

URL: http://svn.apache.org/viewcvs?rev=371723&view=rev
Log:
Do 'svn propset svn:eol-style native' for all text files.

Modified:
    incubator/public/trunk/site/.classpath   (contents, props changed)
    incubator/public/trunk/site/.project   (contents, props changed)
    incubator/public/trunk/site/build.xml   (props changed)
    incubator/public/trunk/site/xdocs/chair_guide.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/faq.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/general_guide.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/how_to_participate.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/how_we_work.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/incubation_policy.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/index.xml   (props changed)
    incubator/public/trunk/site/xdocs/ipclearance/index.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/license.xml   (props changed)
    incubator/public/trunk/site/xdocs/mailing.xml   (props changed)
    incubator/public/trunk/site/xdocs/newshistory.xml   (props changed)
    incubator/public/trunk/site/xdocs/pmc_guide.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/process_description.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/projects/activemq.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/projects/project_template.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/projects/projects.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/projects_and_mentors_guide.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/roles_and_responsibilities.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/stylesheets/project.xml   (props changed)
    incubator/public/trunk/site/xdocs/stylesheets/site.vsl   (props changed)
    incubator/public/trunk/site/xdocs/svn.xml   (props changed)
    incubator/public/trunk/site/xdocs/template.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/website_guide.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/what_we_do.xml   (contents, props changed)
    incubator/public/trunk/site/xdocs/who_we_are.xml   (contents, props changed)

Modified: incubator/public/trunk/site/.classpath
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/.classpath?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/.classpath (original)
+++ incubator/public/trunk/site/.classpath Mon Jan 23 15:58:11 2006
@@ -1,10 +1,10 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
-	<classpathentry kind="lib" path="lib/commons-collections.jar"/>
-	<classpathentry kind="lib" path="lib/jdom-b10-rc1.jar"/>
-	<classpathentry kind="lib" path="lib/logkit-1.0.1.jar"/>
-	<classpathentry kind="lib" path="lib/oro.jar"/>
-	<classpathentry kind="lib" path="lib/velocity-1.5-dev.jar"/>
-	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
-	<classpathentry kind="output" path="bin"/>
-</classpath>
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+	<classpathentry kind="lib" path="lib/commons-collections.jar"/>
+	<classpathentry kind="lib" path="lib/jdom-b10-rc1.jar"/>
+	<classpathentry kind="lib" path="lib/logkit-1.0.1.jar"/>
+	<classpathentry kind="lib" path="lib/oro.jar"/>
+	<classpathentry kind="lib" path="lib/velocity-1.5-dev.jar"/>
+	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+	<classpathentry kind="output" path="bin"/>
+</classpath>

Propchange: incubator/public/trunk/site/.classpath
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/.project
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/.project?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/.project (original)
+++ incubator/public/trunk/site/.project Mon Jan 23 15:58:11 2006
@@ -1,17 +1,17 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>harmony-site</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.jdt.core.javabuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.jdt.core.javanature</nature>
-	</natures>
-</projectDescription>
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>harmony-site</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.eclipse.jdt.core.javabuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.eclipse.jdt.core.javanature</nature>
+	</natures>
+</projectDescription>

Propchange: incubator/public/trunk/site/.project
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/public/trunk/site/build.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/xdocs/chair_guide.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/chair_guide.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/chair_guide.xml (original)
+++ incubator/public/trunk/site/xdocs/chair_guide.xml Mon Jan 23 15:58:11 2006
@@ -1,152 +1,152 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="Incubator Chair Guide">
-
-<p>Some things can only be done by the Incubator Chair. </p>
-
-<subsection name="Adding a new PMC member">
-
-<p>1. Be sure that the person you're adding has been voted by the PMC or is one of
the designated Mentors for a project </p>
-<p>2. Send this mail: </p>
-<pre>
-To: board@apache.org
-CC: pmc@incubator.apache.org
-CC: address(es) of the new pmc member(s)
-
-Subject: [PLEASE ACK] New Incubator PMC member(s): Member1, Member2, ...
-Body:
-
-The Incubator PMC is adding (a) new member(s):
-
- Member1 &lt;member1@apache.org&gt; (ProjectX Mentor)
- Member2 &lt;member2@apache.org&gt; (voted...)
-
-Please ACK.
-
-Explanation of the process
----------------------------
-A chair can add a new PMC member, but it must notify the board first.
-72 hours after a board member has ACKed this request, and no other from
-the board objects, the person is officially part of the PMC. 
-
-For the new member(s)
----------------------------
-general-subscribe@incubator.apache.org
-pmc-subscribe@incubator.apache.org
-</pre>
-
-<p>If he is a Mentor, coming in with a project, you may want to add this  to the mail:
</p>
-
-<pre>
-Note about adding Mentors
----------------------------
-I note that he has not been voted in with a 
-"[VOTE] Name Surmane as PMC member" but has nevertheless 
-been accepted as being the Mentor of a project, that 
-*has* been accepted. 
-</pre>
-<p>3. Add the person to the incubator CVS avail </p>
-<p>3. Wait 72 hours after the ACK of a board member </p>
-<p>4. After 72 hours without problems, add the person to: </p>
-<ul>
-<li>http://cvs.apache.org/viewcvs.cgi/incubator/site/whoweare.cwiki?view=markup </li>
-<li>apachecvs/committers/board/committee-info.txt 5. Mail the new member this welcome
message. </li>
-</ul>
-<pre>
-Welcome in the Apache Incubator Project.
-
-Here is some information to get you started as a PMC member.
-
- - please subscribe to the incubator mailing lists:
-    - general-subscribe@incubator.apache.org
-    - pmc-subscribe@incubator.apache.org
-    - incubator-cvs-subscribe@apache.org
-    - ADD OTHER LISTS HERE
-     (optionally) 
-    - incubator-site-cvs-subscribe@apache.org
-     
- - the incubator CVS modules are:
-    - incubator
-    - incubator-site
-    - ADD OTHER CVS MODULES HERE
- 
- - all the public information, rules and policies about the
-   Apache Incubator is in the 'incubator' CVS module under
-   site/**, and thus published on http://incubator.apache.org/
-
- - the incubator/site/whoweare.wiki page lists all project
-   members, as is also registered in the CVS module
-   'committers' under board/committee-info.txt
-
- - the Incubator website is published by committing the 
-   Forrest-generated docs in the 'incubator-site' CVS module
-   http://incubator.apache.org/howtoparticipate.html#website
-   
- - all private information for the Incubator PMC is  
-   ADD PRIVATE RESOURCES HERE
-
- - all Incubator PMC members have full access to all CVS
-   repositories (also of the incubating projects for
-   oversight purposes) and are wiki admins
-
- - status documents about Incubating projects are under 
-   incubator/site-author/project/ directory; please keep the ones you are 
-   mentoring updated
-
- - all committers on all incubating projects have access to
-   the 'incubator' and 'incubator-site' CVS modules, so they can
-   participate in the general Incubator Project as committers
-
- - please read our work documents under incubator/site-author/incubation/
-   for more information about the incubation process; they are
-   published under http://incubator.apache.org/incubation/
-
-Thanks for helping us :-)
-</pre>
-
-</subsection>
-<subsection name="Making the Board Report">
-
-<p>The Chair must remember to send the board a status report of the Incubator Project.
</p>
-<p>The dates of the meetings and the months in which to send in a report can be found
in the  <span class="codefrag">committers</span> CVS module under  <span class="codefrag">board/</span>
. </p>
-<p>It's  <em>important</em> that the report is sent  <em>at least</em>
two days before the scheduled meeting. </p>
-<p>The Chair should also ensure that the Incubating projects have prior notice of this
so that they can send in their Incubation Report. It's advisable to ask them at least 3 weeks
prior the meeting, so that the Incubator Project can review and discuss them. </p>
-<p>Here is a board report boilerplate: </p>
-<pre>
-Status report for the Apache Incubator Project
-
-* Noteable happening's in the Incubator
-
-* what code releases have been made? [since the last report]
-
-* any new projects in process of being accepted?
-
-* any legal issues to bring to the board?
-
-* any cross-project issues that need to be addressed?
-
-* any problems with committers, members, etc?
-
-* plans and expectations for the next period?
-
-</pre>
-
-</subsection>
-<subsection name="Asking for Incubation Reports">
-
-<p>At least when there is a board report due, or when it seemes needed, the Chair can
ask a project for an Incubation Report. This helps in assessing the status of the project
and eventually vote for the exit from incubation. </p>
-
-</subsection>
-</section>
-
-</body>
-</document>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Incubator Chair Guide">
+
+<p>Some things can only be done by the Incubator Chair. </p>
+
+<subsection name="Adding a new PMC member">
+
+<p>1. Be sure that the person you're adding has been voted by the PMC or is one of
the designated Mentors for a project </p>
+<p>2. Send this mail: </p>
+<pre>
+To: board@apache.org
+CC: pmc@incubator.apache.org
+CC: address(es) of the new pmc member(s)
+
+Subject: [PLEASE ACK] New Incubator PMC member(s): Member1, Member2, ...
+Body:
+
+The Incubator PMC is adding (a) new member(s):
+
+ Member1 &lt;member1@apache.org&gt; (ProjectX Mentor)
+ Member2 &lt;member2@apache.org&gt; (voted...)
+
+Please ACK.
+
+Explanation of the process
+---------------------------
+A chair can add a new PMC member, but it must notify the board first.
+72 hours after a board member has ACKed this request, and no other from
+the board objects, the person is officially part of the PMC. 
+
+For the new member(s)
+---------------------------
+general-subscribe@incubator.apache.org
+pmc-subscribe@incubator.apache.org
+</pre>
+
+<p>If he is a Mentor, coming in with a project, you may want to add this  to the mail:
</p>
+
+<pre>
+Note about adding Mentors
+---------------------------
+I note that he has not been voted in with a 
+"[VOTE] Name Surmane as PMC member" but has nevertheless 
+been accepted as being the Mentor of a project, that 
+*has* been accepted. 
+</pre>
+<p>3. Add the person to the incubator CVS avail </p>
+<p>3. Wait 72 hours after the ACK of a board member </p>
+<p>4. After 72 hours without problems, add the person to: </p>
+<ul>
+<li>http://cvs.apache.org/viewcvs.cgi/incubator/site/whoweare.cwiki?view=markup </li>
+<li>apachecvs/committers/board/committee-info.txt 5. Mail the new member this welcome
message. </li>
+</ul>
+<pre>
+Welcome in the Apache Incubator Project.
+
+Here is some information to get you started as a PMC member.
+
+ - please subscribe to the incubator mailing lists:
+    - general-subscribe@incubator.apache.org
+    - pmc-subscribe@incubator.apache.org
+    - incubator-cvs-subscribe@apache.org
+    - ADD OTHER LISTS HERE
+     (optionally) 
+    - incubator-site-cvs-subscribe@apache.org
+     
+ - the incubator CVS modules are:
+    - incubator
+    - incubator-site
+    - ADD OTHER CVS MODULES HERE
+ 
+ - all the public information, rules and policies about the
+   Apache Incubator is in the 'incubator' CVS module under
+   site/**, and thus published on http://incubator.apache.org/
+
+ - the incubator/site/whoweare.wiki page lists all project
+   members, as is also registered in the CVS module
+   'committers' under board/committee-info.txt
+
+ - the Incubator website is published by committing the 
+   Forrest-generated docs in the 'incubator-site' CVS module
+   http://incubator.apache.org/howtoparticipate.html#website
+   
+ - all private information for the Incubator PMC is  
+   ADD PRIVATE RESOURCES HERE
+
+ - all Incubator PMC members have full access to all CVS
+   repositories (also of the incubating projects for
+   oversight purposes) and are wiki admins
+
+ - status documents about Incubating projects are under 
+   incubator/site-author/project/ directory; please keep the ones you are 
+   mentoring updated
+
+ - all committers on all incubating projects have access to
+   the 'incubator' and 'incubator-site' CVS modules, so they can
+   participate in the general Incubator Project as committers
+
+ - please read our work documents under incubator/site-author/incubation/
+   for more information about the incubation process; they are
+   published under http://incubator.apache.org/incubation/
+
+Thanks for helping us :-)
+</pre>
+
+</subsection>
+<subsection name="Making the Board Report">
+
+<p>The Chair must remember to send the board a status report of the Incubator Project.
</p>
+<p>The dates of the meetings and the months in which to send in a report can be found
in the  <span class="codefrag">committers</span> CVS module under  <span class="codefrag">board/</span>
. </p>
+<p>It's  <em>important</em> that the report is sent  <em>at least</em>
two days before the scheduled meeting. </p>
+<p>The Chair should also ensure that the Incubating projects have prior notice of this
so that they can send in their Incubation Report. It's advisable to ask them at least 3 weeks
prior the meeting, so that the Incubator Project can review and discuss them. </p>
+<p>Here is a board report boilerplate: </p>
+<pre>
+Status report for the Apache Incubator Project
+
+* Noteable happening's in the Incubator
+
+* what code releases have been made? [since the last report]
+
+* any new projects in process of being accepted?
+
+* any legal issues to bring to the board?
+
+* any cross-project issues that need to be addressed?
+
+* any problems with committers, members, etc?
+
+* plans and expectations for the next period?
+
+</pre>
+
+</subsection>
+<subsection name="Asking for Incubation Reports">
+
+<p>At least when there is a board report due, or when it seemes needed, the Chair can
ask a project for an Incubation Report. This helps in assessing the status of the project
and eventually vote for the exit from incubation. </p>
+
+</subsection>
+</section>
+
+</body>
+</document>

Propchange: incubator/public/trunk/site/xdocs/chair_guide.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/xdocs/faq.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/faq.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/faq.xml (original)
+++ incubator/public/trunk/site/xdocs/faq.xml Mon Jan 23 15:58:11 2006
@@ -1,143 +1,143 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="FAQ">
-
-<strong>
-Does the X Project really have to go in the Incubator to get to Apache?
-</strong>
-
-        <p>
-          Yes.
-        </p>
-        <p>Code that has existed outside the asf can <strong>only</strong>
enter 
-           the ASF through the Incubator.  There is no other option.  
-        </p>
-        <p>The Incubator, among other thingsm is where the due-diligence of 
-           making sure the licence is correct, the copyright is assigned, 
-           and all of the initial developers submit their clas.
-        </p>
-
-<strong>
-I'm the mentor of this project, and I think that I'm able to do it by myself.
-        The Incubator doesn't add anything, can it be skipped?
-</strong>
-
-        <p>No.</p> 
-        
-        <p>Do it right, do it well, and add something in the process. </p> 
-
-        <p> Incubation is not about handing it over to some other group and 
-            seeing what happens. The Incubator is simply the name of the place 
-            that governs your actions when you process a new project into Apache.  
-            It moves at the same rate you do, and achieves whatever you achieve 
-            -- the only difference is that we have a permanent record in <strong>one</strong>
-            place that we can go back to if there are later IP problems, and there 
-            is a gate that must be passed through before the project is given 
-            the right to release software on behalf of the ASF.  
-            That gate will not be ignored or bypassed just because one group or 
-            another feels they have earned the right to bypass it; allowing that 
-            kind of exception destroys the potential to build a tradition of effective 
-            oversight, which is the reason we created incubator.
-        </p>
-
-<strong>
-Project XXX makes no mention of the Incubator for accepting new projects, but the 
-Incubator site says that all projects entering Apache must pass the Incubator.
-What do we need to do, to move to the Apache XXX project?
-</strong>
-
-        <p>The incubation process, WRT responsibilities, is roughly as follows:</p>
-          <ol>
-            <li>Any Apache PMC (project management commitee) or the Apache board 
-                approves the entrance of a project at Apache. They are the Sponsor.</li>
-                
-            <li>The Incubator is from that moment on responsible for the project, which

-                will remain so till the Incubator votes for it to be "graduated" to the 
-                PMC that asked for it. If the PMC was the Incubator itself or the board,

-                the project will have its own PMC.</li>
-
-            <li>Incubation complete.</li>
-          </ol>  
-         <p>So, since you would like to have a place under the XXX Project, ask there
to 
-          vote for acceptance. After that vote, you will automatically be under the Incubator,

-          and incubation will take place.
-        </p>
-
-
-<strong>
-Someone has proposed that their code/project be donated to project X
-within the ASF for continued development.  What do we need to do to 
-accept the code?
-</strong>
-
-		<p>
-		  The Incubator will only accept code for incubation if a PMC (project
-		  management committee) or the Apache board has voted to accept it.
-		  So when a proposal for the donation of code occurs, the project in
-		  question should discuss the proposal internally, leading to a
-		  decision by that project's PMC on whether or not to accept the code
-		  (and potentially the project surrounding it) into the fold.
-		</p>
-		<p>
-		  If the PMC agrees, then the incubator can be approached, and the
-		  code accepted for incubation.
-      The grant needs to be recorded by following the procedure
-      outlined at the
-      <link href="http://www.apache.org/licenses/">Software Grants</link>
-      section of the ASF Licenses page.
-		</p>
-
-
-<strong>
-How can I update the site?
-</strong>
-
-      <p>Refer to <a href="/how_to_participate.html">How to Participate</a>
-       page. If you are not a committer on the Incubator project, then you can
-       still send patches for the source documents.</p>
-
-
-<strong>
-How do I update the incubation status of a project?
-</strong>
-
-       <p>Look in the incubator SVN module, under site-author/projects/projectname.html
-         (Note: Some projects still use old *.cwiki as the input format - not recommended.)
-       </p>
-       <p>
-         See the <link href="site:guides/website">instructions</link>
-         for updating the website.
-       </p>
-
-<strong>
-Why don't we use an issue tracking system to track incubation process?
-</strong>
-
-       <p>AFAIK, issue trackers do not authenticate that the person entering 
-          the status information has the authority to do so, which is what we
-          get with the Subversion source control process.</p>
-       <p>Note that how the actual day to day tracking is done is not relevant, 
-          and any means, even an issue tracker can be used.</p>
-       <p>Nevertheless, SVN is our only authorative and formal tracking system
-          for incubation status.</p>
-
-
-<strong>
-How do I update the site of an incubating project?
-</strong>
-
-       <p>First of all, read our <link href="site:incubation/policy">Incubation
Policy</link>.</p>
-       <p>Refer to <link href="howtoparticipate.html#project-website">How to
Participate</link> page.</p>
-    
-</section>
-</body>
-</document>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="FAQ">
+
+<strong>
+Does the X Project really have to go in the Incubator to get to Apache?
+</strong>
+
+        <p>
+          Yes.
+        </p>
+        <p>Code that has existed outside the asf can <strong>only</strong>
enter 
+           the ASF through the Incubator.  There is no other option.  
+        </p>
+        <p>The Incubator, among other thingsm is where the due-diligence of 
+           making sure the licence is correct, the copyright is assigned, 
+           and all of the initial developers submit their clas.
+        </p>
+
+<strong>
+I'm the mentor of this project, and I think that I'm able to do it by myself.
+        The Incubator doesn't add anything, can it be skipped?
+</strong>
+
+        <p>No.</p> 
+        
+        <p>Do it right, do it well, and add something in the process. </p> 
+
+        <p> Incubation is not about handing it over to some other group and 
+            seeing what happens. The Incubator is simply the name of the place 
+            that governs your actions when you process a new project into Apache.  
+            It moves at the same rate you do, and achieves whatever you achieve 
+            -- the only difference is that we have a permanent record in <strong>one</strong>
+            place that we can go back to if there are later IP problems, and there 
+            is a gate that must be passed through before the project is given 
+            the right to release software on behalf of the ASF.  
+            That gate will not be ignored or bypassed just because one group or 
+            another feels they have earned the right to bypass it; allowing that 
+            kind of exception destroys the potential to build a tradition of effective 
+            oversight, which is the reason we created incubator.
+        </p>
+
+<strong>
+Project XXX makes no mention of the Incubator for accepting new projects, but the 
+Incubator site says that all projects entering Apache must pass the Incubator.
+What do we need to do, to move to the Apache XXX project?
+</strong>
+
+        <p>The incubation process, WRT responsibilities, is roughly as follows:</p>
+          <ol>
+            <li>Any Apache PMC (project management commitee) or the Apache board 
+                approves the entrance of a project at Apache. They are the Sponsor.</li>
+                
+            <li>The Incubator is from that moment on responsible for the project, which

+                will remain so till the Incubator votes for it to be "graduated" to the 
+                PMC that asked for it. If the PMC was the Incubator itself or the board,

+                the project will have its own PMC.</li>
+
+            <li>Incubation complete.</li>
+          </ol>  
+         <p>So, since you would like to have a place under the XXX Project, ask there
to 
+          vote for acceptance. After that vote, you will automatically be under the Incubator,

+          and incubation will take place.
+        </p>
+
+
+<strong>
+Someone has proposed that their code/project be donated to project X
+within the ASF for continued development.  What do we need to do to 
+accept the code?
+</strong>
+
+		<p>
+		  The Incubator will only accept code for incubation if a PMC (project
+		  management committee) or the Apache board has voted to accept it.
+		  So when a proposal for the donation of code occurs, the project in
+		  question should discuss the proposal internally, leading to a
+		  decision by that project's PMC on whether or not to accept the code
+		  (and potentially the project surrounding it) into the fold.
+		</p>
+		<p>
+		  If the PMC agrees, then the incubator can be approached, and the
+		  code accepted for incubation.
+      The grant needs to be recorded by following the procedure
+      outlined at the
+      <link href="http://www.apache.org/licenses/">Software Grants</link>
+      section of the ASF Licenses page.
+		</p>
+
+
+<strong>
+How can I update the site?
+</strong>
+
+      <p>Refer to <a href="/how_to_participate.html">How to Participate</a>
+       page. If you are not a committer on the Incubator project, then you can
+       still send patches for the source documents.</p>
+
+
+<strong>
+How do I update the incubation status of a project?
+</strong>
+
+       <p>Look in the incubator SVN module, under site-author/projects/projectname.html
+         (Note: Some projects still use old *.cwiki as the input format - not recommended.)
+       </p>
+       <p>
+         See the <link href="site:guides/website">instructions</link>
+         for updating the website.
+       </p>
+
+<strong>
+Why don't we use an issue tracking system to track incubation process?
+</strong>
+
+       <p>AFAIK, issue trackers do not authenticate that the person entering 
+          the status information has the authority to do so, which is what we
+          get with the Subversion source control process.</p>
+       <p>Note that how the actual day to day tracking is done is not relevant, 
+          and any means, even an issue tracker can be used.</p>
+       <p>Nevertheless, SVN is our only authorative and formal tracking system
+          for incubation status.</p>
+
+
+<strong>
+How do I update the site of an incubating project?
+</strong>
+
+       <p>First of all, read our <link href="site:incubation/policy">Incubation
Policy</link>.</p>
+       <p>Refer to <link href="howtoparticipate.html#project-website">How to
Participate</link> page.</p>
+    
+</section>
+</body>
+</document>

Propchange: incubator/public/trunk/site/xdocs/faq.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/xdocs/general_guide.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/general_guide.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/general_guide.xml (original)
+++ incubator/public/trunk/site/xdocs/general_guide.xml Mon Jan 23 15:58:11 2006
@@ -1,20 +1,20 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="General Guide">
-
-<p>If you don't know how to do something in the Incubator,  look here first, and hopefully
you'll find it. </p>
-<p>If not, please ask on general@incubator.apache.org, and then add it here, so others
after you can find it right away next time. </p>
-
-</section>
-
-</body>
-</document>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="General Guide">
+
+<p>If you don't know how to do something in the Incubator,  look here first, and hopefully
you'll find it. </p>
+<p>If not, please ask on general@incubator.apache.org, and then add it here, so others
after you can find it right away next time. </p>
+
+</section>
+
+</body>
+</document>

Propchange: incubator/public/trunk/site/xdocs/general_guide.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/xdocs/how_to_participate.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/how_to_participate.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/how_to_participate.xml (original)
+++ incubator/public/trunk/site/xdocs/how_to_participate.xml Mon Jan 23 15:58:11 2006
@@ -1,108 +1,108 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="How To Participate">
-
-      
-<subsection name="Check this first">
-         
-<p>Before doing anything, we encourage you to read the incubator website and in particular
-            our "About" documents.</p>
-            
-<p>If you have other questions, feel free to post them on general@incubator.apache.org</p>

-          
-<p>If you want to help in the development of a specific <a href="site:projects">Incubated
Project</a>
-            refer to its development mailing list. The Incubator mailing lists are for project
-            incubation, not for project development.</p>
-            
-<p>In case of generic Project development questions, there is projects@incubator.apache.org</p>
-               
-      
-</subsection>
-
-<subsection name="Incubator Project Resources">
-         
-         
-<div class="fixme">fixme:
-      Check that all Incubator project resources are listed.</div>
-         
-<strong>Mailing lists</strong>
-
-<p>
-As with everything else in Apache, most of what goes on happens or is discussed 
-on electronic mailing lists. 
-You can find information on Incubator mailing lists <a href="mailing.html">here</a>.
-</p>
-
-<strong>Project-specific resources</strong>
-
-<p>
-<a href="/projects.html">Projects</a> under incubation have their 
-own mailing lists, or their development discussion occurs on the 
-mailing list of another project. Check out the project websites to 
-be sure what mailing list is the right one.
-</p>
-         
-<strong>Project Website Howto</strong>
-
-<p>Each project can use whatever documentation system that it
-             chooses. Perhaps use a fancy documentation management
-             system like Forrest or Maven, or just use simple raw html pages.
-</p>
-
-<p>
-             Keep your source documents in your project Version Control System
-             under
-             http://svn.apache.org/repos/asf/incubator/${project}/trunk/
-           </p>
-           <p>
-             To publish
-
-             your site, simply "commit" your final generated documents
-             to your project "site" module at
-             http://svn.apache.org/repos/asf/incubator/${project}/site/
-           </p>
-<p>
-             To update the website, your project "site" SVN module is
-             checked-out on the server.
-             Your project committers can do this step manually,
-             or perhaps automate it with cron.
-           </p>
-<pre class="code">
-ssh people.apache.org
-cd /www/incubator.apache.org/${project-name}
-svn update
-           </pre>
-           <p>
-             Make sure that your subversion client is properly
-             <a href="http://www.apache.org/dev/version-control.html#https-svn">configured</a>.
-             This vastly reduces the amount of traffic on the svn email commits,
-             e.g. *.pdf
-           </p>
-           <p>
-             See other notes for maintenance of
-             <a href="http://www.apache.org/dev/project-site.html">project websites</a>.
-           </p>
-
-<strong>Updating the top-level website</strong>
-<p>How to maintain the top-level <a href="index.html">Incubator website</a>
- (including the project status reports). See the <a href="site:guides/website">website
guide</a>.
-</p>
-<p>
-For actual project websites, see the
-<a href="#project-website">Project Website Howto</a> above.
-However, this section is still relevant for projects.
-</p>
-</subsection>
-</section>
-
- </body>
- </document>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="How To Participate">
+
+      
+<subsection name="Check this first">
+         
+<p>Before doing anything, we encourage you to read the incubator website and in particular
+            our "About" documents.</p>
+            
+<p>If you have other questions, feel free to post them on general@incubator.apache.org</p>

+          
+<p>If you want to help in the development of a specific <a href="site:projects">Incubated
Project</a>
+            refer to its development mailing list. The Incubator mailing lists are for project
+            incubation, not for project development.</p>
+            
+<p>In case of generic Project development questions, there is projects@incubator.apache.org</p>
+               
+      
+</subsection>
+
+<subsection name="Incubator Project Resources">
+         
+         
+<div class="fixme">fixme:
+      Check that all Incubator project resources are listed.</div>
+         
+<strong>Mailing lists</strong>
+
+<p>
+As with everything else in Apache, most of what goes on happens or is discussed 
+on electronic mailing lists. 
+You can find information on Incubator mailing lists <a href="mailing.html">here</a>.
+</p>
+
+<strong>Project-specific resources</strong>
+
+<p>
+<a href="/projects.html">Projects</a> under incubation have their 
+own mailing lists, or their development discussion occurs on the 
+mailing list of another project. Check out the project websites to 
+be sure what mailing list is the right one.
+</p>
+         
+<strong>Project Website Howto</strong>
+
+<p>Each project can use whatever documentation system that it
+             chooses. Perhaps use a fancy documentation management
+             system like Forrest or Maven, or just use simple raw html pages.
+</p>
+
+<p>
+             Keep your source documents in your project Version Control System
+             under
+             http://svn.apache.org/repos/asf/incubator/${project}/trunk/
+           </p>
+           <p>
+             To publish
+
+             your site, simply "commit" your final generated documents
+             to your project "site" module at
+             http://svn.apache.org/repos/asf/incubator/${project}/site/
+           </p>
+<p>
+             To update the website, your project "site" SVN module is
+             checked-out on the server.
+             Your project committers can do this step manually,
+             or perhaps automate it with cron.
+           </p>
+<pre class="code">
+ssh people.apache.org
+cd /www/incubator.apache.org/${project-name}
+svn update
+           </pre>
+           <p>
+             Make sure that your subversion client is properly
+             <a href="http://www.apache.org/dev/version-control.html#https-svn">configured</a>.
+             This vastly reduces the amount of traffic on the svn email commits,
+             e.g. *.pdf
+           </p>
+           <p>
+             See other notes for maintenance of
+             <a href="http://www.apache.org/dev/project-site.html">project websites</a>.
+           </p>
+
+<strong>Updating the top-level website</strong>
+<p>How to maintain the top-level <a href="index.html">Incubator website</a>
+ (including the project status reports). See the <a href="site:guides/website">website
guide</a>.
+</p>
+<p>
+For actual project websites, see the
+<a href="#project-website">Project Website Howto</a> above.
+However, this section is still relevant for projects.
+</p>
+</subsection>
+</section>
+
+ </body>
+ </document>

Propchange: incubator/public/trunk/site/xdocs/how_to_participate.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/xdocs/how_we_work.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/how_we_work.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/how_we_work.xml (original)
+++ incubator/public/trunk/site/xdocs/how_we_work.xml Mon Jan 23 15:58:11 2006
@@ -1,47 +1,47 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="How We Work">
-
-<p>Here are some notes about how we have decided to make decisions 
-and changes to the way we work. 
-</p>
-
-<subsection name="How we make decision on our incubation policies">
-
-<p>
-Apache projects usually make releases, and have deliverables. 
-The code  they put in is managed through lazy consensus and voting
-only when it's  deemed to be required or requested.
-</p>
-
-<p>
-Incubator releases are basically Incubated Projects' release to 
-the  Sponsor PMC. So how incubation is done is our "code".
-</p>
-
-<p>
-Hence there is no need to "ratify" such rules if there seems to be 
-consensus, as it's much easier to manage.
-</p>
-
-<p>
-Because of this, we do not have the "draft" status on our policy 
-docs  and simply use them as our guide, that will change in need 
-without
-</p>
-</subsection>
-</section>
-
- </body>
- </document>
-
-
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="How We Work">
+
+<p>Here are some notes about how we have decided to make decisions 
+and changes to the way we work. 
+</p>
+
+<subsection name="How we make decision on our incubation policies">
+
+<p>
+Apache projects usually make releases, and have deliverables. 
+The code  they put in is managed through lazy consensus and voting
+only when it's  deemed to be required or requested.
+</p>
+
+<p>
+Incubator releases are basically Incubated Projects' release to 
+the  Sponsor PMC. So how incubation is done is our "code".
+</p>
+
+<p>
+Hence there is no need to "ratify" such rules if there seems to be 
+consensus, as it's much easier to manage.
+</p>
+
+<p>
+Because of this, we do not have the "draft" status on our policy 
+docs  and simply use them as our guide, that will change in need 
+without
+</p>
+</subsection>
+</section>
+
+ </body>
+ </document>
+
+

Propchange: incubator/public/trunk/site/xdocs/how_we_work.xml
------------------------------------------------------------------------------
    svn:eol-style = native



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message