Well in my eyes it does address module abandonment and disputed functionality quite well -- it turns them into a technical problem, with a technical solution -- change the authority.
Maybe you're too immune to the current situation. Now users have to pick between modules of identical APIs, rather than identical modules with different authorities. I'm probably going to end of forking POE within the next month. I'm not sure what I'm going to call it, but I'm sure it will confuse people more than seeing POE<cpan:rcaputo> and POE<cpan:ecarroll>
-
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.
|
