sync w/ latest cpan documents

1 files changed, 101 insertions, 115 deletions

diff --git a/cpan/doc/04pause.html b/cpan/doc/04pause.html
index 336e372e..60a0956c 100644
--- a/cpan/doc/04pause.html
+++ b/cpan/doc/04pause.html
@@ -6,9 +6,9 @@
 <h2><a href="https://pause.kbx.de/pause/">The Perl Authors Upload Server</a></h2>
 <p><i>
 <!-- hhmts start -->
-Last modified: Tue Dec  5 21:07:00 CET 2000
+Last modified: Sun May 20 08:29:18 CEST 2001
 <!-- hhmts end -->
-$Revision: 1.3 $
+$Revision: 1.64 $
 </i></p>
 
 <h3>Contents</h3>
@@ -34,7 +34,7 @@ This document is mirrored on CPAN as <i>CPAN</i>/modules/04pause.html.
 <h3><a id="upload" name="upload">Uploading</a></h3>
 
 A server dedicated to collect the work of perl authors is a <a
-href="https://pause.kbx.de/pause/">Perl Authors Upload Server
+href="https://pause.perl.org/pause/">Perl Authors Upload Server
 (PAUSE)</a>. PAUSE provides personal directories and enables their
 owners to upload their work into that directory themselves. The
 procedure of uploading is trivial and needs no explanation here.
@@ -79,72 +79,33 @@ archive, send the following to the maintainers at modules@perl.org
   <li> your homepage if you have one</li>
   <li> your preferred user-ID on CPAN. It must be between 4 and 9
 characters long, all uppercase, letters only. One dash allowed.</li>
-  <li> a description of what you're planning to contribute</li>
-  <li> for modules a description in module list format (DSLI
-entry, which is: Development stage, Support level, Language used,
-Interface style (see the <a
-href="00modlist.long.html#1)ModuleListing"
->modulelist</a>), and a 44 character description).</li>
-  <li> for scripts, ports, documentation, etc. please send a concise
-description that helps us to categorize the issue so we can forward
-your mail to the maintainers of the corresponding archive branch.</li>
-  <li> It would be very nice, if you could also send a note about
-where you have discussed some or all parts of your contribution
-publicly, and if there was at least a little bit of interest. We are
-quite open for submissions, but we owe our users at least some
-rudimentary quality control. If your work has never been discussed
-publicly, then it's extremely difficult for us to make our judgement
-whether to accept the submission or not.</li>
+  <li> a short description of what you're planning to contribute</li>
 </ul>
 
-<blockquote>
-Also: think carefully and honestly whether your module would be better
-off if it were integrated as an option into an already existing module.
-Sometimes it is for the best to put aside personal glory and join
-a collaborative effort: Perl itself is a good example of this.
-Contact the author of an existing module and ask whether your new
-features would fit into his framework.  Even if you in the end
-decide to release the module as your very own, you really should
-know your 'competition', that is, know all the similar modules
-and the features they offer.  Maybe you can learn from them.
-</blockquote>
-
 <p>You will be notified by email about your registration. Please allow
 three weeks for proceeding, which should be the maximum during
 vacation time. Normally we hope to register you within a week. All
 mails to modules@perl.org is archived at <a
 href="http://www.xray.mpe.mpg.de/mailing-lists/modules">http://www.xray.mpe.mpg.de/mailing-lists/modules</a>.
-modules@perl.org isn't a mailing list, just an alias for the front
-desk of the Perl 5 modules list. Please do not subscribe. Visit the
-archive instead.</p>
-
-<p>And please do consult these archive before you post a module proposal.
-The fulltext search capabilities of the archive should help you to
-find similar suggestions and contact addresses. modules@perl.org is
-low volume, so your search in the archive is quite targetted. The
-module list maintainers themselves are mostly lurkers. You need not
-wait for a response. Generally a lack of response can be taken as
-acceptance of the module name being proposed. Note by KS: If you want
-a quick response, be sure to ask if anybody actually reads the list.
-This is guaranteed to produce at least ten responses in rapid
-suggestion (none of which will respond to your proposal).</p>
-
+modules@perl.org isn't a mailing list, just an alias for the
+maintainers of the Perl 5 modules list. Please do not subscribe. Visit
+the archive instead.</p>
 
 <h3><a id="menu" name="menu"></a>Visit PAUSE</h3>
 
 <p>As soon as you have a password (see <a
 href="#registering">registering</a>) you are enabled to use some <a
-href="https://pause.kbx.de/pause/authenquery">forms to interact with
+href="https://pause.perl.org/pause/authenquery">forms to interact with
 the PAUSE database</a> (<a
-href="http://pause.kbx.de/pause/authenquery">Non-SSL version</a>). You
+href="http://pause.perl.org/pause/authenquery">Non-SSL version</a>). You
 can add files to your home directory, edit your name, email, and
 homepage address, delete your files, change your password on PAUSE,
 etc.</p>
 
 <p>If you haven't got a password yet or have forgotten it, please visit
-<a href="https://pause.kbx.de/pause/query?ACTION=mailpw"
->https://pause.kbx.de/pause/query?ACTION=mailpw</a> (<a
-href="http://pause.kbx.de/pause/query?ACTION=mailpw"
+<a href="https://pause.perl.org/pause/query?ACTION=mailpw"
+>https://pause.perl.org/pause/query?ACTION=mailpw</a> (<a
+href="http://pause.perl.org/pause/query?ACTION=mailpw"
 >Non-SSL version</a>) for further instructions.</p>
 
 <p>Please, whenever you exchange email with the maintainers of PAUSE,
@@ -165,27 +126,67 @@ impression of how things fit together. It usually boils down to
 
 <h3><a id="namespace" name="namespace">Register your namespace!</a></h3>
 
-<p><b>Please,</b> talk to <b>modules@perl.org</b> before you decide upon
-the namespace you're going to use for your module. Usually it's not
-considered the perl way to have beaurocratic conventions, but when it
-comes to namespace pollution, there is the need of coordination. Just
-like the InterNIC has to care for unique names for internet hosts,
-somebody has to (sort of) guarantee uniqueness, consistency, and
-sanity of module names. The <a
+<p><b>Please,</b> talk to other people (comp.lang.perl.modules,
+modules@perl.org or any mailing list that fits your problem domain)
+before you decide upon the namespace you're going to use for your
+module. Usually it's not considered the perl way to have beaurocratic
+conventions, but when it comes to namespace pollution, there is the
+need of coordination. Just like the InterNIC has to care for unique
+names for internet hosts, somebody has to (sort of) guarantee
+uniqueness, consistency, and sanity of module names. The <a
 href="00modlist.long.html">modulelist</a> is the place where all
 currently registered module names can be found and the email address
 <b>modules@perl.org</b> is an alias for a hand full of experienced
-volunteers who maintain the module list and give advice for the
-appropriate namespace for your modules.</p>
+volunteers who maintain the module list and--time permitting--try to
+give advice for the appropriate namespace for your modules.</p>
 
 <p>Please consider the namespace you're going to occupy with all due
 sensitivity. Discuss it in the appropriate fora. Read what the <a
 href="00modlist.long.html#2)Guidelinesfor">modulelist</a> has to say
-about this. Please pay special attention to the hints about 'cutesy'
-names. Reading these sections carefully will help you and us to
+about this. Pay special attention to the hints about <i>cutesy
+names</i>. Reading these sections carefully will help you and us to
 greatly improve the usefulness of the CPAN and avoid cumbersome
 renaming at a later date.</p>
 
+<blockquote> Also: think carefully and honestly whether your module
+would be better off if it were integrated as an option into an already
+existing module. Sometimes it is for the best to put aside personal
+glory and join a collaborative effort: Perl itself is a good example
+of this. Contact the author of an existing module and ask whether your
+new features would fit into his framework. Even if you in the end
+decide to release the module as your very own, you really should know
+your 'competition', that is, know all the similar modules and the
+features they offer. Maybe you can learn from them, maybe you can help
+the users of your module better by giving them an overview about
+similar modules.</blockquote>
+
+<p>And please do consult the archives of modules@perl.org before you
+post a module proposal. The fulltext search capabilities of the
+archive should help you to find similar suggestions and contact
+addresses. modules@perl.org is low volume, so your search in the
+archive is quite targetted. <b>modules@perl.org</b> is not a mailing
+list. Please do not try to subscribe. We do not want to establish yet
+another perl mailing list. If we encounter hot topics, we move the
+discussion to the appropriate mailing lists. The traffic on
+<b>modules@perl.org</b> is archived at <a
+href="http://www.xray.mpe.mpg.de/mailing-lists/modules/">http://www.xray.mpe.mpg.de/mailing-lists/modules/</a>.
+The module list maintainers themselves are mostly
+lurkers. You need not wait for a response. Generally a lack of
+response can be taken as acceptance of the module name being
+proposed.</p>
+
+<p>When you're done with all your preparations, considerations, and
+investigations, visit the PAUSE and fill in the form for a new module
+namespace. Take your time filling in the rationale of the module
+proposal. Consider, your form will be posted to modules@perl.org too,
+so other developers will probably stumble over this description many
+years later. The better the decription, the better the chances that
+your module will actually be used.</p>
+
+<p>You need not wait for approval. You can upload anytime, even before
+you fill in the form. Uploading and registering are only loosely
+coupled.</p>
+
 <p>The indexes that are maintained automatically on CPAN all double check
 if the module names that are used in the uploaded packages are
 registered. The indexer unwraps all packages and scans the source code
@@ -194,23 +195,8 @@ the <b>risk of being ignored</b> by the index generator if you do not
 talk to the modulelist maintainers about the namespace you are
 using.</p>
 
-<p><b>modules@perl.org</b> is not a mailing list. Please do not try to
-subscribe. We do not want to establish yet another perl mailing list.
-If we encounter hot topics, we move the discussion to the appropriate
-mailing lists. The traffic on <b>modules@perl.org</b> is archived at
-<a
-href="http://www.rosat.mpe-garching.mpg.de/mailing-lists/modules/">http://www.xray.mpe.mpg.de/mailing-lists/modules/</a>.</p>
-
-<p> Please consult these archives before you post a module proposal.
-The fulltext search capabilities of the archive should help you to
-find similar suggestions and contact addresses.
-<b>modules@perl.org</b> is low volume, so your search in the archive
-is quite targetted. The module list maintainers themselves are mostly
-lurkers. You need not wait for a response. Generally a lack of
-response can be taken as acceptance of the module name being proposed.</p>
-
-
-<h3><a id="conventions" name="conventions">Other conventions you should know about</a></h3>
+<h3><a id="conventions" name="conventions">Other conventions you
+should know about</a></h3>
 
 <p>Do not upload the <b>READMEs</b> that are integrated in your distribution
 files. PAUSE is designed to take care of unwrappig your file with tar
@@ -225,8 +211,8 @@ a few hours after your upload.</p>
 <b><code>$VERSION</code></b> variable that conforms to the CPAN rules, i.e.
 the complete computation of $VERSION must take place on the one first
 line within the module that assigns to it. You can test if this is the
-case by running <br /><code>perl -MExtUtils::MakeMaker -le
-'print MM->parse_version(shift)' filename</code><br />
+case by running <blockquote><code>perl -MExtUtils::MakeMaker -le 
+'print MM->parse_version(shift)' 'file'</code></blockquote>
 on the filenames in question. The CPAN indexer will run this code
 within a Safe compartement.</p>
 
@@ -277,11 +263,11 @@ the <a href="#namespace">standard approval procedure</a>.
 <tr>
 <td colspan="5" align="center">
 
-On a more or less regular basis, the Module List is published on
-USENET in the newsgroups comp.lang.perl.modules, comp.answers, and
-news.answers. Simultaneously an <a href="00modlist.long.html">HTML
-version</a> and a <a href="03modlist.data.gz">machine readable
-representation</a> are uploaded to CPAN.
+On a more or less regular basis, the Module List in <a
+href="00modlist.long.html">HTML</a> and <a
+href="00modlist.long.txt.gz">TXT</a> format and a <a
+href="03modlist.data.gz">machine readable representation</a> are
+uploaded to CPAN.
 
 </td>
 <td colspan="7" align="center">
@@ -359,49 +345,49 @@ keep up the http server for the time being. So if you have
 difficulties accessing https, you can always fall back to http, but
 using SSL greatly improves your and PAUSE's security.</p>
 
-<p>PAUSE's private key is not registered with any certificate authority,
-so when you access the SSL channel for the first time, your browser
-will most likely complain that it <i>does not recognize the authority
-who signed its Certificate</i>. You can safely ignore this error. When
-you verify the fingerprint to be
-B4:96:CD:65:5C:B4:2F:2A:EC:D6:5E:5F:FC:D0:8E:0B, then you know you're
-talking to the real PAUSE.</p>
+<p>PAUSE's private key is not registered with any certificate
+authority, so when you access the SSL channel for the first time, your
+browser will most likely complain that it <i>does not recognize the
+authority who signed its Certificate</i>. You can ignore this caveat.
+The fingerprint of the self-signed certificate that expires on
+2003-05-20 is
+<code>0E:E2:E9:AC:81:D0:DC:80:81:25:E5:BA:66:32:33:E5</code></p>
 
 <h3><a id="credits" name="credits"></a>Software</h3>
 
-<p>The software running PAUSE consists of a database, which is driven by
-<a href="http://www.tcx.se/">mysql</a> and a <a
+<p>The software running PAUSE consists of a database, which is driven
+by <a href="http://www.tcx.se/">mysql</a> and a <a
 href="http://perl.apache.org">mod_perl</a> server with <a
-href="ftp://ftp.ox.ac.uk/pub/crypto/SSL/">SSL</a>. Besides many of the
-perl standard modules like CGI, Data::Dumper, Text::Wrap, File,
+href="ftp://ftp.ox.ac.uk/pub/crypto/SSL/">Ben-SSL</a>. Besides many of
+the perl standard modules like CGI, Data::Dumper, Text::Wrap, File,
 Directory, and IO modules, PAUSE itself uses lots of modules from the
 CPAN. For a complete list, feel free to visit <a
-href="http://pause.kbx.de/perl-status">http://pause.kbx.de/perl-status</a>.
+href="http://pause.perl.org/perl-status">http://pause.perl.org/perl-status</a>.
 Also a lot of work is done by the mirror program by Lee McLoughlin,
 available from the CPAN scripts/ftpstuff directory.</p>
 
 <p>Thanks to all of you for your great contributions!</p>
 
-<hr /> Contact <a href="mailto:koenig@pause.kbx.de">Andreas
+<hr /> Contact <a href="mailto:andreas.koenig@anima.de">Andreas
 K&ouml;nig</a> for any questions.
 <pre>
-<a id="pubkey" name="pubkey"></a>PGP public key for Andreas Koenig &lt;koenig@franz.ww.TU-Berlin.DE&gt;
+<a id="pubkey" name="pubkey"></a>PGP public key for Andreas Koenig &lt;andreas.koenig@anima.de&gt;
 -----BEGIN PGP PUBLIC KEY BLOCK-----
-Version: 2.6.2i
-Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
-
-mQCNAy/cHRcAAAEEANwnl+iKMmChV2bclGabDurm29HHOSSc6cB3jDLC0AzOHeai
-KpWaht05TCh95Bdx19YcfCm+NEd3FK0O1dcitufpNR7QJUvYVuN1AscLoYBmU8BW
-ioIPsdjAj3IVdjwhS5loTyjoIT2/OWC2FxCUV5rSyAo/mQQ9knx7PGaUl9ctAAUT
-tC1BbmRyZWFzIEtvZW5pZyA8a29lbmlnQGZyYW56Lnd3LlRVLUJlcmxpbi5ERT6J
-AJUCBRAwcO+wYOb8KOlZZVUBAVB1BAC1B/zPYWODvdOfEdLtdtqhR/H9ULyaVmOM
-rS1TNpDdnQzzx8jzufHPJbWaY1XbOl3XYJy59lGUGN6rYKj91sDgvSmEL1ojHWmP
-+Ox/FU9ZuNVvwz+qYbw031JLDKX6JWyby6kr742SDX/2Cw99knzh3VpdCUwZYjAq
-DZDrUwUx+4kAlQMFEDBw/xB8ezxmlJfXLQEBpcED/0vP1gyeKTGZGZTg94OzdWlg
-1fRjoVIXqwc10Fce6HnodJ5ScTiVaspA/ppq0p0eKoArPmGxy6ZjX3urr4PtdRck
-5HWf0p8K1pBJ65P7x+vOlN3/v9L9kxtUjHxn/4U0X+xAhOlYQuz3FIdnGz7EDnaK
-6z2ss1hdSC1mTrAF4JME
-=zlTu
+Version: 2.6.3ia
+Comment: Processed by Mailcrypt 3.5.5, an Emacs/PGP interface
+
+mQCNAzrKR68AAAEEAL2GKFOe+hJ+LWhCmPT4xc7Aw3k1/vWwwQXjl79tbr7ITLBW
+c9UhUvlF6cw0CDvar0GzTPHFvSjgx668AQPZv2zSR7uFwwdwYHcysrbMN+iqMmpM
+x713rltz+2WpKhGwCbUrVqgRPn9UAcesWwat48oMmkztA51LmKxNj5KflPz1AAUR
+tChBbmRyZWFzIEtvZW5pZyA8YW5kcmVhcy5rb2VuaWdAYW5pbWEuZGU+iQCVAwUQ
+OspKfnx7PGaUl9ctAQGmewP+M0QpAwbeyiDCWW2EY/Y2rQyUafGbjEr7w9r1nUHk
+oDRqJQPv8XECQQbRhO7JKQmwJA5Jladx4l9kzwuLxZ7/bKj/3fGDhllYByQzaTaT
+nPogP5pa7SwFvlcgwLZ0P2dIc3dwom80bvnmG2QcrEx5xy2I2ZhouCf1Xy/xKZr5
+dweJAJUDBRA6ykevrE2Pkp+U/PUBAWbrBACfgcD+T8W/r5AtLk37ZFL4OtCmYoUs
+cDz6owiBgVqQmAH8lvduA8iecd0pbdDaeSeG9QGRCHFjTkRlzig/saM8xKY3FzDD
+ghrlgeF+lyWcnghsO5PByuPFqBUpcM62yVZJQZwAf27iiBTe+hivbuFEvfKtyYoP
+jG/Dku2EqTXnsg==
+=YKGX
 -----END PGP PUBLIC KEY BLOCK-----
 </pre>
 </body>