It is not surprising that the CPAN admins are slow to declare code abandoned and then seize it.
It is not surprising that many choose not to contribute once they realize that contributing requires that "admins (slowly) declare code abandoned and then seize it". You nicely summarize the problem. Thank you.
This is confused. [....] If you have the right, you can develop a codebase where, how, and with whom you like, then you can release it on CPAN.
That seems to me to completely miss the point. Creation as the act of a single person is so very common. Maintenance is where collaboration is most useful. The ability to collaborate before submitting to the rules of the CPAN services is certainly not the problem, for multiple reasons. The need to thwart the roadblocks of CPAN services just to be able to collaborate should be seen as a problem, but, yes, we shall work around that problem.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||