db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mcai...@apache.org
Subject svn commit: r279676 - in /incubator/jdo/site: docs/get-involved.html docs/svn.html docs/team-list.html xdocs/get-involved.xml xdocs/svn.xml xdocs/team-list.xml
Date Thu, 08 Sep 2005 23:42:32 GMT
Author: mcaisse
Date: Thu Sep  8 16:42:29 2005
New Revision: 279676

URL: http://svn.apache.org/viewcvs?rev=279676&view=rev
Log:
updates to web site

Modified:
    incubator/jdo/site/docs/get-involved.html
    incubator/jdo/site/docs/svn.html
    incubator/jdo/site/docs/team-list.html
    incubator/jdo/site/xdocs/get-involved.xml
    incubator/jdo/site/xdocs/svn.xml
    incubator/jdo/site/xdocs/team-list.xml

Modified: incubator/jdo/site/docs/get-involved.html
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/docs/get-involved.html?rev=279676&r1=279675&r2=279676&view=diff
==============================================================================
--- incubator/jdo/site/docs/get-involved.html (original)
+++ incubator/jdo/site/docs/get-involved.html Thu Sep  8 16:42:29 2005
@@ -141,6 +141,38 @@
       Additional documentation and discussion can be found on the project
      <a href="http://wiki.apache.org/jdo/">wiki</a>
    </li>
+    <li>
+    We have a communications conference call every Friday at 9:00 AM Pacific time. The conference call number is 866 230-6968 (international 865 544-7856) code 294-0479#. During this call we discuss project status, issues, concerns, and strategy. Everyone interested in Apache JDO is welcome and encouraged to participate. 
+   </li>
+</ul>
+                            </blockquote>
+        </p>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#525D76">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="How do I become a committer?"><strong>How do I become a committer?</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>If you're interested in committing to the project: </p>
+                                                <ul>
+<li><p> You'll need to fill out some legal paperwork and go through a process to get an apache committer account: See <a class="external" rel="nofollow" href="http://apache.org/dev/new-committers-guide.html">New Committers Guide</a>, <a class="external" rel="nofollow" href="http://apache.org/dev/contributors.html">Contributors</a>, and <a class="external" rel="nofollow" href="http://apache.org/dev/committers.html">Committers</a> for more details. </p>
+
+</li>
+<li><p> After you've received an email from <a href="mailto:root@apache.org">root@apache.org</a> with your committer account information, change your initial password: Login by 'ssh -l &lt;username&gt; cvs.apache.org' (soon 'people.apache.org', as by apache email announcement); run 'passwd'; run 'svnpasswd'. See <a class="external" rel="nofollow" href="http://apache.org/dev/version-control.html">Committer Subversion Access</a>. </p>
+</li>
+<li><p> Check out the JDO sources and test your svn account: <a href="http://svn.apache.org/viewcvs.cgi/incubator/jdo/">SubversionRepository</a>. </p>
+
+</li>
+<li><p> Sign up for a <a class="external" rel="nofollow" href="http://wiki.apache.org/jdo/UserPreferences">WiKi</a> account. </p>
+</li>
+<li><p> Sign up for an <a class="external" rel="nofollow" href="http://issues.apache.org/jira/">ASF JIRA</a> account. </p>
+</li>
+
 </ul>
                             </blockquote>
         </p>

Modified: incubator/jdo/site/docs/svn.html
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/docs/svn.html?rev=279676&r1=279675&r2=279676&view=diff
==============================================================================
--- incubator/jdo/site/docs/svn.html (original)
+++ incubator/jdo/site/docs/svn.html Thu Sep  8 16:42:29 2005
@@ -119,13 +119,14 @@
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>Apache JDO uses <a class="external" rel="nofollow" href="http://subversion.tigris.org">Subversion</a> to manage its source code. Instructions on Subversion use can be found <a class="external" rel="nofollow" href="http://svnbook.red-bean.com">here</a>. To receive notice of commits to the repository subscribe to <a href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
-                                                <p>
+                                    <p>Apache JDO uses <a class="external" rel="nofollow" href="http://subversion.tigris.org">Subversion</a> to manage its source code.
 If you're new to Subversion, you can check out the
 <a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
 Note that we are currently using Subversion 1.1.x (there are separate
 versions of the book covering 1.0 and 1.1).
 </p>
+                                                <p>
+To receive notice of commits to the repository subscribe to <a href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
                             </blockquote>
         </p>
       </td></tr>
@@ -141,8 +142,8 @@
         <blockquote>
                                     <p>
 If you just want to browse the source code, you can use the
-<a href="http://svn.apache.org/viewcvs.cgi/jdo/trunk/?root=Apache-SVN">ViewCVS
-web interface</a> to Subversion.  This is current at all times.
+<a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/jdo">
+ViewCVS web interface</a> to Subversion.  This is current at all times.
 </p>
                             </blockquote>
         </p>
@@ -152,74 +153,100 @@
                                                 <table border="0" cellspacing="0" cellpadding="2" width="100%">
       <tr><td bgcolor="#525D76">
         <font color="#ffffff" face="arial,helvetica,sanserif">
-          <a name="Normal Subversion Access"><strong>Normal Subversion Access</strong></a>
+          <a name="Checking Out Code Using Subversion"><strong>Checking Out Code Using Subversion</strong></a>
         </font>
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>Anyone can check code out of Subversion.  You need to specify a
-username and password in order to update the Subversion repository, and only
-JDO committers have the permissions to do that.  We run Subversion
-over standard HTTPS. You might need to set up your local subversion
-network configuration for local proxies. Hopefully you won't have 
-problems with intervening firewalls.</p>
-                                                <strong>Check out from Subversion</strong>
-                                                <p>Use a command like:</p>
+                                    <p>Anyone can check code out of Subversion.  You only need to specify a
+username and password to update the Subversion repository, and only
+JDO committers can do that.
+If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.</p>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Anonymous check out from Subversion"><strong>Anonymous check out from Subversion</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>Use a command like:</p>
                                                 <pre>% svn checkout http://svn.apache.org/repos/asf/incubator/jdo </pre>
-                                                <strong>Commit Changes to Subversion</strong>
-                                                <p>
-Any JDO committer should have a shell account on
-<tt>svn.apache.org</tt>.  Before you can commit, you'll need to set a
-Subversion password for yourself.  To do that, log in to
-<tt>svn.apache.org</tt> and run the command <i>svnpasswd</i>.
-</p>
-                                                <p>
-Once your password is set, you can use a command like this to commit:
-</p>
-                                                <pre>svn commit</pre>
-                                                <p>If Subversion can't figure out your username, you can tell it
-explicitly:</p>
-                                                <pre>svn --username your-username-here commit</pre>
-                                                <p>Subversion will prompt you for a password, and once you enter it once, it
-will remember it for you.  Note this is the password you configured with
-<tt>svnpasswd</tt>, not your shell or other password.</p>
+                                                <p>Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo. </p>
+                                                <pre>
+% svn update
+</pre>
                             </blockquote>
-        </p>
       </td></tr>
       <tr><td><br/></td></tr>
     </table>
-                                                <table border="0" cellspacing="0" cellpadding="2" width="100%">
-      <tr><td bgcolor="#525D76">
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
         <font color="#ffffff" face="arial,helvetica,sanserif">
-          <a name="Building JDO from Source"><strong>Building JDO from Source</strong></a>
+          <a name="Access from behind a firewall"><strong>Access from behind a firewall</strong></a>
         </font>
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>Refer to the <a href="http://wiki.apache.org/jdo/FrontPage">Wiki
-page</a> for details. Note that the JDO project is subdivided into several
-smaller projects, and each project is built separately. </p>
+                                    <p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
+                                                <pre>
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+</pre>
                             </blockquote>
-        </p>
       </td></tr>
       <tr><td><br/></td></tr>
     </table>
-                                                <table border="0" cellspacing="0" cellpadding="2" width="100%">
-      <tr><td bgcolor="#525D76">
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Access through a proxy"><strong>Access through a proxy</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
+                                                <p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
+                                                <p>Example : Edit the 'servers' file and add something like : </p>
+                                                <pre>
+[global]
+http-proxy-host = your.proxy.name
+http-proxy-port = 3128
+</pre>
+                                                <p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
         <font color="#ffffff" face="arial,helvetica,sanserif">
-          <a name="Current Version"><strong>Current Version</strong></a>
+          <a name="Committer access"><strong>Committer access</strong></a>
         </font>
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>The Apache subversion repository contains the latest code. </p>
-                                                <p><strong>Previous versions</strong> </p>
-                                                <p>Download the 2005-03-08 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-03-08.zip">here</a>.  It implements the remaining JDO TCK 1 query test cases. The subproject structure has been changed by adding directories java, dtd, jdo, etc. under src and test. The tck11 subproject uses some basic test configuration as described in <a href="/jdo/TestRunner">TestRunner</a>. </p>
-                                                <p>Download the 2005-02-17 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-17.zip">here</a>.  It fixes a problem with running the ri11/tck11 subprojects under windows.  Furthermore it updates some TCK query tests. </p>
-                                                <p>Download the 2005-02-10 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-10.zip">here</a>.  It includes logging changes and support for running the jars with J2SE 1.3. </p>
-                                                <p>Download the 2005-01-21 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-21.zip">here</a>. It includes a working copy of the tck11 sub-project. </p>
-                                                <p>Download the 2005-01-14 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-14.zip">here</a>. </p>
-                                                <p>Download the 2004-12-13 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2004-12-13.zip">here</a>.  </p>
+                                    <p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
+                                                <pre>
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="NetBeans CVS repository access"><strong>NetBeans CVS repository access</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" rel="nofollow" href="http://www.netbeans.org/community/sources">NetBeans sources</a> page for more info.  </p>
+                                                <p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
                             </blockquote>
         </p>
       </td></tr>
@@ -228,95 +255,85 @@
                                                 <table border="0" cellspacing="0" cellpadding="2" width="100%">
       <tr><td bgcolor="#525D76">
         <font color="#ffffff" face="arial,helvetica,sanserif">
-          <a name="Everything else"><strong>Everything else</strong></a>
+          <a name="Submitting Code Changes"><strong>Submitting Code Changes</strong></a>
         </font>
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <h2 id="head-b4db92eef118cd96f75654326d629108ab1b2ebf">Web Access</h2>
-                                                <p><a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/jdo"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11" /> http://svn.apache.org/viewcvs/incubator/jdo</a> </p>
-                                                <h2 id="head-69f36b261cdd6a451d71afd071e980facb8efd18">Anonymous access</h2>
-                                                <p>Apache JDO source can be checked out anonymously with this command: </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
-% svn checkout http://svn.apache.org/repos/asf/incubator/jdo 
-</pre>
-</li>
-</ul>
-                                                <p>Once you have Apacje JDO checked out you can update the source by executing the following command from within the jdo. </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
-% svn update
-</pre>
-</li>
-</ul>
-                                                <h2 id="head-33604d44bc68f38236ff0009b6b6e1797ae2439b">Access from behind a firewall</h2>
-                                                <p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
-</pre>
-</li>
-</ul>
-                                                <h2 id="head-097c9dce4eeef776d9a83883743ceb63828dd02a">Access through a proxy</h2>
-                                                <p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
-                                                <p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
-                                                <p>Example : Edit the 'servers' file and add something like : </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
-[global]
-http-proxy-host = your.proxy.name
-http-proxy-port = 3128
-</pre>
-</li>
-</ul>
-                                                <p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
-                                                <h2 id="head-9c935033e1dc50f91ed53944598dc136159bab9a">Submitting a Patch</h2>
-                                                <p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a href="mailto:jdo-dev@db.apache.org"><img src="/wiki/modern/img/moin-email.png" alt="[MAILTO]" height="10" width="14" /> jdo-dev@db.apache.org</a>.  To create a patch, simply execute the following command: </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
+                                        <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Submitting a patch"><strong>Submitting a patch</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a href="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</a>.  To create a patch, simply execute the following command: </p>
+                                                <pre>
 % svn diff &gt; your-changes.patch
 </pre>
-</li>
-</ul>
-                                                <h2 id="head-253262c428af230484d34abd39cfd93de3b353c2">Developer Access</h2>
-                                                <p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
-</pre>
-</li>
-</ul>
-                                                <p>To commit changes to the repository, you must set your password on the Apache Subversion server.  To set your password, use ssh to connect to svn.apache.org, and enter the command <strong>svnpasswd</strong>. This will prompt you to enter a svn password of your choice (pick a safe password).  Now, now your are ready to commit changes using your username/password.  Execute the following command to commit your changes (svn will prompt you for your password) </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Committing changes to subversion"><strong>Committing changes to subversion</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>
+To commit changes to the Subversion repository, you must be an Apache JDO committer.  See <a href="get-involved.html">Get Involved</a> for information on how to become a committer and how to set up your password once you become a committer.
+</p>
+                                                <p>
+Once your password is set, you can use a command like this to commit:
+</p>
+                                                <pre>
 $&gt; svn commit --username your-username
 Authentication realm: &lt;https://svn.apache.org:443&gt; ASF Committers
 Password for 'your-username': your-password
 </pre>
-</li>
-</ul>
                                                 <p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command).  Here is the command if you are Windows or a single user unix computer: </p>
-                                                <ul>
-<li style="list-style-type:none">
-<pre>
+                                                <pre>
 $&gt; svn commit --username your-username --password your-password
 </pre>
-</li>
-</ul>
                                                 <p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
-                                                <h2 id="head-8e58b63eac33a4eaa91c2926015d99401b80ef5b">NetBeans CVS Repository Access</h2>
-                                                <p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" rel="nofollow" href="http://www.netbeans.org/community/sources"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11" /> NetBeans sources</a> page for more info.  </p>
-                                                <p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
-                                                <h2 id="head-496a9059e3fcee99aa23246c9c99caa907cc696c">Using subversion on Windows with cygwin</h2>
-                                                <p>If you use subversion on Windows under cygwin, you may find that the subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <em>svn diff</em> of the file: 
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                            </blockquote>
+        </p>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#525D76">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Building JDO from Source"><strong>Building JDO from Source</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>Refer to the <a href="http://wiki.apache.org/jdo/FrontPage">Wiki
+page</a> for details. Note that the JDO project is subdivided into several
+smaller projects, and each project is built separately. </p>
+                            </blockquote>
+        </p>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#525D76">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Using Subversion on Windows with cygwin"><strong>Using Subversion on Windows with cygwin</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <em>svn diff</em> of the file: 
 </p>
                                                 <pre>
 Property changes on: test/sql/derby/datastoreidentity/schema1.sql
@@ -325,21 +342,61 @@
    + *
 </pre>
                                                 <p>This section explains the source of the problem and suggests some actions to avoid it. </p>
-                                                <h3 id="head-25f2f810af0c983529ce4e0cf1c97a1c79407d37">Background</h3>
-                                                <p>Subversion carries executable information in the built-in property called svn:executable.  This property, unlike others,  may be present or absent, but it has no value.  You can add it or delete it, but but you cannot change its value. </p>
-                                                <p>In theory, subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Background"><strong>Background</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>Subversion carries executable information in the built-in property called svn:executable.  This property, unlike others,  may be present or absent, but it has no value.  You can add it or delete it, but but you cannot change its value. </p>
+                                                <p>In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
                                                 <p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <em>svn add</em>. </p>
-                                                <h3 id="head-30974b27025652b23debaf98550ad8f306b4f514">Removing existing executable properties from the repository</h3>
-                                                <p>You can use svn propdel to remove the svn:executable property from your working copy. 
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Removing existing executable properties from the repository"><strong>Removing existing executable properties from the repository</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>You can use svn propdel to remove the svn:executable property from your working copy. 
 </p>
                                                 <pre>
     svn propdel -R svn:executable .
 </pre>
                                                 <p>will recursively remove the svn:executable property from all of the files below the current directory.  You can use this and commit the files to clean the repository if necessary. </p>
-                                                <h3 id="head-83054b7348b09c545266af376baebd316a69fb9a">Preventing subversion from adding unwanted executable properties</h3>
-                                                <p>Windows/cygwin users who don't want to have to think about using <em>svn propdel</em> or <em>chmod</em> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11" /> http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation, add the svn.exe location to your Windows PATH variable. You must also remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. </p>
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
+                                                    <table border="0" cellspacing="0" cellpadding="2" width="100%">
+      <tr><td bgcolor="#828DA6">
+        <font color="#ffffff" face="arial,helvetica,sanserif">
+          <a name="Preventing Subversion from adding unwanted executable properties"><strong>Preventing Subversion from adding unwanted executable properties</strong></a>
+        </font>
+      </td></tr>
+      <tr><td>
+        <blockquote>
+                                    <p>Windows/cygwin users who don't want to have to think about using <em>svn propdel</em> or <em>chmod</em> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html">http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn </p>
+                                                <ol type="1">
+<li><p>Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category.  Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.) </p>
+
+</li>
+<li><p>Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\&lt;user&gt;\Application Data\Subversion used by Win32 subversion. </p>
+</li>
+</ol>
+                                                <p>Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes. </p>
                                                 <p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder &amp; select Properties. Select the Security tab. Click Advanced. Remove all instances of Read &amp; Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
-                                                <a id="bottom" />
+                            </blockquote>
+      </td></tr>
+      <tr><td><br/></td></tr>
+    </table>
                             </blockquote>
         </p>
       </td></tr>

Modified: incubator/jdo/site/docs/team-list.html
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/docs/team-list.html?rev=279676&r1=279675&r2=279676&view=diff
==============================================================================
--- incubator/jdo/site/docs/team-list.html (original)
+++ incubator/jdo/site/docs/team-list.html Thu Sep  8 16:42:29 2005
@@ -131,6 +131,10 @@
     If there is nothing in there that suits your interest, but you still have
     ideas, please feel free to suggest them on the mailing list.
 </p>
+                                                <p>
+    If you would like to become a committer, please see
+    <a href="get-involved.html">Get Involved</a>.
+</p>
                                                 <table>
                         <tr>
                         <th bgcolor="#039acc" colspan="" rowspan="" valign="top" align="left">

Modified: incubator/jdo/site/xdocs/get-involved.xml
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/xdocs/get-involved.xml?rev=279676&r1=279675&r2=279676&view=diff
==============================================================================
--- incubator/jdo/site/xdocs/get-involved.xml (original)
+++ incubator/jdo/site/xdocs/get-involved.xml Thu Sep  8 16:42:29 2005
@@ -36,8 +36,32 @@
       Additional documentation and discussion can be found on the project
      <a href="http://wiki.apache.org/jdo/">wiki</a>
    </li>
+    <li>
+    We have a communications conference call every Friday at 9:00 AM Pacific time. The conference call number is 866 230-6968 (international 865 544-7856) code 294-0479#. During this call we discuss project status, issues, concerns, and strategy. Everyone interested in Apache JDO is welcome and encouraged to participate. 
+   </li>
 </ul>
 
 </section>
+
+<section name="How do I become a committer?">
+<p>If you're interested in committing to the project: </p>
+<ul>
+<li><p> You'll need to fill out some legal paperwork and go through a process to get an apache committer account: See <a  class="external" rel="nofollow" href="http://apache.org/dev/new-committers-guide.html">New Committers Guide</a>, <a  class="external" rel="nofollow" href="http://apache.org/dev/contributors.html">Contributors</a>, and <a  class="external" rel="nofollow" href="http://apache.org/dev/committers.html">Committers</a> for more details. </p>
+
+</li>
+<li><p> After you've received an email from <a  href="mailto:root@apache.org">root@apache.org</a> with your committer account information, change your initial password: Login by 'ssh -l &lt;username&gt; cvs.apache.org' (soon 'people.apache.org', as by apache email announcement); run 'passwd'; run 'svnpasswd'. See <a  class="external" rel="nofollow" href="http://apache.org/dev/version-control.html">Committer Subversion Access</a>. </p>
+</li>
+<li><p> Check out the JDO sources and test your svn account: <a  href="http://svn.apache.org/viewcvs.cgi/incubator/jdo/">SubversionRepository</a>. </p>
+
+</li>
+<li><p> Sign up for a <a  class="external" rel="nofollow" href="http://wiki.apache.org/jdo/UserPreferences">WiKi</a> account. </p>
+</li>
+<li><p> Sign up for an <a  class="external" rel="nofollow" href="http://issues.apache.org/jira/">ASF JIRA</a> account. </p>
+</li>
+
+</ul>
+
+</section>
+
 </body>
 </document>

Modified: incubator/jdo/site/xdocs/svn.xml
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/xdocs/svn.xml?rev=279676&r1=279675&r2=279676&view=diff
==============================================================================
--- incubator/jdo/site/xdocs/svn.xml (original)
+++ incubator/jdo/site/xdocs/svn.xml Thu Sep  8 16:42:29 2005
@@ -28,13 +28,14 @@
 
 <section name="Apache JDO Source Code">
 
-<p>Apache JDO uses <a  class="external" rel="nofollow" href="http://subversion.tigris.org">Subversion</a> to manage its source code. Instructions on Subversion use can be found <a  class="external" rel="nofollow" href="http://svnbook.red-bean.com">here</a>. To receive notice of commits to the repository subscribe to <a  href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a  href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
-<p>
+<p>Apache JDO uses <a  class="external" rel="nofollow" href="http://subversion.tigris.org">Subversion</a> to manage its source code.
 If you're new to Subversion, you can check out the
 <a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
 Note that we are currently using Subversion 1.1.x (there are separate
 versions of the book covering 1.0 and 1.1).
 </p>
+<p>
+To receive notice of commits to the repository subscribe to <a  href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a  href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
 
 </section>
 
@@ -42,171 +43,104 @@
 
 <p>
 If you just want to browse the source code, you can use the
-<a
-href="http://svn.apache.org/viewcvs.cgi/jdo/trunk/?root=Apache-SVN">ViewCVS
-web interface</a> to Subversion.  This is current at all times.
+<a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/jdo">
+ViewCVS web interface</a> to Subversion.  This is current at all times.
 </p>
 
 </section>
 
-<section name="Normal Subversion Access">
+<section name="Checking Out Code Using Subversion">
 
-<p>Anyone can check code out of Subversion.  You need to specify a
-username and password in order to update the Subversion repository, and only
-JDO committers have the permissions to do that.  We run Subversion
-over standard HTTPS. You might need to set up your local subversion
-network configuration for local proxies. Hopefully you won't have 
-problems with intervening firewalls.</p>
+<p>Anyone can check code out of Subversion.  You only need to specify a
+username and password to update the Subversion repository, and only
+JDO committers can do that.
+If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.</p>
 
-<strong>Check out from Subversion</strong>
+<subsection name="Anonymous check out from Subversion">
 <p>Use a command like:</p>
 <pre>% svn checkout http://svn.apache.org/repos/asf/incubator/jdo </pre>
-
-<strong>Commit Changes to Subversion</strong>
-
-<p>
-Any JDO committer should have a shell account on
-<tt>svn.apache.org</tt>.  Before you can commit, you'll need to set a
-Subversion password for yourself.  To do that, log in to
-<tt>svn.apache.org</tt> and run the command <i>svnpasswd</i>.
-</p>
-
-<p>
-Once your password is set, you can use a command like this to commit:
-</p>
-
-<pre>svn commit</pre>
-
-<p>If Subversion can't figure out your username, you can tell it
-explicitly:</p>
-<pre>svn --username your-username-here commit</pre>
-<p>Subversion will prompt you for a password, and once you enter it once, it
-will remember it for you.  Note this is the password you configured with
-<tt>svnpasswd</tt>, not your shell or other password.</p>
-
-</section>
-
-<section name="Building JDO from Source">
-<p>Refer to the <a href="http://wiki.apache.org/jdo/FrontPage">Wiki
-page</a> for details. Note that the JDO project is subdivided into several
-smaller projects, and each project is built separately. </p>
-
-</section>
-
-<section name="Current Version">
-
-<p>The Apache subversion repository contains the latest code. </p>
-<p><strong>Previous versions</strong> </p>
-<p>Download the 2005-03-08 version <a  href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-03-08.zip">here</a>.  It implements the remaining JDO TCK 1 query test cases. The subproject structure has been changed by adding directories java, dtd, jdo, etc. under src and test. The tck11 subproject uses some basic test configuration as described in <a  href="/jdo/TestRunner">TestRunner</a>. </p>
-<p>Download the 2005-02-17 version <a  href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-17.zip">here</a>.  It fixes a problem with running the ri11/tck11 subprojects under windows.  Furthermore it updates some TCK query tests. </p>
-<p>Download the 2005-02-10 version <a  href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-10.zip">here</a>.  It includes logging changes and support for running the jars with J2SE 1.3. </p>
-<p>Download the 2005-01-21 version <a  href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-21.zip">here</a>. It includes a working copy of the tck11 sub-project. </p>
-<p>Download the 2005-01-14 version <a  href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-14.zip">here</a>. </p>
-<p>Download the 2004-12-13 version <a  href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2004-12-13.zip">here</a>.  </p>
-
-</section>
-
-<section name="Everything else">
-
-<h2 id="head-b4db92eef118cd96f75654326d629108ab1b2ebf">Web Access</h2>
-
-<p><a  class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/jdo"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11"/> http://svn.apache.org/viewcvs/incubator/jdo</a> </p>
-
-<h2 id="head-69f36b261cdd6a451d71afd071e980facb8efd18">Anonymous access</h2>
-
-<p>Apache JDO source can be checked out anonymously with this command: </p>
-<ul>
-<li style="list-style-type:none">
-<pre>
-% svn checkout http://svn.apache.org/repos/asf/incubator/jdo 
-</pre>
-</li>
-</ul>
-<p>Once you have Apacje JDO checked out you can update the source by executing the following command from within the jdo. </p>
-<ul>
-<li style="list-style-type:none">
+<p>Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo. </p>
 <pre>
 % svn update
 </pre>
-</li>
-</ul>
-
-<h2 id="head-33604d44bc68f38236ff0009b6b6e1797ae2439b">Access from behind a firewall</h2>
+</subsection>
+<subsection name="Access from behind a firewall">
 
 <p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
-<ul>
-<li style="list-style-type:none">
 <pre>
 % svn checkout https://svn.apache.org/repos/asf/incubator/jdo
 </pre>
-</li>
-</ul>
 
-<h2 id="head-097c9dce4eeef776d9a83883743ceb63828dd02a">Access through a proxy</h2>
+</subsection>
+<subsection name="Access through a proxy">
 
 <p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
 <p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
 <p>Example : Edit the 'servers' file and add something like : </p>
-<ul>
-<li style="list-style-type:none">
 <pre>
 [global]
 http-proxy-host = your.proxy.name
 http-proxy-port = 3128
 </pre>
-</li>
-</ul>
 <p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
 
-<h2 id="head-9c935033e1dc50f91ed53944598dc136159bab9a">Submitting a Patch</h2>
+</subsection>
+
+<subsection name="Committer access">
 
-<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a  href="mailto:jdo-dev@db.apache.org"><img src="/wiki/modern/img/moin-email.png" alt="[MAILTO]" height="10" width="14"/> jdo-dev@db.apache.org</a>.  To create a patch, simply execute the following command: </p>
-<ul>
-<li style="list-style-type:none">
+<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
 <pre>
-% svn diff &gt; your-changes.patch
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
 </pre>
-</li>
-</ul>
+</subsection>
+<subsection name="NetBeans CVS repository access">
 
-<h2 id="head-253262c428af230484d34abd39cfd93de3b353c2">Developer Access</h2>
+<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a  class="external" rel="nofollow" href="http://www.netbeans.org/community/sources">NetBeans sources</a> page for more info.  </p>
+<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a  href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+</subsection>
+</section>
 
-<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
-<ul>
-<li style="list-style-type:none">
+<section name="Submitting Code Changes">
+<subsection name="Submitting a patch">
+
+<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a  href="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</a>.  To create a patch, simply execute the following command: </p>
 <pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+% svn diff &gt; your-changes.patch
 </pre>
-</li>
-</ul>
-<p>To commit changes to the repository, you must set your password on the Apache Subversion server.  To set your password, use ssh to connect to svn.apache.org, and enter the command <strong>svnpasswd</strong>. This will prompt you to enter a svn password of your choice (pick a safe password).  Now, now your are ready to commit changes using your username/password.  Execute the following command to commit your changes (svn will prompt you for your password) </p>
-<ul>
-<li style="list-style-type:none">
+</subsection>
+
+<subsection name="Committing changes to subversion">
+<p>
+To commit changes to the Subversion repository, you must be an Apache JDO committer.  See <a href="get-involved.html">Get Involved</a> for information on how to become a committer and how to set up your password once you become a committer.
+</p>
+
+<p>
+Once your password is set, you can use a command like this to commit:
+</p>
 <pre>
 $&gt; svn commit --username your-username
 Authentication realm: &lt;https://svn.apache.org:443&gt; ASF Committers
 Password for 'your-username': your-password
 </pre>
-</li>
-</ul>
 <p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command).  Here is the command if you are Windows or a single user unix computer: </p>
-<ul>
-<li style="list-style-type:none">
 <pre>
 $&gt; svn commit --username your-username --password your-password
 </pre>
-</li>
-</ul>
 <p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
 
-<h2 id="head-8e58b63eac33a4eaa91c2926015d99401b80ef5b">NetBeans CVS Repository Access</h2>
+</subsection>
+</section>
 
-<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a  class="external" rel="nofollow" href="http://www.netbeans.org/community/sources"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11"/> NetBeans sources</a> page for more info.  </p>
-<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a  href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+<section name="Building JDO from Source">
+<p>Refer to the <a href="http://wiki.apache.org/jdo/FrontPage">Wiki
+page</a> for details. Note that the JDO project is subdivided into several
+smaller projects, and each project is built separately. </p>
+
+</section>
 
-<h2 id="head-496a9059e3fcee99aa23246c9c99caa907cc696c">Using subversion on Windows with cygwin</h2>
+<section name="Using Subversion on Windows with cygwin">
 
-<p>If you use subversion on Windows under cygwin, you may find that the subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <em>svn diff</em> of the file: 
+<p>If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <em>svn diff</em> of the file: 
 </p>
 <pre>
 Property changes on: test/sql/derby/datastoreidentity/schema1.sql
@@ -216,13 +150,13 @@
 </pre>
 <p>This section explains the source of the problem and suggests some actions to avoid it. </p>
 
-<h3 id="head-25f2f810af0c983529ce4e0cf1c97a1c79407d37">Background</h3>
+<subsection name="Background">
 
 <p>Subversion carries executable information in the built-in property called svn:executable.  This property, unlike others,  may be present or absent, but it has no value.  You can add it or delete it, but but you cannot change its value. </p>
-<p>In theory, subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
+<p>In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
 <p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <em>svn add</em>. </p>
-
-<h3 id="head-30974b27025652b23debaf98550ad8f306b4f514">Removing existing executable properties from the repository</h3>
+</subsection>
+<subsection name="Removing existing executable properties from the repository">
 
 <p>You can use svn propdel to remove the svn:executable property from your working copy. 
 </p>
@@ -231,11 +165,21 @@
 </pre>
 <p>will recursively remove the svn:executable property from all of the files below the current directory.  You can use this and commit the files to clean the repository if necessary. </p>
 
-<h3 id="head-83054b7348b09c545266af376baebd316a69fb9a">Preventing subversion from adding unwanted executable properties</h3>
+</subsection>
+<subsection name="Preventing Subversion from adding unwanted executable properties">
 
-<p>Windows/cygwin users who don't want to have to think about using <em>svn propdel</em> or <em>chmod</em> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a  rel="nofollow" href="http://subversion.tigris.org/project_packages.html"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11"/> http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation, add the svn.exe location to your Windows PATH variable. You must also remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. </p>
+<p>Windows/cygwin users who don't want to have to think about using <em>svn propdel</em> or <em>chmod</em> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a  rel="nofollow" href="http://subversion.tigris.org/project_packages.html">http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn </p>
+<ol type="1">
+<li><p>Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category.  Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.) </p>
+
+</li>
+<li><p>Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\&lt;user&gt;\Application Data\Subversion used by Win32 subversion. </p>
+</li>
+</ol>
+<p>Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes. </p>
 <p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder &amp; select Properties. Select the Security tab. Click Advanced. Remove all instances of Read &amp; Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
-<a id="bottom"></a>
+
+</subsection>
 </section>
 </body>
 </document>

Modified: incubator/jdo/site/xdocs/team-list.xml
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/xdocs/team-list.xml?rev=279676&r1=279675&r2=279676&view=diff
==============================================================================
--- incubator/jdo/site/xdocs/team-list.xml (original)
+++ incubator/jdo/site/xdocs/team-list.xml Thu Sep  8 16:42:29 2005
@@ -24,6 +24,10 @@
     If there is nothing in there that suits your interest, but you still have
     ideas, please feel free to suggest them on the mailing list.
 </p>
+<p>
+    If you would like to become a committer, please see
+    <a href="get-involved.html">Get Involved</a>.
+</p>
 
 <table>
 <tr><th>Name</th><th>Organization</th></tr>



Mime
View raw message