comment on

I recognize you here and I respect you, but without this thread I might not have made the connection between ECARROLL and Evan Carroll. I would not have placed rcaputo at all. I know I'm poor at tracking attributions but I don't see how a name like POE<cpan:ecarroll> is more informative than POE_Fast or POE_Portable.

Yes, I am relatively unaffected by any current namespace disputes. I am further removed from CPAN than you. For a decade or more, I used Perl for small jobs and when I discovered CPAN, the task, as a rookie, of finding a module to do some task lacked any immediate payback. It can be easier to build a wheel than to find one.

I am further removed from CPAN than you; I don't pretend to know the intent or workings of authorities. I seek education:

How do I as user determine which POE is the POE I've heard about?
Should I view the existence/publishing of both POE<cpan:rcaputo> and POE<cpan:ecarroll> as proof of some disagreement between the two authors?
If not, how do I know which is the ephemeral package?
If yes, how has the social problem been solved?
If these authorities are of equal status, how should I not view this as the demolition of namespaces on CPAN? Update: My use of namespace here is vague, I really am referring to branding or product identification.

I do realize that more toolchain learning issues will deter people from contributing to CPAN. That is bad but does allow a smaller group the chance of greater cooperative action.

Be well,
rir

In reply to Re^6: JETTERO tries to take over Net::IMAP::Simple on PAUSE by rir
in thread JETTERO tries to take over Net::IMAP::Simple on PAUSE by jettero

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks