Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Re: How to complain about changes to a module? (And what good would it do?)

by moritz (Cardinal)
on Aug 28, 2008 at 12:17 UTC ( #707460=note: print w/replies, xml ) Need Help??


in reply to How to complain about changes to a module? (And what good would it do?)

I assume that you already asked the author politely to revert his changes. If not, that's the first step (and maybe the only), and you don't need to read on.

unnecessary;

Your chances are not good at this one: if the author thought the cange was unnecessary, he wouldn't have done it.

go against both its design philospophy and purpose;

That's something you can try to come up with; if you do it politely and well reasoned, maybe you can convince the author. Politely implies...

introduce dependancies upon other modules that same author has already ruined.

... not mentioning that you think the author ruined anything. Even it might be the case, you won't make any friends by saying it.

If the author introduced another dependency, you can be fairly sure that he didn't think it was unnecessary, so most certainly you lost on your first point already.

What can be done about it?

Either cope with your frustration and don't do anything about it, or fork the module.

To whom does one complain?

To good friends in real life, or your significant other, if you happen to have one. Don't complain to the module author, it will make things worse.

And would it do any good?

No. Technical discussions might be helpful, but complaints are most certainly not. It only helps you to deal with your frustration, thus if you complain to anybody, make sure it's somebody who doesn't have any influence on the situation, and just listens.

What other options are open to curtail or rollback such changes.

Fork the module. Or keep using a patched version. Or take over the module, if the author agrees.


I can very much understand your situation. We geeks tend to have strong opinions on technical matters, and the more we are familiar with them, the stronger they are. As a user of a good piece of software it hurts to see it being crippled, and as an author you feel pretty sure that you're improving it. Unfortunately there's no silver bullet solution.

  • Comment on Re: How to complain about changes to a module? (And what good would it do?)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://707460]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (8)
As of 2021-02-27 22:45 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?