ArchWiki:Maintenance Team

From ArchWiki
Revision as of 16:42, 5 February 2012 by Kynikos (Talk | contribs) (Recent changes patrolling: rw)

Jump to: navigation, search

Category:ArchWiki <<< Enable category

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

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in ArchWiki talk:Maintenance Team#)

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

How to join

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

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in ArchWiki talk:Maintenance Team#)
Template:Box YELLOW

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 can increase 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:Quick 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.

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 User:Kynikos/Wiki Monkey.

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

Report solving

There are two main pages where maintenance problems are addressed: ArchWiki:Quick Reports, where recent changes patrollers directly add their reports, and ArchWiki:Reports, where the most complex problems are discussed.

When working in ArchWiki:Quick Reports, 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.

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.

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:Reports as a reminder and delete the report from ArchWiki:Quick Reports.

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

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

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

Most common problems and solutions

Content-related

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

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in ArchWiki talk:Maintenance Team#)

Style-related

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

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in ArchWiki talk:Maintenance Team#)
Template:Box YELLOW