Difference between revisions of "ArchWiki:Maintenance Team"

From ArchWiki
Jump to: navigation, search
(related)
(Recent changes patrolling: allow bypassing the table)
Line 58: Line 58:
 
If you think the edit requires a quick fix that you can perform immediately, you should just do it; you will decide what "quick" exactly means on a case-by-case basis.  
 
If you think the edit requires a quick fix that you can perform immediately, you should just do it; you will decide what "quick" exactly means on a case-by-case basis.  
  
If instead the edit is questionable but you cannot fix it, you should look if it has already been reported in [[ArchWiki:Reports]], and add it to the table if it is not there yet, describing the problem in the Notes field. In case it has already been reported, see if you can add useful details to the accompanying note. Note that the table distinguishes between content and style-related reports with the "Type" field: if an edit has both content and style problems, mark it as "content".
+
If instead the edit is questionable but you cannot fix it, you should look if it has already been reported in [[ArchWiki:Reports]], and add it to the table if it is not there yet, describing the problem in the Notes field; in case it has already been reported, see if you can add useful details to the accompanying note. Note that the table distinguishes between content and style-related reports with the "Type" field: if an edit has both content and style problems, mark it as "content". As an alternative, you may even decide to add the report directly in [[ArchWiki talk:Reports]], still checking that it is not there yet.  
  
{{Tip|It is important that quick reports can be added with the same speed and ease as bookmarking the page, so you are advised to use a dedicated script, for example the one bundled with [[Wiki Monkey]].}}
+
{{Tip|It is important that quick reports can be added to [[ArchWiki:Reports]] with the same speed and ease as bookmarking the page, so you are advised to use a dedicated script, for example the one bundled with [[Wiki Monkey]].}}
 +
{{Box YELLOW|TODO|Expand Wiki Monkey's compatibility}}
  
 
The following scheme roughly sums up the workflow:
 
The following scheme roughly sums up the workflow:
Line 69: Line 70:
 
****fix the edit
 
****fix the edit
 
***else if the edit has not been reported yet:
 
***else if the edit has not been reported yet:
****add an entry to [[ArchWiki:Reports]]
+
****add an entry to [[ArchWiki:Reports]] or [[ArchWiki talk:Reports]]
***else if the quick report note can be improved:
+
***else if the quick report note (or the information in its discussion, if existing) can be improved:
****add info to the note
+
****improve the note or the discussion
 
|#777|#fcfcfc}}
 
|#777|#fcfcfc}}
  

Revision as of 16:08, 18 April 2012

Category:ArchWiki <<< Enable category

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: The organization of the team is still under discussion. (Discuss in ArchWiki talk:Maintenance Team#)
Summary help replacing me
Organization of the official maintenance team.
Related
Help:Style
ArchWiki:Requests
ArchWiki:Tasks

The ArchWiki Maintenance Team is an official group of users whose goal is supervising and fixing the edits that are made every day to the articles in the wiki.

Members

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Members should be listed here with specific notes, read #How to join. (Discuss in ArchWiki talk:Maintenance Team#)
  • ...

How to join

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: This section is still under development and may contain inaccurate information. (Discuss in ArchWiki talk:Maintenance Team#)
Template:Box YELLOW

Template:Box YELLOW Just read the #Requisites below and, if you think you satisfy them, joining the team can be as easy as appending your name to the list in the #Members section; please also add a brief description of how you will help exactly and how often you think you will be able to contribute. The #Workflow section explains how this team is organized and how its members work with each other.

Then you can add a special tag in your user page: ArchWiki Maintainer (code: [[ArchWiki:Maintenance Team|ArchWiki Maintainer]]).

Note: New/unexperienced members may see their own fixes reported again by the recent changes patrollers, if these find that some fine tuning is still required: this is perfectly normal and part of learning the best fixing techniques.

Requisites

  • Some free time and the commitment to contribute regularly enough (at least once a week).
  • Will to collaborate and discuss with the other members of the team.
  • Patience, accuracy and tidiness.
  • Sufficient knowledge of Arch Linux and the subjects treated in the articles, or will to do some research or discuss with the edits' authors when fixing content-related issues.
  • Experience in wiki editing.
  • Good knowledge of wiki syntax: see Help:Editing and related.
  • Good knowledge of the style rules: Help:Style.

Workflow

The supervision of the edits made to the wiki can be accomplished in two complementary stages: #Recent changes patrolling and #Report solving. The former stage is where the problems are found and reported, while the latter is where they are finally processed and solved.

You can engage in one of the two tasks, or even in both if you want, keeping in mind that patrolling the recent changes obviously requires a more constant commitment, while fixing the reports is much more flexible and can be done whenever you find some time; moreover, even though having multiple users patrolling the same edit increases the probability of finding possible mistakes, there is surely a limit beyond which this practice becomes a waste of efforts, so if you are undecided and you see there are already some users patrolling the recent changes, prefer helping in report solving.

Recent changes patrolling

There are two main ways you can patrol the recent changes:

  • Visiting Special:RecentChanges at regular intervals, checking all the edits that have been made since the previous visit (for example once a day, after dinner, checking all the edits that have been done the previous day).
  • Subscribing to Special:RecentChanges's Atom feed or even following Special:RecentChanges live in the browser and checking the edits as soon as you find some time.
Tip: Enable the enhanced Recent changes in your preferences -> Recent changes menu.

For each edit, or group of edits made to the same page, you should assess if it is questionable, according to your experience and knowledge, also taking into account the list of the most frequent problems.

If you think the edit requires a quick fix that you can perform immediately, you should just do it; you will decide what "quick" exactly means on a case-by-case basis.

If instead the edit is questionable but you cannot fix it, you should look if it has already been reported in ArchWiki:Reports, and add it to the table if it is not there yet, describing the problem in the Notes field; in case it has already been reported, see if you can add useful details to the accompanying note. Note that the table distinguishes between content and style-related reports with the "Type" field: if an edit has both content and style problems, mark it as "content". As an alternative, you may even decide to add the report directly in ArchWiki talk:Reports, still checking that it is not there yet.

Tip: It is important that quick reports can be added to ArchWiki:Reports with the same speed and ease as bookmarking the page, so you are advised to use a dedicated script, for example the one bundled with Wiki Monkey.

Template:Box YELLOW

The following scheme roughly sums up the workflow: Template:Box

Report solving

ArchWiki:Reports is the reference page for addressing maintenance problems. When working there, you should first choose one of the listed reports, also reading the accompanying patroller's note: if you think you can fix the report, just fix it and remove it from the table. Read also #Most common problems and solutions.

If otherwise you feel it is better to contact the author of the edit, write him a message in his talk page, or send him an email in order to request an explanation or discuss further; then add a discussion in ArchWiki talk:Reports as a reminder and delete the report from ArchWiki:Reports.

If instead you think the problem deserves a discussion with the other members of the team, start it in ArchWiki talk:Reports and delete the report from ArchWiki:Reports.

The problems treated in ArchWiki talk:Reports will be solved when the related discussions reach a definitive solution.

Tip:  
  • Prefer trying to fix the oldest reports
  • Prefer fixing content-related over style-related issues.
  • Remember to start the edit summary with "quick report fix: " in order to help recent changes patrollers recognize it when they find it in the recent changes.
  • Add ArchWiki:Reports to your watchlist or subscribe to the Atom feed of its history and the one of the talk page.
  • You may consider using an editor assistant (e.g. Wiki Monkey) in order to solve some common style issues automatically.

The following scheme roughly sums up the workflow in ArchWiki:Reports: Template:Box

Most common problems and solutions

The following are the most common problems that recent changes patrollers can find and report, with brief tips for possible fixes.

Content-related

  • Removal of useful content: undo or contact the author.
  • Unexplained modification or removal of content: contact the author.
  • Major modification (usually in a single bulky edit) without sufficient explanation: contact the author.

Style-related

  • Signature, credits, personal observations in articles: undo or move to talk page.
  • Start headings from level 1: move all sections up 1 level.
  • Uncategorized new article: add category and fix header.
  • Improper use of templates: fix according to Help:Style.
  • Addition of installation instructions: undo or comply with Help:Style.

Statistics

Update approximately once a month.

Date Pages Content pages Edits Edits/day (last interval) Users Active users Maintainers Reports Report discussions
2012-02-24 10128 3395 184080 - 14198 513 - - 31
2012-03-25 10468 3475 189796 191 14548 482 - - 28

See also