Are you claiming you actually got flamed?

Well I didnt rate it as a flaming. It was more like "yeah so what you dont like the decision. Thats the decision, its not going to change get over it." It was pretty clear that public opinion, or maintaining backward compatibility was not a priority. As for bug reports, i got tired of sending them out after the first couple were totally ignored. The impression I got was the attitude was like "we dont know who you are and we dont care what you think and oh btw getting it running on Win32 isn't a priority for us." Which essentially lost the efforts of at least one (somewhat) competent Win32 Perl Programmer who normally is inclined to help and to post patches.

Maybe you shouldn't start by accusing the people working on it of being arrogant

Well, I think their conduct and approach to Module::Build has been arrogant. I'm sorry if that upsets you, or that you feel that is unwarranted criticism, but the fact is that is the perception of a lot of people I've chatted with on this subject. Maybe what needs to happen is that the M::B crew actually listens to people, and perhaps even solicits their opinions and thoughts. If the ambition of this project is to change the working processes of tens of thousands of programmers dont you think a little community interfacing should occur?

Let me give you an example, ive seen you post a numer of "defend the module" posts. Have you ever posted a Meditation asking for the communities position on the changes being contemplated by M::B? Have you posted postion documents on CLPM, P5P and the other community locuses? Ive not seen any. Has anybody every asked the folks outside the M::B and CPANPLUS cliques how they feel about things? I bet not because I bet if it were put up to a vote there never would be another Build.pl uploaded to CPAN.

Basically the impression of M::B is: It produces distributions that are unbuildable from CPAN. It doesnt (or didnt) run on Win32. The people involved don't seem to listen unless your name is widely known in the community already.

If you are in a position to change these things then do so and youll see a lot of folks who dis M::B turn into Cheerleaders. Come and tell us we are wacko because we raise issues that are valid in our eyes and you wont win many converts.

Cheers, and respect.


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi

In reply to Re: Re: Re: Re: Re: Module::Build and the PPM by demerphq
in thread Module::Build and the PPM by barbie

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.