Difference between revisions of "ArchWiki:Maintenance Team"

From ArchWiki
Jump to: navigation, search
(Recent changes patrolling: update)
(update join procedure, be much more schematic, drop useless considerations)
Line 14: Line 14:
 
==Members==
 
==Members==
 
{{Expansion|Members should be listed here with specific notes, read [[#How to join]].}}
 
{{Expansion|Members should be listed here with specific notes, read [[#How to join]].}}
*;[[User:A]]:{{Box YELLOW|NOTES|}}
 
  
*;[[User:B]]:{{Box YELLOW|NOTES|}}
+
;[[User:A]]:{{Box YELLOW|NOTES|}}
 
+
;[[User:B]]:{{Box YELLOW|NOTES|}}
*;...
+
;...
  
 
===How to join===
 
===How to join===
 
{{Accuracy|This section is still under development and may contain inaccurate information.}}
 
{{Accuracy|This section is still under development and may contain inaccurate information.}}
{{Box YELLOW|option A|TODO}}
 
  
{{Box YELLOW|option B|}}
+
Official Maintainers are chosen by the Administrators among the most active and collaborative users of the wiki, and personally invited to participate in the team. Maintainers belong to a particular group of wiki users with [[Special:ListGroupRights|special rights]].
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:Maintenance Team|ArchWiki Maintainer]] (code: {{ic|<nowiki>[[ArchWiki:Maintenance Team|ArchWiki Maintainer]]</nowiki>}}).
+
Common requisites for becoming a Maintainer are:
 
+
*Some free time and the commitment to contribute regularly enough.
{{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.
 
*Will to collaborate and discuss with the other members of the team.
 
*Patience, accuracy and tidiness.
 
*Patience, accuracy and tidiness.
 +
*Experience in wiki editing and good knowledge of [[Help:Editing|wiki syntax]].
 +
*Good knowledge of the structure of ArchWiki and its [[Help:Style|style rules]].
 
*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.
 
*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.
+
If you are interested in joining the team, you can start making yourself visible to the community by helping with the [[ArchWiki:Tasks|common tasks]], in particular contributing to the discussions that take place in the various talk pages.
*Good knowledge of the style rules: [[Help:Style]].
+
 
 +
Once elected, members should describe briefly, in the [[#Members|above list]], the areas where they will be helping, possibly adding other useful considerations; they may also add a special tag in their user page: {{ic|<nowiki>[[ArchWiki:Maintenance Team|ArchWiki Maintainer]]</nowiki>}}. Then they are advised to read the following sections which explain how this team is organized and how its members work with each other.
  
 
==Workflow==
 
==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.
 
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.
+
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.
  
 
===Recent changes patrolling===
 
===Recent changes patrolling===
Line 49: Line 45:
 
There are two main ways you can patrol the recent changes:
 
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).
+
*Visiting [[Special:RecentChanges]] at regular intervals, checking all the edits that have been made since the previous visit.
*Subscribing to [https://wiki.archlinux.org/index.php?title=Special:RecentChanges&feed=atom 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.
+
*Subscribing to [https://wiki.archlinux.org/index.php?title=Special:RecentChanges&feed=atom Special:RecentChanges's Atom feed] 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_common_problems_and_solutions|most frequent problems]].
 
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_common_problems_and_solutions|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 you think the edit requires a quick fix that you can perform immediately, just do it.
 +
* If instead the edit is questionable but you cannot fix it, you should look if it has already been reported in [[ArchWiki:Reports]]:
 +
** If not, add it to the table describing the problem in the ''Notes'' field; 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 decide to add the report directly in [[ArchWiki talk:Reports]], still checking that it is not there yet.
 +
** In case the edit has already been reported, see if you can add useful details to the accompanying note or discussion.
  
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|1=&nbsp;
 
+
*Enable the ''enhanced recent changes'' in your ''preferences -> Recent changes'' menu.
{{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]]'s ''Patrol'' or ''Patrol Lite'' configurations.}}
+
*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]]'s ''Patrol'' or ''Patrol Lite'' configurations.
 
+
*Add [[ArchWiki:Reports]] to your watchlist or subscribe to the Atom feed of [https://wiki.archlinux.org/index.php?title=ArchWiki:Reports&action=history its history] and [https://wiki.archlinux.org/index.php?title=ArchWiki_talk:Reports&action=history the one of the talk page].}}
The following scheme roughly sums up the workflow:
+
{{Box||
+
*for each edit or group of edits:
+
**if you think the edit is questionable:
+
***if you can fix the edit quickly and immediately:
+
****fix the edit
+
***else if the edit has not been reported yet:
+
****add an entry to [[ArchWiki:Reports]] or [[ArchWiki talk:Reports]]
+
***else if the quick report note (or the information in its discussion, if existing) can be improved:
+
****improve the note or the discussion
+
|#777|#fcfcfc}}
+
  
 
===Report solving===
 
===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]].
+
[[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 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 you think you can fix the report, just do it and remove the entry 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]].
  
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 definitive solutions.
  
The problems treated in [[ArchWiki talk:Reports]] will be solved when the related discussions reach a definitive solution.
+
{{Tip|
 
+
{{Tip|1=&nbsp;
+
 
*Prefer trying to fix the oldest reports
 
*Prefer trying to fix the oldest reports
 
*Prefer fixing content-related over style-related issues.
 
*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.
 
*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 [https://wiki.archlinux.org/index.php?title=ArchWiki:Reports&action=history its history] and [https://wiki.archlinux.org/index.php?title=ArchWiki_talk:Reports&action=history the one of the talk page].
+
*You may consider using an editor assistant (e.g. [[Wiki Monkey]]'s ''Editor'' configuration) in order to solve some common style issues automatically.}}
*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]]:
+
{{Box||
+
*while you have some free time:
+
**choose a report also reading the accompanying note
+
**if you can fix the report:
+
***fix the report and delete it from the table
+
**else if you think the report needs a discussion with the edit's author:
+
***start a discussion in the author's talk page, report it in [[ArchWiki talk:Reports]] and delete the report from the table
+
**else if you think the report needs an open discussion with other interested users:
+
***start a discussion in [[ArchWiki talk:Reports]] and delete the report from the table
+
|#777|#fcfcfc}}
+
  
==Most common problems and solutions==
+
==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.
 
The following are the most common problems that recent changes patrollers can find and report, with brief tips for possible fixes.
 +
{{Expansion|it may be useful to add more examples.}}
  
 
===Content-related===
 
===Content-related===

Revision as of 23:40, 26 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#)
User:A
Template:Box YELLOW
User:B
Template:Box YELLOW
...

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#)

Official Maintainers are chosen by the Administrators among the most active and collaborative users of the wiki, and personally invited to participate in the team. Maintainers belong to a particular group of wiki users with special rights.

Common requisites for becoming a Maintainer are:

  • Some free time and the commitment to contribute regularly enough.
  • Will to collaborate and discuss with the other members of the team.
  • Patience, accuracy and tidiness.
  • Experience in wiki editing and good knowledge of wiki syntax.
  • Good knowledge of the structure of ArchWiki and its style rules.
  • 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.

If you are interested in joining the team, you can start making yourself visible to the community by helping with the common tasks, in particular contributing to the discussions that take place in the various talk pages.

Once elected, members should describe briefly, in the above list, the areas where they will be helping, possibly adding other useful considerations; they may also add a special tag in their user page: [[ArchWiki:Maintenance Team|ArchWiki Maintainer]]. Then they are advised to read the following sections which explain how this team is organized and how its members work with each other.

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.

Recent changes patrolling

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

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, just do it.
  • If instead the edit is questionable but you cannot fix it, you should look if it has already been reported in ArchWiki:Reports:
    • If not, add it to the table describing the problem in the Notes field; 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 decide to add the report directly in ArchWiki talk:Reports, still checking that it is not there yet.
    • In case the edit has already been reported, see if you can add useful details to the accompanying note or discussion.
Tip:  
  • Enable the enhanced recent changes in your preferences -> Recent changes menu.
  • 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's Patrol or Patrol Lite configurations.
  • Add ArchWiki:Reports to your watchlist or subscribe to the Atom feed of its history and the one of the talk page.

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 do it and remove the entry 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 definitive solutions.

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.
  • You may consider using an editor assistant (e.g. Wiki Monkey's Editor configuration) in order to solve some common style issues automatically.

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.

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

Reason: it may be useful to add more examples. (Discuss in ArchWiki talk:Maintenance Team#)

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
2012-04-26 10748 3469 197285 234 14878 461 - - 22

See also