incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r157371 [2/2] - incubator/public/trunk/site-author/projects/TEMP_HTML
Date Mon, 14 Mar 2005 03:26:20 GMT
Modified: incubator/public/trunk/site-author/projects/TEMP_HTML/spamassassin.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/TEMP_HTML/spamassassin.html?view=diff&r1=157370&r2=157371
==============================================================================
--- incubator/public/trunk/site-author/projects/TEMP_HTML/spamassassin.html (original)
+++ incubator/public/trunk/site-author/projects/TEMP_HTML/spamassassin.html Sun Mar 13 19:26:16
2005
@@ -94,160 +94,160 @@
 </tr>
 </table>
 <h1>Incubation status reports</h1>
-<h2>2004-04-22&#13;
+<h2>2004-04-22
 </h2>
-<pre class="code">&#13;
-&#13;
-  * is the Incubation Status file up to date? (also post link)&#13;
-&#13;
-Yep --&#13;
-http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/spamassassin.cwiki&#13;
-&#13;
-  * any legal, cross-project or personal issues that still need to be addressed?&#13;
-&#13;
-Copyright and distribution rights still remain to be verified by ASF. The&#13;
-trademark issue on the "SpamAssassin" name is still in progress.&#13;
-&#13;
-  * what has been done for incubation since the last report?&#13;
-&#13;
-news.spamassassin.org has been shut down; it was becoming just a dumping-ground&#13;
-for third-party press releases, and Wiki pages were more appropriate.&#13;
-&#13;
-We're still waiting for trademark assignment to be taken care of.   Also unsure&#13;
-if the ASF have vetted the CLA coverage of the current codebase.  Mostly, the&#13;
-ball is in the ASF's court ;)&#13;
-&#13;
-Have received agreement from current domain holder of "spamassassin.org"&#13;
-that it will be transferred to the ASF.&#13;
-&#13;
- * plans and expectations for the next period?&#13;
-&#13;
-Hopefully we'll get the TM assignment taken care of, and the CLAs vetted;&#13;
-then we'll be ready (at least in terms of ASF procedures) to issue a&#13;
-3.0.0 release of SpamAssassin as an ASF project.&#13;
-&#13;
- * any recommendations for how incubation could run more smoothly for you?&#13;
-&#13;
- * etc (your own thoughts on what is important would be helpful!)&#13;
-&#13;
+<pre class="code">
+
+  * is the Incubation Status file up to date? (also post link)
+
+Yep --
+http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/spamassassin.cwiki
+
+  * any legal, cross-project or personal issues that still need to be addressed?
+
+Copyright and distribution rights still remain to be verified by ASF. The
+trademark issue on the "SpamAssassin" name is still in progress.
+
+  * what has been done for incubation since the last report?
+
+news.spamassassin.org has been shut down; it was becoming just a dumping-ground
+for third-party press releases, and Wiki pages were more appropriate.
+
+We're still waiting for trademark assignment to be taken care of.   Also unsure
+if the ASF have vetted the CLA coverage of the current codebase.  Mostly, the
+ball is in the ASF's court ;)
+
+Have received agreement from current domain holder of "spamassassin.org"
+that it will be transferred to the ASF.
+
+ * plans and expectations for the next period?
+
+Hopefully we'll get the TM assignment taken care of, and the CLAs vetted;
+then we'll be ready (at least in terms of ASF procedures) to issue a
+3.0.0 release of SpamAssassin as an ASF project.
+
+ * any recommendations for how incubation could run more smoothly for you?
+
+ * etc (your own thoughts on what is important would be helpful!)
+
 </pre>
-<h2>2004-03-??&#13;
+<h2>2004-03-??
 </h2>
-<pre class="code">&#13;
-  * STATUS is up to date&#13;
-&#13;
-http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/spamassassin.cwiki&#13;
-is now the canonical STATUS file and it is now up-to-date.  The trunk&#13;
-copy points at it now.&#13;
-&#13;
-  * 3.0.0 tree under development at ASF&#13;
-&#13;
-  * 2.6x not under development at ASF&#13;
-&#13;
+<pre class="code">
+  * STATUS is up to date
+
+http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/spamassassin.cwiki
+is now the canonical STATUS file and it is now up-to-date.  The trunk
+copy points at it now.
+
+  * 3.0.0 tree under development at ASF
+
+  * 2.6x not under development at ASF
+
 </pre>
-<h2>2004-01-21&#13;
+<h2>2004-01-21
 </h2>
-<pre class="code">&#13;
-  * is the STATUS file up to date? (also post link)&#13;
-&#13;
-http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/spamassass&#13;
-in.cwiki&#13;
-&#13;
-Not quite -- the two 'Establish a list of active committers' items are not&#13;
-up to date.  All active committers are now signed up, so that can be&#13;
-closed off.&#13;
-&#13;
-The second item is 'Add all active committers in the STATUS file.'&#13;
-However, I'm now confused.  Which is the canonical STATUS file --&#13;
-/incubator/spamassassin/trunk/STATUS, or&#13;
-/incubator/site/projects/spamassassin.cwiki?  Some signs seem to be&#13;
-pointing to the latter...  so, if the latter, some cut and paste from the&#13;
-former to the latter is then required (and note, I don't think I&#13;
-or anyone else on the SpamAssassin PPMC have write access to it).&#13;
-&#13;
-I'm kind of taking the approach that the latter is the incubation&#13;
-checklist, and the former is tracking our assets and people.  That&#13;
-may be wrong though &#13;
-&#13;
-BTW the former is here:&#13;
-&#13;
-http://svn.apache.org/repos/asf/incubator/spamassassin/trunk/STATUS&#13;
-&#13;
-Also, the two tasks under 'Verify distribution rights', should be&#13;
-complete.  All code in the trunk is covered by CLAs, and the non-covered&#13;
-branches have README files noting their non-Apache status and presence for&#13;
-historical purposes only.   However, perhaps this may need to be verified&#13;
-by the ASF before the task can be marked as complete, I'm not sure.&#13;
-&#13;
-&#13;
-  * any legal, cross-project or personal issues&#13;
-    that still need to be addressed?&#13;
-&#13;
-Copyright and distribution rights still remain to be verified, although&#13;
-all CLAs should now be in.&#13;
- -- so it's up to ASF legal now.&#13;
-&#13;
-The trademark issue on the "SpamAssassin" name is still in progress; as&#13;
-far as I know, NAI legal still need to provide some documentation to DW,&#13;
-Jim Jagielski et al.&#13;
-&#13;
-&#13;
-  * what has been done for incubation since the last report?&#13;
-&#13;
-Lots!&#13;
-&#13;
-- - all committer accounts are set up;&#13;
-&#13;
-- - source code is now running from the Apache Incubator SVN repository;&#13;
-&#13;
-- - all of the developer-oriented mailing lists are now at the Incubator -&#13;
-  although some user-oriented lists are still external, to avoid user&#13;
-  confusion;&#13;
-&#13;
-- - all code has been vetted for CLA coverage, and removed or clean-roomed&#13;
-  if a CLA could not be provided, and this is now awaiting verification by&#13;
-  the ASF;&#13;
-&#13;
-- - and all major code or rules files in SVN are tagged with the ASL 1.1.&#13;
-&#13;
-- - The Wiki has been moved to wiki.apache.org.&#13;
-&#13;
-&#13;
-  * plans and expectations for the next period?&#13;
-&#13;
-We need to transition more infrastructure, including our main website,&#13;
-Wiki and Bugzilla.  Bugzilla uses some custom code to track CLAs, which&#13;
-would be nice to bring over.&#13;
-&#13;
-We also plan to finish up the legal situation, by getting the CLA coverage&#13;
-verified by the ASF, then the trademark.&#13;
-&#13;
-Also we have several cron scripts that are used to perform distributed&#13;
-rule QA, and a very large rsync server contain 2.7Gb of data, which will&#13;
-need to be migrated.   What to do with these is still a topic of&#13;
-discussion, since they're *big* in terms of disk space usage, and&#13;
-there may not be room at the ASF infrastructure for this!&#13;
-&#13;
-There's also a spamtrap server which almost definitely should *not* come&#13;
-along -- it handles approx 1 Gbit of traffic per day (in spam reports)&#13;
-and would be a waste of ASF hardware and bandwidth, IMO.&#13;
-&#13;
-&#13;
-  * any recommendations for how incubation could run&#13;
-    more smoothly for you?&#13;
-&#13;
-A little more introductory doco would be nice; I hadn't heard of&#13;
-http://www.apache.org/dev/ until quite late in the process, and there were&#13;
-a few other issues where I had to hop around the apache.org website to&#13;
-figure out what things meant or what a given procedure was.&#13;
-&#13;
-Also, one thing I'm concerned about is how many aspects of our&#13;
-infrastructure will wind up with "incubator" in their URL or hostname;&#13;
-as a mature project, it'd be much easier to transition with the minimum&#13;
-of changes for the existing community, and this scoping of URLs&#13;
-and hostnames as in incubation means an additional change once we&#13;
-leave the incubator.   As a result, it gives us a bit of an incentive&#13;
-to *not* set things up (lists, etc.) until we leave.&#13;
+<pre class="code">
+  * is the STATUS file up to date? (also post link)
+
+http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/spamassass
+in.cwiki
+
+Not quite -- the two 'Establish a list of active committers' items are not
+up to date.  All active committers are now signed up, so that can be
+closed off.
+
+The second item is 'Add all active committers in the STATUS file.'
+However, I'm now confused.  Which is the canonical STATUS file --
+/incubator/spamassassin/trunk/STATUS, or
+/incubator/site/projects/spamassassin.cwiki?  Some signs seem to be
+pointing to the latter...  so, if the latter, some cut and paste from the
+former to the latter is then required (and note, I don't think I
+or anyone else on the SpamAssassin PPMC have write access to it).
+
+I'm kind of taking the approach that the latter is the incubation
+checklist, and the former is tracking our assets and people.  That
+may be wrong though 
+
+BTW the former is here:
+
+http://svn.apache.org/repos/asf/incubator/spamassassin/trunk/STATUS
+
+Also, the two tasks under 'Verify distribution rights', should be
+complete.  All code in the trunk is covered by CLAs, and the non-covered
+branches have README files noting their non-Apache status and presence for
+historical purposes only.   However, perhaps this may need to be verified
+by the ASF before the task can be marked as complete, I'm not sure.
+
+
+  * any legal, cross-project or personal issues
+    that still need to be addressed?
+
+Copyright and distribution rights still remain to be verified, although
+all CLAs should now be in.
+ -- so it's up to ASF legal now.
+
+The trademark issue on the "SpamAssassin" name is still in progress; as
+far as I know, NAI legal still need to provide some documentation to DW,
+Jim Jagielski et al.
+
+
+  * what has been done for incubation since the last report?
+
+Lots!
+
+- - all committer accounts are set up;
+
+- - source code is now running from the Apache Incubator SVN repository;
+
+- - all of the developer-oriented mailing lists are now at the Incubator -
+  although some user-oriented lists are still external, to avoid user
+  confusion;
+
+- - all code has been vetted for CLA coverage, and removed or clean-roomed
+  if a CLA could not be provided, and this is now awaiting verification by
+  the ASF;
+
+- - and all major code or rules files in SVN are tagged with the ASL 1.1.
+
+- - The Wiki has been moved to wiki.apache.org.
+
+
+  * plans and expectations for the next period?
+
+We need to transition more infrastructure, including our main website,
+Wiki and Bugzilla.  Bugzilla uses some custom code to track CLAs, which
+would be nice to bring over.
+
+We also plan to finish up the legal situation, by getting the CLA coverage
+verified by the ASF, then the trademark.
+
+Also we have several cron scripts that are used to perform distributed
+rule QA, and a very large rsync server contain 2.7Gb of data, which will
+need to be migrated.   What to do with these is still a topic of
+discussion, since they're *big* in terms of disk space usage, and
+there may not be room at the ASF infrastructure for this!
+
+There's also a spamtrap server which almost definitely should *not* come
+along -- it handles approx 1 Gbit of traffic per day (in spam reports)
+and would be a waste of ASF hardware and bandwidth, IMO.
+
+
+  * any recommendations for how incubation could run
+    more smoothly for you?
+
+A little more introductory doco would be nice; I hadn't heard of
+http://www.apache.org/dev/ until quite late in the process, and there were
+a few other issues where I had to hop around the apache.org website to
+figure out what things meant or what a given procedure was.
+
+Also, one thing I'm concerned about is how many aspects of our
+infrastructure will wind up with "incubator" in their URL or hostname;
+as a mature project, it'd be much easier to transition with the minimum
+of changes for the existing community, and this scoping of URLs
+and hostnames as in incubation means an additional change once we
+leave the incubator.   As a result, it gives us a bit of an incentive
+to *not* set things up (lists, etc.) until we leave.
 </pre>
 <h1>Incubation work items</h1>
 <h2>Project Setup</h2>
@@ -255,7 +255,7 @@
 <p>
 <em>Item assignment is shown by the Apache id.</em> <em>Completed tasks
are shown by the completion date (YYYY-MM-dd). </em> 
 </p>
-<h3>Identify the project to be incubated&#13;
+<h3>Identify the project to be incubated
 </h3>
 <table>
 <tr>
@@ -271,8 +271,8 @@
 <p>
 <em>NOTE</em> 
 </p>
-<pre class="code">&#13;
-There is a trademark&#13;
+<pre class="code">
+There is a trademark
 </pre>
 <h3>Interim responsibility</h3>
 <table>
@@ -352,16 +352,16 @@
 <p>
 <em>NOTES</em> 
 </p>
-<pre class="code">&#13;
-Discussion is underway to whether SA wants to use Jira, or wants to&#13;
-import their BZ database into the existing ASF installation.&#13;
+<pre class="code">
+Discussion is underway to whether SA wants to use Jira, or wants to
+import their BZ database into the existing ASF installation.
 </pre>
-<pre class="code">&#13;
-The moving to the ASF infrastructure is partly delayed by the limited resources&#13;
-available in the ASF Infrastructure team (time).  Also, this mature project&#13;
-has quite a lot of infrastructure to move.  I suggest we don't let this be&#13;
-one of the points to keep SA in the Incubator; the intent to move to the&#13;
-ASF infrastructure is there.&#13;
+<pre class="code">
+The moving to the ASF infrastructure is partly delayed by the limited resources
+available in the ASF Infrastructure team (time).  Also, this mature project
+has quite a lot of infrastructure to move.  I suggest we don't let this be
+one of the points to keep SA in the Incubator; the intent to move to the
+ASF infrastructure is there.
 </pre>
 <h3>Project specific </h3>
 <p>

Modified: incubator/public/trunk/site-author/projects/TEMP_HTML/wsrp4j.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/TEMP_HTML/wsrp4j.html?view=diff&r1=157370&r2=157371
==============================================================================
--- incubator/public/trunk/site-author/projects/TEMP_HTML/wsrp4j.html (original)
+++ incubator/public/trunk/site-author/projects/TEMP_HTML/wsrp4j.html Sun Mar 13 19:26:16
2005
@@ -75,126 +75,126 @@
 <td>Extra              </td><td>.                       </td><td>.
</td>
 </tr>
 </table>
-<h1>Incubation status reports&#13;
+<h1>Incubation status reports
 </h1>
-<h2>2004-07-19&#13;
+<h2>2004-07-19
 </h2>
-<pre class="code">&#13;
-Status Report for the Incubator&#13;
-&#13;
-* is the STATUS file up to date? (also post link)&#13;
-&#13;
-  The cwiki file on the incubator site is  up to date as well as the STATUS file in the project
directory.&#13;
-  http://incubator.apache.org/projects/wsrp4j.html&#13;
-&#13;
-* any legal, cross-project or personal issues&#13;
- that still need to be addressed?&#13;
- &#13;
-  No.&#13;
-&#13;
-* what has been done for incubation since the last report?&#13;
-&#13;
-  1.  Annointed a new committer: sgoldstein &#13;
-  2.  Various bug fixes.&#13;
-  3.  Restructured the website and added the Portals logo.&#13;
-  4.  Migrated to the new moinmoin wiki.&#13;
-&#13;
-* plans and expectations for the next period?&#13;
-&#13;
-  1. Continue development work on outstanding WSRP 1.0 items &#13;
-     (see TODO wiki: http://wiki.apache.org/wiki/apachewiki.cgi?WsrpToDoList)&#13;
-  2. Continue to build the community by encouraging developers &#13;
-     to contribute code.  We are building a user population, but few &#13;
-     outside developers have made code contributions.&#13;
-  3. Will probably ask for a vote to graduate from the Incubator into Portals.&#13;
-&#13;
-* any recommendations for how incubation could run more smoothly for you?&#13;
-&#13;
-  None.&#13;
-&#13;
-* etc (your own thoughts on what is important would be helpful!) &#13;
+<pre class="code">
+Status Report for the Incubator
+
+* is the STATUS file up to date? (also post link)
+
+  The cwiki file on the incubator site is  up to date as well as the STATUS file in the project
directory.
+  http://incubator.apache.org/projects/wsrp4j.html
+
+* any legal, cross-project or personal issues
+ that still need to be addressed?
+ 
+  No.
+
+* what has been done for incubation since the last report?
+
+  1.  Annointed a new committer: sgoldstein 
+  2.  Various bug fixes.
+  3.  Restructured the website and added the Portals logo.
+  4.  Migrated to the new moinmoin wiki.
+
+* plans and expectations for the next period?
+
+  1. Continue development work on outstanding WSRP 1.0 items 
+     (see TODO wiki: http://wiki.apache.org/wiki/apachewiki.cgi?WsrpToDoList)
+  2. Continue to build the community by encouraging developers 
+     to contribute code.  We are building a user population, but few 
+     outside developers have made code contributions.
+  3. Will probably ask for a vote to graduate from the Incubator into Portals.
+
+* any recommendations for how incubation could run more smoothly for you?
+
+  None.
+
+* etc (your own thoughts on what is important would be helpful!) 
 </pre>
-<h2>2004-06-14&#13;
+<h2>2004-06-14
 </h2>
-<pre class="code">&#13;
-Status Report for the Incubator&#13;
-&#13;
-* is the STATUS file up to date? (also post link)&#13;
-&#13;
-  The cwiki file on the incubator site is  up to date. &#13;
-  http://incubator.apache.org/projects/wsrp4j.html&#13;
-&#13;
-* any legal, cross-project or personal issues&#13;
- that still need to be addressed?&#13;
-&#13;
-  It is expected that the WSRP4J project will graduate to the portals TLP.&#13;
-  &#13;
-* what has been done for incubation since the last report?&#13;
-&#13;
-  1.  Moved from Bugzilla to JIRA&#13;
-  2.  Various bug fixes.&#13;
-&#13;
-* plans and expectations for the next period?&#13;
-&#13;
-  1. Continue development work on outstanding WSRP 1.0 items &#13;
-     (see TODO wiki: http://nagoya.apache.org/wiki/apachewiki.cgi?WsrpToDoList)&#13;
-  2. Continue to build the community by encouraging developers &#13;
-     to contribute code.  We are building a user population, but few &#13;
-     outside developers have made code contributions.&#13;
-&#13;
-* any recommendations for how incubation could run more smoothly for you?&#13;
-&#13;
-  None.&#13;
-&#13;
-* etc (your own thoughts on what is important would be helpful!) &#13;
+<pre class="code">
+Status Report for the Incubator
+
+* is the STATUS file up to date? (also post link)
+
+  The cwiki file on the incubator site is  up to date. 
+  http://incubator.apache.org/projects/wsrp4j.html
+
+* any legal, cross-project or personal issues
+ that still need to be addressed?
+
+  It is expected that the WSRP4J project will graduate to the portals TLP.
+  
+* what has been done for incubation since the last report?
+
+  1.  Moved from Bugzilla to JIRA
+  2.  Various bug fixes.
+
+* plans and expectations for the next period?
+
+  1. Continue development work on outstanding WSRP 1.0 items 
+     (see TODO wiki: http://nagoya.apache.org/wiki/apachewiki.cgi?WsrpToDoList)
+  2. Continue to build the community by encouraging developers 
+     to contribute code.  We are building a user population, but few 
+     outside developers have made code contributions.
+
+* any recommendations for how incubation could run more smoothly for you?
+
+  None.
+
+* etc (your own thoughts on what is important would be helpful!) 
 </pre>
-<h2>2004-01-19&#13;
+<h2>2004-01-19
 </h2>
-<pre class="code">&#13;
-Status report for the Incubator&#13;
-&#13;
-* is the STATUS file up to date? (also post link)&#13;
-&#13;
-  The cwiki file on the incubator site is more or less up to date. &#13;
-  http://incubator.apache.org/projects/wsrp4j.html&#13;
-&#13;
-* any legal, cross-project or personal issues&#13;
- that still need to be addressed?&#13;
-&#13;
-  There is a effort under way to create a portals super project &#13;
-  that would have the WSRP4J project as a sub project.  This is a &#13;
-  desireable thing for the WSRP4J project since it would give us &#13;
-  focus as a portal-related technology.&#13;
-  &#13;
-* what has been done for incubation since the last report?&#13;
-&#13;
-  This is the first report.  However, since we started we have:&#13;
-  1.  Imported all the code into CVS.&#13;
-  2.  Granted committer rights to initial committers.&#13;
-  3.  Established mailing lists.&#13;
-  4.  Created Bugzilla components, although no bugs have been &#13;
-      reported yet using Bugzilla.&#13;
-  5.  Created a website using Forrest.&#13;
-  6.  Create a TODO wiki to encourage collaboration on features &#13;
-      and enhancements.&#13;
-  7.  Joined the Gump nightly build process.&#13;
-  8.  Voted to join portals.apache.org&#13;
-  9.  Voted to substitute JIRA for Bugzilla&#13;
-&#13;
-* plans and expectations for the next period?&#13;
-&#13;
-  1. Continue development work on outstanding WSRP 1.0 items &#13;
-     (see TODO wiki: http://nagoya.apache.org/wiki/apachewiki.cgi?WsrpToDoList)&#13;
-  2. Continue to build the community by encouraging developers &#13;
-     to contribute code.  We are building a user population, but few &#13;
-     outside developers have made code contributions.&#13;
-&#13;
-* any recommendations for how incubation could run more smoothly for you?&#13;
-&#13;
-  I'm confused on the difference between a STATUS file and the cwiki &#13;
-  page on the Incubator website.  Do I need both?&#13;
-&#13;
-* etc (your own thoughts on what is important would be helpful!) &#13;
+<pre class="code">
+Status report for the Incubator
+
+* is the STATUS file up to date? (also post link)
+
+  The cwiki file on the incubator site is more or less up to date. 
+  http://incubator.apache.org/projects/wsrp4j.html
+
+* any legal, cross-project or personal issues
+ that still need to be addressed?
+
+  There is a effort under way to create a portals super project 
+  that would have the WSRP4J project as a sub project.  This is a 
+  desireable thing for the WSRP4J project since it would give us 
+  focus as a portal-related technology.
+  
+* what has been done for incubation since the last report?
+
+  This is the first report.  However, since we started we have:
+  1.  Imported all the code into CVS.
+  2.  Granted committer rights to initial committers.
+  3.  Established mailing lists.
+  4.  Created Bugzilla components, although no bugs have been 
+      reported yet using Bugzilla.
+  5.  Created a website using Forrest.
+  6.  Create a TODO wiki to encourage collaboration on features 
+      and enhancements.
+  7.  Joined the Gump nightly build process.
+  8.  Voted to join portals.apache.org
+  9.  Voted to substitute JIRA for Bugzilla
+
+* plans and expectations for the next period?
+
+  1. Continue development work on outstanding WSRP 1.0 items 
+     (see TODO wiki: http://nagoya.apache.org/wiki/apachewiki.cgi?WsrpToDoList)
+  2. Continue to build the community by encouraging developers 
+     to contribute code.  We are building a user population, but few 
+     outside developers have made code contributions.
+
+* any recommendations for how incubation could run more smoothly for you?
+
+  I'm confused on the difference between a STATUS file and the cwiki 
+  page on the Incubator website.  Do I need both?
+
+* etc (your own thoughts on what is important would be helpful!) 
 </pre>
 <h1>Incubation work items</h1>
 <h2>Project Setup</h2>
@@ -202,7 +202,7 @@
 <p>
 <em>Item assignment is shown by the Apache id.</em> <em>Completed tasks
are shown by the completion date (YYYY-MM-dd). </em> 
 </p>
-<h3>Identify the project to be incubated&#13;
+<h3>Identify the project to be incubated
 </h3>
 <table>
 <tr>

Modified: incubator/public/trunk/site-author/projects/TEMP_HTML/xmlbeans.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/TEMP_HTML/xmlbeans.html?view=diff&r1=157370&r2=157371
==============================================================================
--- incubator/public/trunk/site-author/projects/TEMP_HTML/xmlbeans.html (original)
+++ incubator/public/trunk/site-author/projects/TEMP_HTML/xmlbeans.html Sun Mar 13 19:26:16
2005
@@ -103,183 +103,183 @@
 <h2>Incubator sign-off:</h2>
 <p>X- Has the Incubator decided that the project has accomplished all of the above
tasks? </p>
 <h1>Incubation Status Reports</h1>
-<h2>2004-04-20&#13;
+<h2>2004-04-20
 </h2>
-<pre class="code">&#13;
-- Status report for the Incubator -&#13;
-&#13;
-Changes since last report in January:&#13;
-* Added Dutta Satadip as a committer &#13;
-* Released incubating-xmlbeans-1.0.2 after a thorough legal review&#13;
-** after review of license issues: added jaxen to distribution, removed junit, noted W3C
XML Schemas&#13;
-** applied Apache License 2.0&#13;
-* Formed a PPMC; set up mailing list and designed guidelines&#13;
-* Moved from bugzilla to JIRA.&#13;
-* Set up new wiki pages.&#13;
-&#13;
-Expectations for next three months:&#13;
-* Find two more committers&#13;
-* Release one more distribution&#13;
-* Improve web site (faq, current info, etc)&#13;
-* Exit incubator&#13;
+<pre class="code">
+- Status report for the Incubator -
+
+Changes since last report in January:
+* Added Dutta Satadip as a committer 
+* Released incubating-xmlbeans-1.0.2 after a thorough legal review
+** after review of license issues: added jaxen to distribution, removed junit, noted W3C
XML Schemas
+** applied Apache License 2.0
+* Formed a PPMC; set up mailing list and designed guidelines
+* Moved from bugzilla to JIRA.
+* Set up new wiki pages.
+
+Expectations for next three months:
+* Find two more committers
+* Release one more distribution
+* Improve web site (faq, current info, etc)
+* Exit incubator
 </pre>
-<h2>2004-01-17 &#13;
+<h2>2004-01-17 
 </h2>
-<pre class="code">&#13;
-&#13;
-- Status report for the Incubator -&#13;
-&#13;
-Overall the xmlbeans project is progressing with good committer&#13;
-productivity and a growing user community.  Converting over the Apache&#13;
-CVS systems and build process has been accomplished along with various&#13;
-other Apache administrative tasks such as setting up the Apache website.&#13;
-&#13;
-There is some movement towards growth in the development side of the&#13;
-community with one contributor (Dutta Satadip) submitting a nice&#13;
-enhancement and several other contributors submitting small patches&#13;
-related to bugs.&#13;
-&#13;
-More on each of the bullet points below.&#13;
-&#13;
-* is the STATUS file up to date? (also post link)&#13;
-&#13;
-&lt;Cliff Schmidt&gt;&#13;
-We need to update the status file with the latest incubator guidelines.&#13;
-We're mostly there, but there are a couple things that need to be added.&#13;
-I also think the status file needs to be updated in one or two other ways.&#13;
-For instance, the tasks completed should now include:&#13;
-- build xmlbeans website &#13;
-- grant some committers access to xml-site (Cliff and Remy)&#13;
-&lt;/Cliff Schmidt&gt;&#13;
-&#13;
-http://incubator.apache.org/projects/xmlbeans.html&#13;
-&#13;
-* any legal, cross-project or personal issues&#13;
-  that still need to be addressed?&#13;
-&#13;
-In general it appears xmlbeans is through most of the known issues &#13;
-that existed getting started.  The committers have been able to be &#13;
-productive and there is a lot of code being created in version 2 &#13;
-and fixes are being made into version 1.&#13;
-&#13;
-One issue that we have run into is how best to accommodate commonly &#13;
-used api jars primarily (but not exclusively) JCP related api's from &#13;
-SUN.  We are not sure the appropriate process to determine whether &#13;
-we can use a particular jar and host the jar in the xmlbeans build.  &#13;
-examples of api's that we are unsure the appropriate/best way to deal &#13;
-with are:&#13;
-&#13;
-  * JSR173 api and JSR 173 RI (Streaming API for XML, a.k.a., STAX) - &#13;
-    the JSR173 RI dependency is temporary.  Currently xmlbeans downloads &#13;
-    it from external server during the build process&#13;
-  * SAAJ api - we used the saaj-api source code in axis.  &#13;
-  * xml commons resolver (Apache jakarta)&#13;
-  * jaxen  (jaxen.sourceforge.net - apache-style license, but not apache)&#13;
-&#13;
-Here are some specific questions on this subject that David Bau posted:&#13;
-&#13;
-&lt;David Bau&gt;&#13;
-- We currently load resolver.jar and jaxen.jar if the user happens to put&#13;
-them on the classpath, and throw a runtime exception if the user tries to&#13;
-use a resolver- or jaxen- dependent feature without those JARs present.&#13;
-This is OK, but it would be nicer for users if resolver and jaxen were just&#13;
-included in xbean.jar, but this presents both licensing issues (for jaxen)&#13;
-and possible-version-conflict issues (for commons resolver).  A question is:&#13;
-is there a nice way we include resolver.jar and jaxen.jar inside xbean.jar,&#13;
-or should we stay away from that idea?&#13;
-&#13;
-- We need the JSR 173 API to run, and this is definitely something that we&#13;
-want to be able to distribute either directly inside xbean.jar, or at least&#13;
-directly inside Apache since it's so core.  In other words, we can't expect&#13;
-users to do anything without this API present.  I've noticed that for other&#13;
-APIs, such as SAAJ, Apache seems to have a "clean room" copy of the APIs.&#13;
-Should we be making such a copy of the JSR 173 APIs?  What is the right way&#13;
-to do this?&#13;
-&lt;/David Bau&gt;&#13;
-&#13;
-* what has been done for incubation since the last report?&#13;
-&#13;
-&lt;David Bau&gt;&#13;
-The main thing is that we've been working on the project.  We're getting&#13;
-more folks hanging around on the lists; we're getting some of the code that&#13;
-we've talked about on the lists and on the wiki actually written and checked&#13;
-in.  We've been encouraging the wider community to critique and contribute&#13;
-ideas and code. Community-building is a gradual process; we don't have a&#13;
-mature community yet, but we've certainly gotten started at building a little&#13;
-one.&#13;
-&lt;/David Bau&gt;&#13;
-&#13;
- *  source code checkin (was that since last status report?)&#13;
- *  build and test ant scripts established&#13;
- *  website updated including docs, source code access, etc.&#13;
- *  established version 2 effort and modified CVS tree accordingly&#13;
- *  proposed (close to implementing I think) branching strategy for &#13;
-    version 1 (by Kevin Krouse)&#13;
- *  gump integration (thanks to Robert Burrell Donkin)&#13;
-&#13;
-&#13;
-* plans and expectations for the next period?&#13;
-&#13;
- * development on v2 will continue incorporating community feedback.&#13;
- * continued work on soliciting volunteers for contribution and committership.&#13;
- * work on organizing bug tracking and follow up&#13;
- * xmlbeans-1.01 distribution (minor bug fixes to v1) &#13;
- * improve process of bug testing and fixing from BugZilla contributions.&#13;
-&#13;
-* any recommendations for how incubation could run&#13;
-   more smoothly for you?&#13;
-&#13;
-Incubation seems to be going well with one, albeit an important one,&#13;
-challenge of getting outside committers.  Having a large existing&#13;
-codebase in a fairly complicated area makes it challenging.  The growing&#13;
-user community and the excellent posts that we are getting on the&#13;
-xmbleans-dev list make us optimistic we will make some breakthroughs&#13;
-in the next period.&#13;
-&#13;
-* things that xmlbeans could/will improve on (summary, contributed by Cliff Schmidt)&#13;
-&#13;
-1. Bug management: http://nagoya.apache.org/bugzilla/buglist.cgi?product=XMLBeans&#13;
-(as has already been mentioned by one or two others) &#13;
--- This is just as much related to community as code.  Of the 12 bugs&#13;
-entered so far, we haven't done a very good job of keeping them updated&#13;
-with status.  We should encourage people to file bugs by showing that&#13;
-the committers are actually responding to them (even if the response&#13;
-is "need more info to repro" or simply noting the priority).&#13;
-&#13;
-2. Web site: http://xml.apache.org/xmlbeans/&#13;
--- We got this built and running but we need to keep it updated.  For &#13;
-instance, it still shows the ApacheCon advertisement.  &#13;
-&#13;
-3. Binary download.  &#13;
--- We started to get this done, but I don't think we ever finished.  &#13;
-Actually, I'd like to try to get this done in the next couple days.&#13;
-&#13;
-4. PPMC&#13;
--- The incubator introduced the idea of a PPMC and we haven't responded&#13;
-to this yet.  I'll follow up in a separate post on what needs to be done.&#13;
-&#13;
-5. Status file&#13;
--- We need to update the status file with the latest incubator guidelines.&#13;
-We're mostly there, but there are a couple things that need to be added.&#13;
-I also think the status file needs to be updated in one or two other ways.&#13;
-For instance, the tasks completed should now include:&#13;
-- build xmlbeans website &#13;
-- grant some committers access to xml-site (although I forgot who has this;&#13;
-I think it is me and Remy)&#13;
-&#13;
-6. Committer keys &#13;
-Bau and I were both able to make it to ApacheCon and we both participated in&#13;
-the key-signing party.  We need to get other committers to make keys and &#13;
-get them signed by me and Bau whenever we run into each other in person &#13;
-again.&#13;
-&#13;
-7. New Committers&#13;
-The biggest issue of all is definitely the new committers, as everyone&#13;
-seems to agree.  We really need to find more ways to encourage others to&#13;
-contribute.   I think we are all ready and willing to share some of the&#13;
-responsibility; we just need to find people who are showing enough interest&#13;
-(and action) to be considered for committership.&#13;
-&#13;
+<pre class="code">
+
+- Status report for the Incubator -
+
+Overall the xmlbeans project is progressing with good committer
+productivity and a growing user community.  Converting over the Apache
+CVS systems and build process has been accomplished along with various
+other Apache administrative tasks such as setting up the Apache website.
+
+There is some movement towards growth in the development side of the
+community with one contributor (Dutta Satadip) submitting a nice
+enhancement and several other contributors submitting small patches
+related to bugs.
+
+More on each of the bullet points below.
+
+* is the STATUS file up to date? (also post link)
+
+&lt;Cliff Schmidt&gt;
+We need to update the status file with the latest incubator guidelines.
+We're mostly there, but there are a couple things that need to be added.
+I also think the status file needs to be updated in one or two other ways.
+For instance, the tasks completed should now include:
+- build xmlbeans website 
+- grant some committers access to xml-site (Cliff and Remy)
+&lt;/Cliff Schmidt&gt;
+
+http://incubator.apache.org/projects/xmlbeans.html
+
+* any legal, cross-project or personal issues
+  that still need to be addressed?
+
+In general it appears xmlbeans is through most of the known issues 
+that existed getting started.  The committers have been able to be 
+productive and there is a lot of code being created in version 2 
+and fixes are being made into version 1.
+
+One issue that we have run into is how best to accommodate commonly 
+used api jars primarily (but not exclusively) JCP related api's from 
+SUN.  We are not sure the appropriate process to determine whether 
+we can use a particular jar and host the jar in the xmlbeans build.  
+examples of api's that we are unsure the appropriate/best way to deal 
+with are:
+
+  * JSR173 api and JSR 173 RI (Streaming API for XML, a.k.a., STAX) - 
+    the JSR173 RI dependency is temporary.  Currently xmlbeans downloads 
+    it from external server during the build process
+  * SAAJ api - we used the saaj-api source code in axis.  
+  * xml commons resolver (Apache jakarta)
+  * jaxen  (jaxen.sourceforge.net - apache-style license, but not apache)
+
+Here are some specific questions on this subject that David Bau posted:
+
+&lt;David Bau&gt;
+- We currently load resolver.jar and jaxen.jar if the user happens to put
+them on the classpath, and throw a runtime exception if the user tries to
+use a resolver- or jaxen- dependent feature without those JARs present.
+This is OK, but it would be nicer for users if resolver and jaxen were just
+included in xbean.jar, but this presents both licensing issues (for jaxen)
+and possible-version-conflict issues (for commons resolver).  A question is:
+is there a nice way we include resolver.jar and jaxen.jar inside xbean.jar,
+or should we stay away from that idea?
+
+- We need the JSR 173 API to run, and this is definitely something that we
+want to be able to distribute either directly inside xbean.jar, or at least
+directly inside Apache since it's so core.  In other words, we can't expect
+users to do anything without this API present.  I've noticed that for other
+APIs, such as SAAJ, Apache seems to have a "clean room" copy of the APIs.
+Should we be making such a copy of the JSR 173 APIs?  What is the right way
+to do this?
+&lt;/David Bau&gt;
+
+* what has been done for incubation since the last report?
+
+&lt;David Bau&gt;
+The main thing is that we've been working on the project.  We're getting
+more folks hanging around on the lists; we're getting some of the code that
+we've talked about on the lists and on the wiki actually written and checked
+in.  We've been encouraging the wider community to critique and contribute
+ideas and code. Community-building is a gradual process; we don't have a
+mature community yet, but we've certainly gotten started at building a little
+one.
+&lt;/David Bau&gt;
+
+ *  source code checkin (was that since last status report?)
+ *  build and test ant scripts established
+ *  website updated including docs, source code access, etc.
+ *  established version 2 effort and modified CVS tree accordingly
+ *  proposed (close to implementing I think) branching strategy for 
+    version 1 (by Kevin Krouse)
+ *  gump integration (thanks to Robert Burrell Donkin)
+
+
+* plans and expectations for the next period?
+
+ * development on v2 will continue incorporating community feedback.
+ * continued work on soliciting volunteers for contribution and committership.
+ * work on organizing bug tracking and follow up
+ * xmlbeans-1.01 distribution (minor bug fixes to v1) 
+ * improve process of bug testing and fixing from BugZilla contributions.
+
+* any recommendations for how incubation could run
+   more smoothly for you?
+
+Incubation seems to be going well with one, albeit an important one,
+challenge of getting outside committers.  Having a large existing
+codebase in a fairly complicated area makes it challenging.  The growing
+user community and the excellent posts that we are getting on the
+xmbleans-dev list make us optimistic we will make some breakthroughs
+in the next period.
+
+* things that xmlbeans could/will improve on (summary, contributed by Cliff Schmidt)
+
+1. Bug management: http://nagoya.apache.org/bugzilla/buglist.cgi?product=XMLBeans
+(as has already been mentioned by one or two others) 
+-- This is just as much related to community as code.  Of the 12 bugs
+entered so far, we haven't done a very good job of keeping them updated
+with status.  We should encourage people to file bugs by showing that
+the committers are actually responding to them (even if the response
+is "need more info to repro" or simply noting the priority).
+
+2. Web site: http://xml.apache.org/xmlbeans/
+-- We got this built and running but we need to keep it updated.  For 
+instance, it still shows the ApacheCon advertisement.  
+
+3. Binary download.  
+-- We started to get this done, but I don't think we ever finished.  
+Actually, I'd like to try to get this done in the next couple days.
+
+4. PPMC
+-- The incubator introduced the idea of a PPMC and we haven't responded
+to this yet.  I'll follow up in a separate post on what needs to be done.
+
+5. Status file
+-- We need to update the status file with the latest incubator guidelines.
+We're mostly there, but there are a couple things that need to be added.
+I also think the status file needs to be updated in one or two other ways.
+For instance, the tasks completed should now include:
+- build xmlbeans website 
+- grant some committers access to xml-site (although I forgot who has this;
+I think it is me and Remy)
+
+6. Committer keys 
+Bau and I were both able to make it to ApacheCon and we both participated in
+the key-signing party.  We need to get other committers to make keys and 
+get them signed by me and Bau whenever we run into each other in person 
+again.
+
+7. New Committers
+The biggest issue of all is definitely the new committers, as everyone
+seems to agree.  We really need to find more ways to encourage others to
+contribute.   I think we are all ready and willing to share some of the
+responsibility; we just need to find people who are showing enough interest
+(and action) to be considered for committership.
+
 </pre>
 </body>
 </html>



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


Mime
View raw message