comment on

You know, I am not a machine with a hard coded set of rules, I am a person, am so my thinking and feeling are fuzzy...

If somebody releases an unauthorized version of my modules without first trying to communice with me in any way, yes, I probably would get upset.

If somebody releases an unauthorized version of my modules after I have failed to reply to several mails from him, I would probably feel more guilty than upset.

But nevertheless, I still think that in that later case, he should had written me an email volunteering to take over the module (even if for a single release) because even if I had failed to reply to his bug reports and patches, I still would be willing to collaborate with him to take out that new release and, this is the important thing, everybody will win.

In reply to Re^9: Fixing broken CPAN modules without author cooperation (years) by salva
in thread Fixing broken CPAN modules without author cooperation by cavac

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks