John Adams wrote:
This may not quite be an advocacy question, but it's the closest category I can come up with.
I suppose there are better mailing lists for this, but it's not an inflamatory topic, so what?
I have two projects I'm ready to start putting onto CPAN--what is the ettiquette of creating a namespace? The projects want a top-level namespace, but I'm hesitant to just carve out the space on my own.
First thing you should do is read the 'perlnewmod', 'perlmod', and all other documents that come with Perl that relate to modules and CPAN. Forgive me if you did, but those docs should give you a general idea on how things work. Next would be searching on the main cpan and pause sites for guidelines. (There aren't actually *formal* guidelines on how to choose a namespace, but quite a bit of help. If I recall correctly, that is.)
I daresay that unless you are doing something that's pretty unrelated to anything on CPAN, you're better off trying hard to find an existing namespace to extend.
Now, please don't let you be put off your willingness to contribute your work to CPAN by this. (Is that grammar correct? I have a succinct feeling the previous sentence doesn't parse right.)
Steffen
--
sub'_{q} tsuJ}}_();sub's{seek+DATA,0,0}sub'p{print&_}sub'r{reverse$_[0]}
@_=(('')x2,split" ",<DATA>);s!!&s,$_=<DATA>;s/}.*?}/$_[$s+1]/
if$s;s/(}.*?})/r$1/e;eval$_;p,[EMAIL PROTECTED];
__DATA__
} rehtona} } lreP} },rekcah}