CZ Talk:Moderator Policy: Difference between revisions
imported>Howard C. Berkowitz (Where should certain policies be clarified?) |
imported>D. Matt Innis (→Behavioral vs. editorial vs. blurred: first impression) |
||
Line 9: | Line 9: | ||
[[User:Howard C. Berkowitz|Howard C. Berkowitz]] 03:29, 16 January 2009 (UTC) | [[User:Howard C. Berkowitz|Howard C. Berkowitz]] 03:29, 16 January 2009 (UTC) | ||
''*When moving or splitting articles, using subpages, etc., since clusters do not work in userspace, it can be very helpful to have a temporary hold on editing while the cluster features are being tested. This is not in any way intended to be a restriction on what can or cannot be in the content, but simply a means of change control where technical complexities exist. I could see asking, before the action, for a brief period of restriction on what are mostly mechanical processes of editing, as opposed to content of editing.'' | |||
:Hi Howard, my gut reaction to this is that I really hate to stop any form of collaboration while the creative juices are flowing. In other words, I think we should do anything we can to solve the problem *before* we put a hold on an article, though I certainly wouldn't rule out doing it if we had to. [[User:D. Matt Innis|D. Matt Innis]] 03:46, 16 January 2009 (UTC) |
Revision as of 21:46, 15 January 2009
Behavioral vs. editorial vs. blurred
As we've discusssed in various areas, there are a number of areas where there is some question if a matter if is behavioral or editorial. Some really do straddle the line. What is the best place to discuss these, especially if they may be issues that are relatively pressing in progressing?
Think of these as samples:
- When moving or splitting articles, using subpages, etc., since clusters do not work in userspace, it can be very helpful to have a temporary hold on editing while the cluster features are being tested. This is not in any way intended to be a restriction on what can or cannot be in the content, but simply a means of change control where technical complexities exist. I could see asking, before the action, for a brief period of restriction on what are mostly mechanical processes of editing, as opposed to content of editing.
- Certain markup features, such as text boxes and tables, are very easy to break during early article development with lots of collaborative editing. Tables and columns may be the only way to present numerical material and the like, but text boxes may be a visual flourish that interferes with collaboration.
- Who has authority over workgroup assignments? What is the real meaning of the metadata field "editors asked to check categories"?
- Where is the line between editor rulings of content fact, and the appropriateness of topics or means of argument in an article? Who and when can sourcing be challenged (and no, I'm not talking about Other Place style templates everywhere)?
Howard C. Berkowitz 03:29, 16 January 2009 (UTC)
*When moving or splitting articles, using subpages, etc., since clusters do not work in userspace, it can be very helpful to have a temporary hold on editing while the cluster features are being tested. This is not in any way intended to be a restriction on what can or cannot be in the content, but simply a means of change control where technical complexities exist. I could see asking, before the action, for a brief period of restriction on what are mostly mechanical processes of editing, as opposed to content of editing.
- Hi Howard, my gut reaction to this is that I really hate to stop any form of collaboration while the creative juices are flowing. In other words, I think we should do anything we can to solve the problem *before* we put a hold on an article, though I certainly wouldn't rule out doing it if we had to. D. Matt Innis 03:46, 16 January 2009 (UTC)