[GNU-traductores] gnudist:/home/www/html/server/standards/README.savannah.html -- recent changes

[gnudist's file diff daemon]

This is an automated report from gnudist.
Recent changes to /home/www/html/server/standards/README.savannah.html:

  81 -rw-rw-r--    1 webcvs   www         81228 Jan  9 04:10 
/home/www/html/server/standards/README.savannah.html

diff  -u  
/home/diffmon/old_file_dir/gnudist:!home!www!html!server!standards!README.savannah.html.gz
 /home/www/html/server/standards/README.savannah.html
--- /tmp/diffmon6614    Wed Jan  9 08:07:44 2002
+++ /home/www/html/server/standards/README.savannah.html        Wed Jan  9 
04:10:23 2002
@@ -53,12 +53,20 @@
 
 </p><li><a href="#Import%20repositories">Import repositories</a>: 
 <li><a href="#Sources%20CVS%20repositories">Sources CVS repositories</a>: 
+<li><a href="#Getting%20email%20from%20CVS">Getting email from CVS</a>: 
 <li><a href="#Source%20CVS%20tarbals">Source CVS tarbals</a>: 
 <li><a href="#Web%20CVS%20repositories">Web CVS repositories</a>: 
 <li><a href="#Web%20CVS%20Symbolic%20links">Web CVS Symbolic links</a>: 
 <li><a href="#Sync%20of%20www.gnu.org%20on%20commit">Sync of www.gnu.org on 
commit</a>: 
 <li><a href="#Web%20CVS%20and%20Projects">Web CVS and Projects</a>:
 
+<p>Getting email from CVS
+
+</p><li><a href="#Set%20up%20a%20mailing%20list">Set up a mailing list</a>: 
+<li><a href="#Set%20up%20syncmail">Set up syncmail</a>: 
+<li><a href="#Configure%20CVS%20to%20use%20syncmail">Configure CVS to use 
syncmail</a>: 
+<li><a href="#Read%20email!">Read email!</a>:
+
 <p>Database
 
 </p><li><a href="#Remote%20Access">Remote Access</a>: 
@@ -227,6 +235,7 @@
 <ul>
 <li><a href="#Import%20repositories">Import repositories</a>: 
 <li><a href="#Sources%20CVS%20repositories">Sources CVS repositories</a>: 
+<li><a href="#Getting%20email%20from%20CVS">Getting email from CVS</a>: 
 <li><a href="#Source%20CVS%20tarbals">Source CVS tarbals</a>: 
 <li><a href="#Web%20CVS%20repositories">Web CVS repositories</a>: 
 <li><a href="#Web%20CVS%20Symbolic%20links">Web CVS Symbolic links</a>: 
@@ -258,7 +267,7 @@
 
 <p><hr>
 Node:<a name="Sources%20CVS%20repositories">Sources CVS repositories</a>,
-Next:<a rel=next href="#Source%20CVS%20tarbals">Source CVS tarbals</a>,
+Next:<a rel=next href="#Getting%20email%20from%20CVS">Getting email from 
CVS</a>,
 Previous:<a rel=previous href="#Import%20repositories">Import repositories</a>,
 Up:<a rel=up href="#CVS%20repositories">CVS repositories</a>
 <br>
@@ -308,9 +317,206 @@
 user/password pairs that are in the Savannah database.
 
 <p><hr>
+Node:<a name="Getting%20email%20from%20CVS">Getting email from CVS</a>,
+Next:<a rel=next href="#Source%20CVS%20tarbals">Source CVS tarbals</a>,
+Previous:<a rel=previous href="#Sources%20CVS%20repositories">Sources CVS 
repositories</a>,
+Up:<a rel=up href="#CVS%20repositories">CVS repositories</a>
+<br>
+
+<h2>Getting email from CVS</h2>
+
+<p>In any large project, keeping track of changes is difficult.  CVS does
+a reasonable job of allowing source changes to be controlled and
+managed, but does not provide tools to make it easier to work with a
+changing code base.  The hardest part of working on a dynamic project
+with many changing modules is knowing when changes occur, and what
+those changes are.
+
+<p>Software developers often are heavy email users, spending huge amounts
+of time working with their email software.  Free software developers are
+among the most serious email addicts out there, sorting through
+hundreds of emails a day, since this is often the only way to stay in
+touch with users and fellow developers.
+
+<p><code>Clearly, we need more email</code>.
+
+<ul>
+<li><a href="#Set%20up%20a%20mailing%20list">Set up a mailing list</a>: 
+<li><a href="#Set%20up%20syncmail">Set up syncmail</a>: 
+<li><a href="#Configure%20CVS%20to%20use%20syncmail">Configure CVS to use 
syncmail</a>: 
+<li><a href="#Read%20email!">Read email!</a>: 
+</ul>
+
+<p><hr>
+Node:<a name="Set%20up%20a%20mailing%20list">Set up a mailing list</a>,
+Next:<a rel=next href="#Set%20up%20syncmail">Set up syncmail</a>,
+Previous:<a rel=previous href="#Getting%20email%20from%20CVS">Getting email 
from CVS</a>,
+Up:<a rel=up href="#Getting%20email%20from%20CVS">Getting email from CVS</a>
+<br>
+
+<h3>Set up a mailing list</h3>
+
+<p>If you haven't already created a mailing list to handle messages sent
+by CVS, follow these instructions to do so.
+
+<p>To get started, surf to your project's "Project Page."  If the "Public
+Areas" section of the page doesn't list "Mailing Lists," click over to
+the <code>Project Admin</code> page, the to the <code>Edit Public Info</code>
+page.  Make sure the "Use Mailing Lists:" checkbox is on, and click
+"Update."  Now go back to your "Project Page."
+
+<p>Go to the <code>Mailing Lists</code> page and click through to the
+<code>Admin</code> page.  Select <code>Add Mailing List</code> to get a really
+easy-to-use form that asks you only <code>two questions</code>:
+
+<dl>
+<dt><code>What do you want to name your list?</code>
+<dd>
+Since all Savannah list names start with the Unix name of your
+project and a hyphen, you don't even have to worry about that part! 
+You just decide on the hard part: "Do I call it
+<code>myproject-commits</code>, or <code>myproject-checkins</code>?"  You can
+choose other names, but those are well-recognized by active Free
+Software developers.
+
+<br><dt><code>Should I let just anyone subscribe?</code>
+<dd>
+"Yes" will already be checked for you, so leave it that way.  You want
+your users to be able to subscribe so they'll know when you've fixed
+the bug they reported, because they want to try out the changes as
+soon as they're in.
+
+</dl>
+
+<p>Ok, so you really only had to decide one thing - that's even better. 
+Now, click the "Add This List" button, and wait for your list to be
+created.
+
+<p><hr>
+Node:<a name="Set%20up%20syncmail">Set up syncmail</a>,
+Next:<a rel=next href="#Configure%20CVS%20to%20use%20syncmail">Configure CVS 
to use syncmail</a>,
+Previous:<a rel=previous href="#Set%20up%20a%20mailing%20list">Set up a 
mailing list</a>,
+Up:<a rel=up href="#Getting%20email%20from%20CVS">Getting email from CVS</a>
+<br>
+
+<h3>Set up syncmail</h3>
+
+<p><code>syncmail</code> is a <a href="http://www.python.org/";>Python</a>
+script written by Barry Warsaw to send mail to the
+<code>python-checkins</code> list long ago, before the Python development
+tree moved to SourceForge.  It's undergone a bit of evolution, but
+essentially does one thing: send email based on CVS activity.  It
+takes a little bit of information from CVS and generates messages that
+include useful information, such as the actual changes that happened
+to the modified files.  It shoves all this into email that gets sent
+to an email address passed on the command line.  For projects with
+enough developers that <code>syncmail</code> becomes interesting, this will
+typically be a mailing list.
+
+<p>For your project, this will be
+<code>address@hidden</code> or
+<code>address@hidden</code>, depending on the name
+you chose in the first part of these instructions.
+
+<p>To install <code>syncmail</code>, you need a working copy of the 
<code>CVSROOT</code> directory from your CVS repository. 
+Check it out just like you did for your project modules, but with the module 
name "CVSROOT".
+
+<p>Now, get the latest version of <code>syncmail</code>.  The canonical copy 
is in the repository for the
+<a href="http://www.list.org/";>GNU Mailman</a> mailing list manager (the one 
you're using for the checkins list you set up earlier). 
+Get it from Savannah:
+
+<a 
href="https://savannah.gnu.org/syncmail";>https://savannah.gnu.org/syncmail</a>
+
+<p>Save the most recent revision to your working copy of your project's
+<code>CVSROOT</code> directory.  Use <code>chmod +x</code>
+to set the executable bit for all users, and then add the file to your
+project: <code>cvs add syncmail</code>; <code>cvs commit syncmail</code>.  You
+probably want to mention in your comment message where the file came
+from and the revision number you picked up.
+
+<p>Now just edit the "checkoutlist" file in the CVSROOT.  Just add "syncmail" 
to
+the bottom of the file.  Save it and checkin.  Now syncmail will be 
automatically
+checked out whenever necessary.
+
+<p><hr>
+Node:<a name="Configure%20CVS%20to%20use%20syncmail">Configure CVS to use 
syncmail</a>,
+Next:<a rel=next href="#Read%20email!">Read email!</a>,
+Previous:<a rel=previous href="#Set%20up%20syncmail">Set up syncmail</a>,
+Up:<a rel=up href="#Getting%20email%20from%20CVS">Getting email from CVS</a>
+<br>
+
+<h3>Configure CVS to use syncmail</h3>
+
+<p>Now that you've spent the better part of a day (or night) reading
+these instructions, and a few minutes following them, you have just a
+tiny bit more to do to get CVS to put <code>syncmail</code> to work.
+
+<p><code>After</code> you've handled the checkout a working copy of 
<code>syncmail</code>
+into the repository, you need to modify your <code>CVSROOT/loginfo</code> file 
to tell CVS to invoke
+<code>syncmail</code> for all the interesting events CVS is willing to tell
+us about.
+
+<p>If you have not modified the <code>CVSROOT/loginfo</code> file from the 
stock file provided by
+Savannah (which is very useful, as the comments include
+documentation), what you need to do is very simple: just add stuff to
+the end.  Here's some example stuff to get you started:
+
+<pre>CVSROOT $CVSROOT/CVSROOT/syncmail %{sVv} address@hidden
+
+DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} address@hidden
+</pre>
+
+<p>This will cause email to be sent to two different places, with which
+depending on what files in the repository are affected.  For
+administrative files in the <code>CVSROOT</code>
+directory, email will be sent to <code>address@hidden</code>; you
+should probably list all your project administrators here.  For all
+other files, email will be sent to your mailing list (remember to
+change the list name to match <code>your</code> mailing list!).
+
+<p>If you have several sub-products for which you want different checkin
+lists, you can change the "DEFAULT" label to match the subtree that
+you want to go to each list, with a separate line for each distinct
+prefix.  For example, if your project includes the products "one" and
+"two", you could use the following:
+
+<pre>CVSROOT $CVSROOT/CVSROOT/syncmail %{sVv} address@hidden
+
+one/ $CVSROOT/CVSROOT/syncmail %{sVv} address@hidden
++two/ $CVSROOT/CVSROOT/syncmail %{sVv} address@hidden
+</pre>
+
+<p>You can still have a "DEFAULT" line that gets used for any additional
+subprojects.
+
+<p>If you do <code>not</code> have a stock <code>CVSROOT/loginfo</code> file,
+then you can probably figure out what
+you need to do to combine the information above with your existing
+changes.  You might not have even needed any of these instructions!
+
+<p>Check in your changes to <code>CVSROOT/loginfo</code>
+and check in some other change in your working directories to test your
+new configuration.
+
+<p><hr>
+Node:<a name="Read%20email!">Read email!</a>,
+Previous:<a rel=previous 
href="#Configure%20CVS%20to%20use%20syncmail">Configure CVS to use syncmail</a>,
+Up:<a rel=up href="#Getting%20email%20from%20CVS">Getting email from CVS</a>
+<br>
+
+<h3>Read email!</h3>
+
+<p>Now for the real test.  If you have started a successful Free Software
+project, you will not be able to catch up with your email.  If you can
+keep up with it and still have time to hack, you need to make your
+project more attractive to others, so you can get more developers
+checking in more changes.  Then you'll always have more email than you
+know what to do with!
+
+<p><hr>
 Node:<a name="Source%20CVS%20tarbals">Source CVS tarbals</a>,
 Next:<a rel=next href="#Web%20CVS%20repositories">Web CVS repositories</a>,
-Previous:<a rel=previous href="#Sources%20CVS%20repositories">Sources CVS 
repositories</a>,
+Previous:<a rel=previous href="#Getting%20email%20from%20CVS">Getting email 
from CVS</a>,
 Up:<a rel=up href="#CVS%20repositories">CVS repositories</a>
 <br>
 
@@ -1786,6 +1992,13 @@
 <ul>
 <li><a href="#Import%20repositories">Import repositories</a>
 <li><a href="#Sources%20CVS%20repositories">Sources CVS repositories</a>
+<li><a href="#Getting%20email%20from%20CVS">Getting email from CVS</a>
+<ul>
+<li><a href="#Set%20up%20a%20mailing%20list">Set up a mailing list</a>
+<li><a href="#Set%20up%20syncmail">Set up syncmail</a>
+<li><a href="#Configure%20CVS%20to%20use%20syncmail">Configure CVS to use 
syncmail</a>
+<li><a href="#Read%20email!">Read email!</a>
+</ul>
 <li><a href="#Source%20CVS%20tarbals">Source CVS tarbals</a>
 <li><a href="#Web%20CVS%20repositories">Web CVS repositories</a>
 <li><a href="#Web%20CVS%20Symbolic%20links">Web CVS Symbolic links</a>