CPAN Name Squatting

That was taken by MARCEL but the module is missing. I guess MARCEL deleted Attribute::Memoize in favor of Attribute::Util which has the same functionality. But I don't like the idea of grab-bagging of multiple Attribute handlers in a single module so I mailed him what he wants to do with it. The mail was sent on April 8th and I got no reponse since then.

Case: Crypt::Camellia

That module does Camellia cipher for Crypt::CBC. The algorithm became open source only recently (April 13th) so it is almost impossible that the name space be registered by someone else. But it is registered by JCDUQUE. It is registered as RcdOg but once again the module itself is missing (naturally). Since JCDUQUE has registered Many Crypt:: modules, he did so assuming it will soon be available.

I now have a very strong doubt of module registration system. Do we really need that? And who and how the registration be processed is in the haze. I have requested to register Encode and Jcode before. Encode is even in core but those requests were simply ignored.

http://search.cpan.org/ seems to be taking more practical approach. Just index whatever does REALLY exist. So Attribute::Memoize and Crypt::Camellia belongs to me from its point of view. But once you fire up CPAN shell, it's registration that has te precedence.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

CPAN, by design, wants people to upload things at the earliest time possible, even before stuff works in some cases. Get it out, available, and hackable by the community.The gateway to that is the Perl Authors Upload Server (PAUSE). You just need a CPAN ID, which is pretty easy to get. You can then upload any module that you like, including ones with names already taken.

On top of that is the PAUSE indexer, which makes the CPAN meta files. It knows who uploaded what and which CPAN IDs get first right to a mo

Still, just because it isn't reasonable doesn't mean he has a point...

I'm not sure if there are any obvious steps we could take to make the situation any better though.

God knows I'd hate to have some web application or something queuing module requests. That would get out of hand pretty quickly. At least when something falls through the cracks on modules@ currently it doesn't hang around to slow things down later.

His complaint would be more valid (but not really) three years ago. Even then, he could have tracked down a PAUSE admin and made a more direct plea. It doesn't look like he tried anything other than submitting the module registration form, so I don't think he really tried hard enough to make a statement about PAUSE other than his module wasn't registered.

Guilty as charged; for the record, I've now made Dan co-maintainer of the Attribute::Memoize and Attribute::Util namespaces. Maybe I should actually give up the Attribute::Memoize namespace, since I've got no module of that name anymore...