what does it take to get a module accepted by CPAN?

bkchapin has asked for the wisdom of the Perl Monks concerning the following question:

I made my first submission to CPAN last week. I submitted an update to a module, DBIx::Perform. It's sitting in my upload directory. How does it go from there to something that can be found in CPAN?

I have no feedback. I can think of lots of reasons why this module isn't in the search. Someone clue me in?

Hasn't been long enough.
CPAN doesn't index updates, or particular sorts of updates.
CPAN doesn't work that way.
The original module is by another author, and it requires his permission. Should've called it by a new name?
It should've been submitted as tar.gz, not tar.bz2
It's broken in some way. Test scripts do not run, or it's not formatted correctly, or something is missing, causing some automatic process to reject it.

There are a lot of instructions to follow. Too many, really. Can't this submission process be a little friendlier and clearer? I suppose I missed something.

Comment on what does it take to get a module accepted by CPAN?

Replies are listed 'Best First'.
Re: what does it take to get a module accepted by CPAN? by Corion (Patriarch) on Aug 01, 2007 at 19:41 UTC
Normally, you get (three) mails from PAUSE and CPAN about the progress of your submission. As for DBIx::Perform, there already is such a module, so maybe the name clash is part of the problem. I normally use Module::Release to handle the nitty-gritty of running the tests, updating cvs and then uploading to PAUSE. Once the stuff is on PAUSE, it's a matter of minutes until it's moved into the CPAN and then it takes maybe a day until it shows up via CPAN. So, likely, something went wrong with your upload. Uploading as `.tar.gz` is the common way as `bzip2` is not available everywhere that Perl is, at least not by default. You should have given the module a new name or requested co-maintainership from the original author - that shouldn't prevent search.cpan.org from indexing your module, but it would have "UNAUTHORIZED RELEASE" in big red letters besides it. Other than that, the PAUSE/CPAN process is pretty lenient.	[reply]
Re: what does it take to get a module accepted by CPAN? by Joost (Canon) on Aug 01, 2007 at 19:52 UTC
http://search.cpan.org usually indexes new releases within a day, and AFAIK new releases get published even if no automated system manages to run the tests. If you haven't received any clarifying emails from pause, I'd guess your problem is 4. - you've uploaded a module to a registered namespace and the registrar hasn't (yet) approved your addition. Have you contacted the original author? "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^2: what does it take to get a module accepted by CPAN? by bkchapin (Acolyte) on Aug 01, 2007 at 20:03 UTC
I have tried to contact the original author, this Eric C. Weaver, at the email address given in the docs. No response. If his email address is still valid, I think it rather likely my emails were tagged as spam at his end, and silently discarded.	[reply]
Re^3: what does it take to get a module accepted by CPAN? by Corion (Patriarch) on Aug 01, 2007 at 20:13 UTC
Also see perlfaq candidate: "How do I adopt an abandoned module ? "	[reply]
Re: what does it take to get a module accepted by CPAN? by spatterson (Pilgrim) on Aug 02, 2007 at 16:15 UTC
CPAN will only update a module if the version number you are uploading is greater than the version of that module on CPAN. just another cpan module author	[reply]