in reply to Multiple considering?

I think I've seen nodes that have been considered for several different reasons at different times -- it seems all that is needed to solve this 'problem' is a little patience. If a node is considered for reason A, and you think it should be considered for reason B, just wait until A is resolved and reconsider it for B (assuming the [id://janitors] don't detect the additional problem and resolve it on the fly). It has been surprising to me to find that there are significant differences in opinion regarding consideration -- not everyone thinks the same way, and I would tend to resist any short-circuiting of the consideration process.

Replies are listed 'Best First'.
Re^2: Multiple considering?
by blazar (Canon) on Oct 20, 2006 at 16:41 UTC
    It has been surprising to me to find that there are significant differences in opinion regarding consideration -- not everyone thinks the same way, and I would tend to resist any short-circuiting of the consideration process.

    Actually, I second that, and I was not thinking in my meditation of the short-circuiting aspect of the thing. Now that I do, I'm feeling even more half-hearted about it than when I wrote it. Still occasionally I feel the lack for a discussion/talk node of other nodes, in the same fashion as some wikis have talk pages about other pages, but then that's more connaturated to the very philosophy of wikis themselves. Also, patience is fine and all, but one thing is to want to contribute to The Monastery by considering a node, another thing is to have to remember to come back to that node after one consideration in course has been closed. Perhaps it should be permitted to consider a node also when one consideration is already open, to the effect of creating a queue of considerations for that node, which however should happen rarely enough. Of course, were this to happen, it should be left to the consciousness of the users: for example it shouldn't be a means to start arguments in the vein of "no, retitle it like thus" and so on. It should be a feature to be used to track only truely different issues with the same node...