There are, I believe, more effective ways to recommend node title changes:
Consideration has become, I believe, the preferred way to suggest a new node title. Not only does this get the community's feedback in the form of votes, but it also gets the attention of people aware of the amount of work involved1 and experienced in the way we prefer to handle this sort of thing.
If you'd prefer a more private process, you can always /msg the editors group at large or any member of the group. I know I've tried to be very responsive to such requests and I believe the other janitors have, too.
Editor Requests is, of course, the oldest mechanism. However, the general sense I've gotten is that it's been generally superceded by the previously mentioned tools. I'm not sure this is "official," but it is an idea I've seen expressed in the ChatterBox on more than one occasion.
Personally, I would rather we used these tools instead making general posts in other areas. Why? Well, there really doen't seem to be a lot to discuss. Either the node needs to be retitled or it does not--and the Consideration process will help determine that. If the janitors have questions, they have areas where they can discuss things of this type.
If you're not sure, then perhaps it would be best to informally poll the Chatterbox or to privately /msg the author or one of the janitors
. That seems the most team-oriented approach, as well as the most respectful of the original monk's feelings, as it may have been an honest mistake. I know that I prefer people quietly tell me when I've screwed up and I suspect that other people appreciate it when the same level of respect is accorded to them.
Also, I should point out that you really should use the [id://] prefix tag to link to internal nodes, as the HREF anchor you're currently using will appear to log people out if they're using the .com URL instead of the .org. For additional details, please see What shortcuts can I use for linking to other information?--especially Footnote 1 (which leads to a complete description of the problem).
1 - Please be aware that I, personally, don't retitle nodes out of hand, though it certainly seems appropriate in this case. When I retitle nodes, I also take care to retitle each node in the thread. This is time consuming and takes much longer than simply adding <code> tags or performing other basic clean-up. But, that's my editorial style; there are others.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||