This is an old revision of this page, as edited by RobLa (talk | contribs) at 20:08, 10 May 2010 (→Reviewing: Adapted the table+prose from Misplaced Pages:Flagged protection in a simplified form on this page. I'll elaborate on the simplification on Talk page.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 20:08, 10 May 2010 by RobLa (talk | contribs) (→Reviewing: Adapted the table+prose from Misplaced Pages:Flagged protection in a simplified form on this page. I'll elaborate on the simplification on Talk page.)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)| Pending changes Interface: Pages with pending edits · Pages under pending changes · Pending changes log · Documentation: Main talk · Reviewing guideline · Reviewing talk · Protection policy · Testing · Statistics |
| 2010 Trial and 2012 Implementation
Historical: Trial proposal · Specifics · Reviewing guideline · Metrics · Terminology · Queue · Feedback · Closure · 2012 Implementation Discussions: |
Summary information for editors
|
The purpose of this page is to coordinate the trial and centralize the discussion on its conduct and evaluation. The trial will last for two months and then a community discussion will decide the future of the implementation, the default being deactivation. Each section must be completed based on the discussions before the trial implementation; for now, they are only brief introductions on the subject to debate.
Conduct
How should the trial be conducted? Should we create control groups?
Flag protection
Creation of a draft policy on when to use flag protection, and when to use normal protection in lights of flag protection, both being limited in scope by the official protection policy.
Reviewing
For the trial, there will be two protection levels: semi flagged protection and full flagged protection. On semi-flagged protected pages, the latest confirmed revision is displayed to readers by default. All autoconfirmed users are auto-confirmed on semi-flagged protected pages, that is, if the latest version of a page is confirmed, a new revision by an autoconfirmed user is automatically confirmed. On fully flagged protected pages, only admins will have the ability to confirm edits.
The following table shows the effect of the new protection levels:
| Protection levels | Anonymous / Non-Autoconfirmed | Autoconfirmed | Administrator | |
|---|---|---|---|---|
| Semi-protection | Cannot edit | Can edit; edits are immediately visible | ||
| Semi flagged protection (new) | Can edit; a new edit is visible to registered users, but not to readers by default until confirmed by an 'auto-confirmed' user (or an 'administrator') | Can edit; a new edit is visible immediately if the previous version is already confirmed or when the option "confirm this revision" is selected; otherwise the article is unconfirmed until an 'administrator' confirms the edit. | ||
| Full protection | Cannot edit | Can edit; edits are visible immediately | ||
| Full flagged protection (new) | Can edit; new edits are visible to registered users, but not to readers by default until validated by an 'administrator' | Can edit; a new edit is visible immediately if the previous version is already confirmed or when the option "confirm this revision" is selected; otherwise the article is unconfirmed until an 'administrator' confirms the edit. | ||
During the trial period, the community will have the opportunity to discuss the possibility of adding a new level of account access for "reviewers" which would be a new level between 'administrator' and 'auto-protected' user. See Misplaced Pages:Reviewers for more.
Content
In addition to reviewing policy/guideline content, other content will need to be created and/or modified.
- For example, the "When you click Save, your changes will immediately become visible to everyone." text will not be true for the flagged protection levels. This text appears at the bottom of every edit page; see http://en.wikipedia.org/MediaWiki:Edittools . We need to have this figured out and ready-to-roll before the trial can begin.
- etc.
Initial article count limits
The initial plan calls for putting an upper bound of 2000 articles under Flagged Protection, adjusting the number up or down depending on how the trial is going. The rationale:
- Performance - we know already from de.wikipedia.org and from watching flaggedrevs.labs.wikimedia.org that this feature can impact performance. So, the engineering team at WMF would like to start small and build up from there
- Community norm development - this gives the community a chance to use this in production in a limited way to start with to get a feel for the feature in the wild.
If performance takes a hit, the ops team may wish to roll back Flagged Protection on a portion of the articles (mechanism TBD), rather than shutting off the feature altogether. If things are going well on both the performance and community norm fronts, the operations team may increase the limit during the trial.
There are not currently plans for a limit after the trial period. However, there may need to be some mechanism in place to prevent drastic increases in the number of articles placed under Flagged Protection to safeguard site performance.
Measure of success
measures, metrics for trial success, etc, some can be adapted from Misplaced Pages:Flagged revisions/Trial/Proposed trials#Possible metrics to measure success of trials
Category: