I'm always glad to see some one applying a bit of JFDI rather than having interminable discussions about things. But as a module author/maintainer, this puts me in a bit of a spot - it's probably easier just quote what I said when asked about this somewhere else:
I can't see what niche
this fills: if there are bugs in a module to report then the author will
probably have indicated where these should go, either to
http://rt.cpan.org , to a mailling list, direct to the author or
whatever.
As a module author and/or maintainer I don't want to have to monitor
another site to pick up support issues anyway, but having it as a web
forum just makes it even more inconvenient - the majority of the free
time I have when I might be able to offer support to my modules is those
times when I will not be able to use a web site. I prefer e-mail.
There is no option on the site to opt your modules out of it - so if
this achieves some semi-official status, then people who have problems
with the modules I support are going to perceive that they are poorly
supported when they don't get a response.
/J\
-
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.
|