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

[gnudist's file diff daemon]

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

  11 -rw-rw-r--   1 webcvs   www         10776 Sep 21 14:16 
/home/www/html/server/standards/README.webmastering.html

diff  -u  
/home/diffmon/old_file_dir/gnudist:!home!www!html!server!standards!README.webmastering.html.gz
 /home/www/html/server/standards/README.webmastering.html
--- /tmp/diffmon7490    Sat Sep 22 05:33:11 2001
+++ /home/www/html/server/standards/README.webmastering.html    Fri Sep 21 
14:16:16 2001
@@ -128,6 +128,66 @@
 our web pages it happens quite often that we receive spam to that
 address. It's best to simply ignore such messages.
 
+<h4>Handling Press Releases</h4>
+
+Occasionally, the webmasters are asked to handle press releases.  These
+are in the <a href="/press">/press</a> directory.  You should always make
+both a text and HTML version, and follow the format used for other press
+releases.  (Some do have PDF and Postscript, but webmasters need not worry
+about that at the moment).
+
+<P>
+
+Currently, it is often <a href="mailto:address@hidden";>bkuhn</a>
+who handles the text version of a press release (although will hopefully
+change sometime in 2002).  He will normally commit the <code>.txt</code>
+file version, and then tell webmasters to do the "rest" or "DTRT" with it.
+He will also give a date and time when the press release should be up.
+
+<p>
+
+For the time being, always check with bkuhn before posting any press
+releases sent in by other parties, and note that bkuhn will always
+GPG-sign his messages about press releases.
+
+<p>
+
+To handle one of these requests, here is what you should do:
+<ul>
+
+<li>Make an HTML version of the <code>.txt</code> file, following the
+    format used for other press releases.  Be sure to change the
+    <code>META</code> tags for <code>Keywords</code> and
+    <code>Description</code> to reflect the new press release.
+</li><p>
+
+<li>Make an entry at the top of the list on <a
+    href="/press/press.html">/press/press.html</a> for the press
+    release.</li><p>
+
+<li>Add an entry for it on <a
+    href="/server/whatsnew.html">/server/whatsnew.html</a>.  <p></li>
+
+<li>Add an entry for it on the GNU's Flashes of <a
+          href="/home.html">/home.html</a>, unless the request to post the
+          release specifically says <em>not</em> to put a note there.</li><p>
+
+ <li> A release date and time "window" will be included in the request to
+      post it.  The <code>cvs commit</code> should <strong>only be
+      done</strong> in that window.  If you won't be able to do it then,
+      use the <code>makepatch</code> command (it's in the makepatch
+      package of Debian) to send a patch back to bkuhn, and put URGENT in
+      the subject line.</li><p>
+
+ <li> The final step is submitting it as a story to as many news sites as
+        possible (linuxtoday.com, slashdot.org, and newsforge.com should
+        definitely be done).  This can be done later in the same day as
+        when the release goes up, but should also be done the same
+        day.</li><p>
+</ul>
+
+<p>
+
 
 <h4>Webmaster Organization</h4>
 
@@ -204,7 +264,7 @@
 permitted in any medium, provided this notice is preserved.<P>
 Updated:
 <!-- timestamp start -->
-$Date: 2001/04/14 00:58:14 $ $Author: bkuhn $
+$Date: 2001/09/21 21:16:10 $ $Author: bkuhn $
 <!-- timestamp end -->
 <HR>
 </BODY>