Submitting Your Module to CPAN

  The DSLIP code information:

  D: The development stage (i idea, c pre alpha, a alpha, b beta, 

R released, M mature, S standard, or ? unknown)

  S: The support level (n none, d developer, m mailing list, 

u comp.lang.perl.*, or ? unknown)

  L: The language used (p Perl, c C, + C++, o other, h hybrid, 

or ? unknown)

  I: The interface style (f functions, r references and ties, 

O object oriented, p pragma, h hybrid, n none, or ? unknown)

  P: The public license (p standard Perl, g GPL, l LGPL, b BSD, 

a Artistic, o open source, d distribution allowed, r restricted distri 

bution, n no license, or ? unknown)

  A short description of the module (up to 44 characters)

  A list of places where the module has been or will be discussed publicly

  A list of modules with similar functionality

  Rational

Although highly recommended, filling out this form isn't strictly necessary. 

Once you have a CPAN Author ID, you're able to upload any module you like so 

long as you're not uploading a module containing a package name that's already 

been registered to another author. However, by not registering your module name, 

you run the risk that someday the folks on modules@perl.org will decide to let 

another author register the namespace out from under you.

3

You should expect to receive a reply to your namespace registration request 

within three weeks. Or you might never receive a reply at all, which means accep 

tance of your registration request. Yes, really.

4

 As a result, it's common for experienced 

authors to register and upload in one fell swoop.

3. This has never happened, to my knowledge, but if it scares just one author into registering his 

or her namespace, then it was worth mentioning.

4. A search of the modules@perl.org archive will reveal that I had to learn this one the hard way. 

Learn from my mistake!

13

133

3