comment on

Well said there perrin, I couldn't agree more.

I would also say to the OP, that I don't seem to remember many (heated or otherwise) perlmonks discussions where the soul of an entire framework was in the balance.. Discussing for the sake of it is one thing, trying to decide the fate of a project is another. Also, the Catalyst discussing was taking place realtime, on IRC, thus it would have been a lot harder to preview content, consider, post only when really sure, etc, since by that time the moment is gone.. Thus heated discussions would have been a lot more so.

Civility and mediated discussion is definitely a plus, in my book, when things are at stake. Having them closed/private just means people can discuss properly.

In reply to Re^2: Catalyst team change by castaway
in thread Catalyst team change by naChoZ

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.


Pathologically Eclectic Rubbish Lister
	PerlMonks