I agree on the need of this improvement.
If such a feature is to be implemented, though, perhaps it should take into account other needs as well, such as the case of a node considered for the wrong reason.
Examples:
- node id XXXX has a duplicate YYYY. I submit node YYYY for deletion and in the meantime another monk submits node XXXX for the same reason.
-
Node XXXX has been formatted badly, and an unclosed tag has caused a mangling of the node. Somebody submits it for deletion, because the text displayed looks trollish.
- Node XXXX asks something about a dark acronym , and somebody, thinking it is an Off Topic, submits it for deletion.
- Node XXXX is submitted for Tutorial. It looks good, also because it is talking about something less than ordinary. However, one of the replies points out that the code shown is completely wrong and misleading. Many people evaluating this node in Nodes to consider don't see the reply and vote "edit."
In all these cases, editing the consideration field would not solve the problem.
What should address all these issues, while keeping the spirit of the Monastery, would be the capability of adding a comment to the initial consideration comment.
If this feature is implemented, the consideration input box doesn't disappear after submission, and other monks can add their own comments to address the problem correctly.
A stream of comments for case (1) would be:
Node YYYY
[SomeMonk] DELETE - dup of [XXXX]
[WiserMonk] DON'T DELETE - [XXXX] has no replies. This one does.
for case (2):
Node XXXX
[SomeMonk] DELETE - no contents
[WiserMonk] KEEP and EDIT - fix <NASTY> tags
for case (3):
Node XXXX
[SomeMonk] DELETE - Not a Perl Question. We don't do XYZ!
[WiserMonk] KEEP - [CPAN://XYZ] is a Perl module
for case (4):
Node XXXX
[SomeMonk] EDIT - That's great! Promote to Tutorials
[WiserMonk] KEEP - Look at [XXXYY]. The code is a mess.
I believe that such a change would improve the quality of the whole consideration process.
-
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.