Another option is to complain to the old maintainer. The new maintainer may be more likely to listen to the old maintainer than a random user.
Also if the changes are egregious, then discussing specifics in public, ideally on a module-specific mailing list, but you could do ithere or on use.perl.org, may make more people aware of the issues around this new maintainer. That may help convince someone else to undertake the fork of the module that you don't want to handle, and it may make others aware that this isn't a good person to hand over modules to.
Of course that option comes with the significant cost that you'll be reasonably likely to create some bad blood. I've always had the attitude that I'm willing to risk create bad blood if I think the cause is important enough. (That said I set the bar fairly high, and work to avoid accidentally creating bad blood.) However lots of people disagree with me on that.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||