CPAN pause turnaround time

Hi,

I've submitted a request at PAUSE for registering a namespace for
a module I would like to implement. Can anyone tell me the
average turnaround time for a response. Does a negative response
mean no response?

From "perldoc perlnewmod":

ask the modules list at "modules@perl.org". Remember that this
is a closed list with a very long turn-around time - be
prepared to wait a good while for a response from them

Man oh man.. Can anyone please tell me their personal experience,
and what was the average turn-around time?

Thanks.

--
Rohan

Re: CPAN pause turnaround time

Also sprach Rohan R. Almeida:

> I've submitted a request at PAUSE for registering a namespace for
> a module I would like to implement. Can anyone tell me the
> average turnaround time for a response. Does a negative response
> mean no response?
>
> From "perldoc perlnewmod":
>
> ask the modules list at "modules@perl.org". Remember that this
> is a closed list with a very long turn-around time - be
> prepared to wait a good while for a response from them
>
> Man oh man.. Can anyone please tell me their personal experience,
> and what was the average turn-around time?

It might be anything, even indefinite. My experience is that requests
for namespace registrations frequently get dropped. I think this is
because there are not so many people who could carry out these
registrations and they are most probably busy doing other things as
well.

By and large I stopped worrying about registering modules. It serves
little purpose.

Tassilo
--
use bigint;
$n=714233503437702801613970263303373711390544118542200534375 65440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);

Re: CPAN pause turnaround time

Tassilo v. Parseval wrote:
>
> It might be anything, even indefinite. My experience is that requests
> for namespace registrations frequently get dropped. I think this is
> because there are not so many people who could carry out these
> registrations and they are most probably busy doing other things as
> well.
>
> By and large I stopped worrying about registering modules. It serves
> little purpose.
>

Thanks. Does this mean its ok to go ahead and code my module and
upload it to my CPAN space?

I do have a CPAN directory, but no modules yet. This is my first
time :-)

--
Rohan

Re: CPAN pause turnaround time

Rohan R. Almeida wrote:
> Tassilo v. Parseval wrote:
>> By and large I stopped worrying about registering modules. It serves
>> little purpose.
>
> Thanks. Does this mean its ok to go ahead and code my module and upload
> it to my CPAN space?

Registered or not, it's always a good idea to discuss its intended
purpose, namespace, etc. with others first. Maybe there is a natural
forum to do so considering the nature of the module; otherwise such
requests for comments are often posted here.

> I do have a CPAN directory, but no modules yet. This is my first time :-)

Good luck as a CPAN contributor. :)

--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl

Re: CPAN pause turnaround time

Also sprach Rohan R. Almeida:

> Tassilo v. Parseval wrote:
>>
>> It might be anything, even indefinite. My experience is that requests
>> for namespace registrations frequently get dropped. I think this is
>> because there are not so many people who could carry out these
>> registrations and they are most probably busy doing other things as
>> well.
>>
>> By and large I stopped worrying about registering modules. It serves
>> little purpose.
>>
>
> Thanks. Does this mean its ok to go ahead and code my module and
> upload it to my CPAN space?

Yes, by all means. The only thing that should be taken into account on
the first release of a new module is the namespace you choose. If
unsure, discussing it here is a good idea.

> I do have a CPAN directory, but no modules yet. This is my first
> time :-)

There's nothing to worry about. For a first-time submission your focus
should additionally be on making a module and tarball that adheres to
the CPAN standards. This is very easy with tools such as 'h2xs' or any
of the other module-skeleton creators that exist out there.

Tassilo
--
use bigint;
$n=714233503437702801613970263303373711390544118542200534375 65440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);

Re: CPAN pause turnaround time

"Tassilo v. Parseval" writes:

> By and large I stopped worrying about registering modules. It serves
> little purpose.

It depends on what you want. If you just want to upload your module,
no registration is required.

But if you want more people to use your module, the registration
process will help to:
- get a meaningful module name (so people won't skip your module
because its name does not ring a bell)
- use a name that will be consistent with other modules in the same
category (so people will consider your module when looking for a
solution for their problem)
- avoid future name clash by avoiding ambiguous names

A registered module will be visible through the browsing facility of
search.cpan.org. A non registered module will be visible only through
its distribution and the search engine.

If you want to register a module you must use PAUSE register facility.

Now, it's your call.

HTH

--
Dominique Dumont
"Delivering successful solutions requires giving people what they
need, not what they want." Kurt Bittner

Re: CPAN pause turnaround time

Also sprach Dominique Dumont:

> "Tassilo v. Parseval" writes:
>
>> By and large I stopped worrying about registering modules. It serves
>> little purpose.
>
> It depends on what you want. If you just want to upload your module,
> no registration is required.
>
> But if you want more people to use your module, the registration
> process will help to:
> - get a meaningful module name (so people won't skip your module
> because its name does not ring a bell)
> - use a name that will be consistent with other modules in the same
> category (so people will consider your module when looking for a
> solution for their problem)
> - avoid future name clash by avoiding ambiguous names

All of the above are generic rules for finding a name for a module. They
remain valid if no registration is intended.

> A registered module will be visible through the browsing facility of
> search.cpan.org. A non registered module will be visible only through
> its distribution and the search engine.

Which is what I suppose people most often use. I don't think I ever
browsed by category when a search didn't turn up anything suitable.

Tassilo
--
use bigint;
$n=714233503437702801613970263303373711390544118542200534375 65440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);