CZ:Approval Process: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Larry Sanger
imported>David Tribe
No edit summary
Line 107: Line 107:
== Revoking approval ==
== Revoking approval ==


== Approving another version ==
== Re-approving revisions to approved articles ==
The process of approving another version is in its essentials the same as for the first version, but as the draft page now exists, a mode of operating needs to be established to minimize confusion.


A suggested approach is to continue all edit discussions on the Foo/draft talk page, and provide a section at the top of that talk page for the approval templates of the sucessive versions, which can be reffered to in the text of the talk page as V1.1, V1.2 etc.
Re-approval is the process of approving the replacement to and approved article. These replacements are called versions (XYX version 1.1 1.2 and so on) for clarity here.
 
The process of re-approving a revision to an an approved article is in its essentials the same as for the first version, but as two article pages (approved and draft page now exist), a mode of operation needs to be established to minimize confusion.
 
A suggested approach is to continue all edit discussions leading to re-approval  on the XYZ/draft talk page, and provide a section at the top of that talk page for the approval templates of the sucessive versions, which can be referred to in the text of the talk page as V1.1, V1.2 etc.


e.g.
e.g.


==Version record area (on XYZ/draft talk)==
==Article re-approval and version record area==
====Reserved for a log of Approved XYZ article revisions Approval events and their formal approval templates====
====Reserved for a log of re-approval of XYZ article revision events and template records==== templates====


====Version 1.1 approval events====
====Version 1.1 approval events====
Line 128: Line 131:


----
----
Annotate the XYZ talk page to the effect that editing discussion are occuring on the XYZ/draft page.
Annotate the top of XYZ talk page to the effect that editing discussions on article revisions are continuing on the XYZ/draft page.


It will be necessary for a sysop to transfer markup text to the protected main page to create a new approved version ( i.e. V1.1) and at such time annotate such save events with approval version and source (permanent link are at the top of XYZ/draft talk) descriptions to clarify the source of the text.
It will be necessary for a sysop to transfer markup text to the protected main page to create a new approved version ( i.e. V1.1) by code copy, paste and save, and at such time annotate such re-approval save events with the approval version (e.g. V1.2 )and source of code ("permanent links to source code are at the top of XYZ/draft talk, commented out") descriptions to clarify the source of the text. This article re-approval actioning sysop should never be the user or users involved in proposing the re-approval, or having a substantive role in the particular article editing or authorship process. An exception may be correction of glaring minor errors of layout evidentduring the re-approved.

Revision as of 15:57, 28 January 2007

Overview

Here, in broad strokes, is how the approval process goes:

  1. An editor decides that an article is ready to approve, or nearly so. If the editor has worked on it him/herself, he or she asks another editor to approve it; or, if there are several editors all doing significant work on the article, then at least three of them can agree to approve it.
  2. So then (one of) the approving editor(s) places a {{ToApprove}} template on the article's talk page. That approval template will be marked with a date, usually several days to a week from the date that it is placed. This acts as an announcement: If the approval template remains there, approval will occur on that date. Meanwhile, the template could be removed by another editor if the discussion on the talk page is one that brings up important objections.
  3. Unless the template is removed, on the designated date, a sysop (a person with "sysop" administrative rights on the wiki) then freezes the approved version of the article on the main article page under an {{Approved}} template. At that freeze, a draft form of the article is generated. The draft is not frozen.
  4. When a user calls up the article, the appoved (frozen) version appears. At the top of the article is a notice to users who would prefer to write or edit, redirecting them to the Draft page. Work on the article continues on that "Draft" page. Discussion about the article in progress is made on the Talk:Draft Page, and eventually it may be nominated to replace the approved version, and the procedure repeats.

The provisional nature of this process

This process is provisional and probably temporary in this form. The use of templates, in particular, may be regarded as a temporary stopgap measure; eventually, we will want to integrate certain procedures into the software itself. But it is actually desirable to test out the process first "by hand" before stabilizing it in code.

Who may approve

For any given topic, only editors who may be considered experts on that topic may approve an article on that topic.

Expert editors may approve articles in either of two configurations: individually or as part of a group.

Individual approval. Editors working individually may approve articles if they have not contributed significantly to the article; there is, in this way, a kind of peer review. No single editor may approve an article to which that editor has contributed significantly. In other words, no editor may approve his or her own work singlehandedly.

Group approval. If there are at least three editors, all of which are expert in the topic of an article, and all of which have been at work on an article, then any one of them may approve of an article with the concurrence of the other two (or more) expert editors.

A simple note to several relevant editors, drawing attention to the page, is a path by which an author may use to trigger the approval process.

When and how to use the {{ToApprove}} template

An approving editor (or "approver") should be of the considered opinion that the article satisfies the Citizendium article approval standards.

The actual act of approval consists of placing a {{ToApprove}} template at the top of the talk page of an article. (You may wish to consult the Wikimedia help page about templates for background. We haven't yet written our own help page for templates.)

Here is an example of the template as it appears on the talk page:

Toapprove.png
Nancy Sculerati MD has nominated this version of this article for approval. Other editors may also sign to support approval. The Biology Workgroup is overseeing this approval. Unless this notice is removed, the article will be approved on December 14, 2006.

Here is the code that produces that template:

{{ToApprove|editor=Nancy Sculerati MD|url=http://pilot.citizendium.org/wiki?title=Biology/Draft&oldid=100012889|group=Biology|date=December 14, 2006}}

Or, more generalized:

{{ToApprove|editor=APPROVER USERNAME|url=URL OF VERSION TO APPROVE|group=WORKGROUP|date=DATE TO APPROVE}}

To prepare the template, simply copy the above code and make the following replacements:

  • For APPROVER USERNAME, put the username of the approver. This is your username without the [[ ]] brackets and without the usual User: prefix.
  • For URL OF VERSION TO APPROVE, you need to look in the relevant page history:
    • If this the first time the article has been approved, then look under the "history" tab. Find the specific version, in the history, that you want to approve. It may or may not be the most recent version. Please don't simply put down the URL of the main article; so, you would not mark down simply http://pilot.citizendium.org/wiki/Biology as the URL to approve. It should be
    • If this article has been approved before, then look under the "history" tab of the /Draft article, for example, the "history" tab you find on the Biology/Draft page. This is where the "working (draft) version" of the article is.
  • For WORKGROUP, place the name of the overseeing workgroup, without the word "Workgroup"; so, "Biology" not "Biology Workgroup", or "Philosophy" not "Philosophy Workgroup".
  • For DATE TO APPROVE, write down the day after tomorrow, or perhaps better a few days after that if to allow time for completion of last minute copyedits. You must give others at least 24 full hours to examine the article after you have placed the {{ToApprove}} template.

If you have made all the correct replacements, then all the links in the template should appear blue; none should appear red.

Updating the {{ToApprove}} template after revision

It is all right if, in the days following the initial placement of the {{ToApprove}} template, the article undergoes significant revision. If after such revision the approver is still willing to approve the article in its revised state, he or she should update the URL in the template to point at the most recent satisfactory version of the article, found under the "history" tab. At any given moment it might or might not be the most recent version.

If an article is undergoing group approval, it must be the sense of at least two other editors, in addition to the approver, that the newly-revised version is also worthy of approval.

Involving other editors from a workgroup

  • Discuss your impending approval on the forum for the relevant workgroup(s). This isn't required but it's a good idea.

Involving copyeditors (informally)

  • Post a note to the Copyedit Board on the forums. Not required, but an excellent idea.

Sysops make it official with the {{Approved}} template

Anyone with "Sysop" permissions on the wiki--that is, personnel administrators, constables, and technical staff--may go through the following steps when initially marking an article as approved. An important exception is that no person with "Sysop" permissions on the wiki who has done any significant work on the article, or who is an editor in any workgroup to which the article is assigned, must "do the honors." That means that Editors at work on the article, who are also Constables, must call another Constable to "do the honors." We thus hold a hard line against appearances of conflict of interest. To ask a Constable to "make it official," simply send an e-mail to constables@citizendium.org. The following steps may be followed on or after the date (and time, if any) given by someone with "Sysop" permissions:

  1. Examine the talk page. Make sure it's clear that there are three editors who are in agreement about the approvability of the article, or, if it seems there is an individual approval going on, make sure that the person approving the article has not worked much on the article. (For that, examine the article's history.)
  2. Make the Draft page:
    • Copy the current version of the article (i.e., the one you see by simply clicking "edit"), and paste it into a new "Draft" page. If the article name is "XYZ" then the draft page name is "XYZ/Draft".
    • At the top of that page, make a link back to the approved version of the article: "Most recent approved version: [[XYZ]]"
    • Comment out the article's categories. To do this, simply surround the template code with
      <!-- [[Category:Foo]] ... -->
    • Save. You're done making the Draft page.
  3. Next, make the main namespace copy of the article and protect it:
    • On the talk page of the article to be approved, where you find the article's {{ToApprove}} template, click through to the URL supplied by the approving editor. Copy the text there.
    • Edit the main namespace version of the article. Delete whatever is there, and replace it with what you copied from the approved page.
    • At the very top of the article, put in the {{approved}} template. This requires that you copy the exact editor username and group name. Here is the form:
      {{approved|editor=APPROVER USERNAME|group=GROUP NAME}}
      For example:
      {{approved|editor=Nancy Sculerati MD|group=Biology}}
    • Save.
    • Press the "protect" tab. Explain why you're protecting the page: "Article version approved." You're done making the Approved article copy.
  4. Finally, go to the article's talk page, and "comment out"--do not delete--the template. To do this, simply surround the template code with
    <!-- [template code here] -->
  5. Leave a note saying that you've approved the article.
  6. Add a redirect at the top of the article's talk page to continue edit discussions at Foo/draft
==This page's role is to preserve a copy of XYZ Approved Version 1 editing discussions== ::====For discussions on subsequent XYZ versions V1.1, 1.2... see [[Talk:FXYZ/Draft]]====

Finished!

Approval and protection process for templates used in approved pages

Editors and sysops need to be aware that a protected approved page draws on templates which contain text. Consideration should be given to subjecting key subject specific templates for banners, boxes and footers to protection and editorial approval in step with major pages.

Revoking approval

Re-approving revisions to approved articles

Re-approval is the process of approving the replacement to and approved article. These replacements are called versions (XYX version 1.1 1.2 and so on) for clarity here.

The process of re-approving a revision to an an approved article is in its essentials the same as for the first version, but as two article pages (approved and draft page now exist), a mode of operation needs to be established to minimize confusion.

A suggested approach is to continue all edit discussions leading to re-approval on the XYZ/draft talk page, and provide a section at the top of that talk page for the approval templates of the sucessive versions, which can be referred to in the text of the talk page as V1.1, V1.2 etc.

e.g.

Article re-approval and version record area

Reserved for a log of re-approval of XYZ article revision events and template records==== templates

Version 1.1 approval events

(Earlier details of V 1.1 commented out for clarity)

(Approval V 1.1) confusing text commented out but log details retained.

Version V1.2 approval events

Approval V1.2



Annotate the top of XYZ talk page to the effect that editing discussions on article revisions are continuing on the XYZ/draft page.

It will be necessary for a sysop to transfer markup text to the protected main page to create a new approved version ( i.e. V1.1) by code copy, paste and save, and at such time annotate such re-approval save events with the approval version (e.g. V1.2 )and source of code ("permanent links to source code are at the top of XYZ/draft talk, commented out") descriptions to clarify the source of the text. This article re-approval actioning sysop should never be the user or users involved in proposing the re-approval, or having a substantive role in the particular article editing or authorship process. An exception may be correction of glaring minor errors of layout evidentduring the re-approved.