CZ:Proposals/Approval system for CZ: pages: Difference between revisions
imported>Warren Schudy |
imported>Stephen Ewen m (→Discussion) |
||
Line 39: | Line 39: | ||
:I can't see us ever wishing to approve any page unless there is a need to maintain a stable version of the page while changes or tried out on a Draft.[[User:Gareth Leng|Gareth Leng]] 03:57, 16 February 2008 (CST) | :I can't see us ever wishing to approve any page unless there is a need to maintain a stable version of the page while changes or tried out on a Draft.[[User:Gareth Leng|Gareth Leng]] 03:57, 16 February 2008 (CST) | ||
This is needed in a very major way, in my mind. [[User:Stephen Ewen|Stephen Ewen]] 02:40, 24 February 2008 (CST) | This is needed in a very major way, in my mind, just to prevent people from changing policy pages wily-nilly. [[User:Stephen Ewen|Stephen Ewen]] 02:40, 24 February 2008 (CST) | ||
The approving body of a rules page should be the one that is authorized to make changes to the rules documented therein. Content and editor policy pages should be approved by the editorial council and other pages by the executive council. I think something along these lines is worth a try. See [http://forum.citizendium.org/index.php/topic,1563 this forum thread] for an example of the slightly awkward and informal approval process for policy pages currently in place. [[User:Warren Schudy|Warren Schudy]] 11:37, 24 February 2008 (CST) | The approving body of a rules page should be the one that is authorized to make changes to the rules documented therein. Content and editor policy pages should be approved by the editorial council and other pages by the executive council. I think something along these lines is worth a try. See [http://forum.citizendium.org/index.php/topic,1563 this forum thread] for an example of the slightly awkward and informal approval process for policy pages currently in place. [[User:Warren Schudy|Warren Schudy]] 11:37, 24 February 2008 (CST) | ||
{{Proposals navigation}} | {{Proposals navigation}} |
Revision as of 16:26, 24 February 2008
This proposal has been assigned to the Executive Committee, and is now in the Executive proposals queue.
This is a reasonably important proposal and should be generally vetted by the community, not just the Executive Committee. Therefore, there must be broad (if not unanimous) support for the proposal before it moves on to the Executive Committee.
Complete explanation
I think we just extend the Approval/Draft system to all CZ pages. They become approved once approved by executive committee members, and then a draft is open to revise. I think an approved version should remain editable for minor things without re-approval. But there will be two versions, a formally approved version, and an evolving draft alternative.
Proposed Approval process for CZ: pages.
A member of the executive committee places a "ToApprove" template on the article's talk page. That template will be marked with a date, usually several days to a week from the date that it is placed.
If the approval template remains there, approval will occur on that date. Meanwhile, discussion and edits continue. Edits at this stage should be made only by executive committee members, involved authors and relevant parties (e.g. constables). Other members of Citizendium should make recommendations and criticisms on the talk page.
If another member of the executive committee objects to approval, then the template is removed by this member, who explains why on the talk page.
If the nominator notes that the discussion on the talk page that has occurred since the nomination for approval brings up important objections, then he or she may delay the date for approval to allow for work to continue. The nominator may also change the version nominated for approval on the "to approve" template to an updated draft.
Unless the template is removed, on the designated date, a sysop then freezes the approved version of the article under an Approved template. At that freeze, a draft form of the article is generated. This draft is open to edits as are all unapproved articles on the wiki.
After approval, copyediting and minor changes may be performed by any member of the executive committee with the help of the approvals editor. This may occur at any time.
Who may approve:
For any CZ page, only members of the executive committee may approve.
Reasoning
Below is copied the discussion from an earlier, discarded proposal (See [[CZ:Proposals > CZ Community pages should be revised for simplicity]]), that led to the present proposal.
That proposal was justified thus: "....Part of what is keeping our "elitism shield" up is that many (if not all) of the community pages are overly complex. A campaign to heavily review and edit the pages will give us leaner, easy-to-comprehend documentation and improve our external appearance."
Implementation
As far as I can see this just needs Executive Committee endorsement.
Discussion
See CZ:Proposals/CZ Community pages should be revised for simplicity
I assume that this approval system is only proposed for CZ: pages with rules, and not for pages like CZ:Monthly Write-a-Thon or indeed this page itself. -- Jitse Niesen 13:42, 15 February 2008 (CST)
- I can't see us ever wishing to approve any page unless there is a need to maintain a stable version of the page while changes or tried out on a Draft.Gareth Leng 03:57, 16 February 2008 (CST)
This is needed in a very major way, in my mind, just to prevent people from changing policy pages wily-nilly. Stephen Ewen 02:40, 24 February 2008 (CST)
The approving body of a rules page should be the one that is authorized to make changes to the rules documented therein. Content and editor policy pages should be approved by the editorial council and other pages by the executive council. I think something along these lines is worth a try. See this forum thread for an example of the slightly awkward and informal approval process for policy pages currently in place. Warren Schudy 11:37, 24 February 2008 (CST)
Proposals System Navigation (advanced users only) | |
|
Proposal lists (some planned pages are still blank):
|