Politically - that's a tough call. Reason with the new maintainer? Bug the people who proposed or seconded the new maintainer?

Technically - as has been suggested, start your own branch from a known good version.

No one - Open Source is both blessed and cursed with Technical Anarchy. People are free to take the ball and run with it, based on their opinions and technical ability.

The best revenge is to fork the offending modules and champion their use. Natural selection will determine how successful each outcome is.

Sure - complaining is always better than saying nothing. But it's what happens after the complaining that's probably more important.

Like I said, there's a sense of anarchy when it comes to this area of software development. If the new maintainer's a lunatic, from your point of view, the answer is simple - fork the good code and move on from there.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

In reply to Re: How to complain about changes to a module? (And what good would it do?) by talexb
in thread How to complain about changes to a module? (And what good would it do?) by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.