I think we're on the same page here. I'm proposing that a link on search.cpan.org would go to a node dedicated to the relevant CPAN distribution. That node would be 'owned' by an editor (kind of like dmoz categories) and would have structured content (XBEL could add real value here). The 'free-for-all' discussion would take the form of replies to that node - using the existing PM threads facility.
Ideally the system would have some 'smarts' eg: if a person followed a link to the node for Test::Case and no such node had been created, then they would be presented with the node for the Test namespace instead. From there they might find links to Test::Simple, Test::More, Test::Harness etc with commentary that suggested when you might use one over another. Restricting that commentary to fit into an XBEL <desc> element would probably be beneficial - if there's more to be said it deserves it's own node or offsite link.
I think having a dedicated node type that understands the 'standard' framework is important. Sure we could do all this with static HTML pages under personal accounts around the place, but if it ain't easy to maintain it won't succeed in the long term.
-
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.
|
