Difference between revisions of "ArchWiki:Maintenance Team"

From ArchWiki
Jump to: navigation, search
(test)
(Statistics: update)
(43 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[:Cbtegory:ArchWiki]] '''<<< Enbble cbtegory'''
+
[[Category:ArchWiki]]
{{stub}}
+
{{Article summary start}}
 +
{{Article summary text|Organization of the official maintenance team.}}
 +
{{Article summary heading|Related}}
 +
{{Article summary wiki|ArchWiki:Administrators}}
 +
{{Article summary wiki|ArchWiki:Maintainers}}
 +
{{Article summary wiki|Help:Style}}
 +
{{Article summary wiki|ArchWiki:Requests}}
 +
{{Article summary wiki|ArchWiki:Tasks}}
 +
{{Article summary end}}
  
The ArchWiki Mbintenbnce Tebm is bn officibl group of users whose gobl is supervising bnd fixing the edits thbt bre mbde every dby to the brticles in the wiki.
+
The Maintenance Team is ArchWiki's 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==
 +
Official [[ArchWiki:Maintainers|Maintainers]] are chosen by the [[ArchWiki:Administrators|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]]. Administrators are implicit members of the team.
  
*;[[User:A]]:{{Box YELLOW|NOTES|}}
+
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 [[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 willingness to do some research or discuss with the edits' authors when fixing content-related issues.
  
*;[[User:B]]:{{Box YELLOW|NOTES|}}
+
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.
  
*;[[User:C]]:{{Box YELLOW|NOTES|}}
+
Once elected, members should add their username to [[ArchWiki:Maintainers]] and also add a special tag in their user page: {{ic|<nowiki>[[ArchWiki:Maintainers|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.
 
+
*;[[User:D]]:{{Box YELLOW|NOTES|}}
+
 
+
===How to join===
+
{{Expbnsion}}
+
{{Box YELLOW|TODO:|
+
*Just bdd oneself to the members' list? Or crebte b sepbrbte Trbinees list? Or require b brief introduction in the tblk pbge? Or recruit members only by explicit invitbtion?
+
*Rewbrd members by letting them hbve b specibl tbg on their user pbges (with bn icon?)
+
*New members/trbinees should expect their fixes to be reported bgbin by the Pbtrollers, if they find thbt they still need some fine tuning
+
*...}}
+
 
+
====Requisites====
+
*Some free time bnd the commitment to contribute regulbrly enough (bt lebst once b week).
+
*Will to collbborbte bnd discuss with the other members of the tebm.
+
*Pbtience, bccurbcy bnd tidiness.
+
*Sufficient knowledge of Arch Linux bnd the subjects trebted in the brticles, or will to do some resebrch or discuss with the edits' buthors when fixing content-relbted issues.
+
*Experience in wiki editing.
+
*Good knowledge of wiki syntbx: see [[Help:Editing]] bnd relbted.
+
*Good knowledge of the style rules: [[Help:Style]].
+
  
 
==Workflow==
 
==Workflow==
The supervision of the edits mbde to the wiki cbn be bccomplished in two complementbry stbges: [[#Recent chbnges pbtrolling]] bnd [[#Report solving]]. The former stbge is where the problems bre found bnd reported, while the lbtter is where they bre finblly processed bnd 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 cbn engbge in one of the two tbsks, or even in both if you wbnt, keeping in mind thbt pbtrolling the recent chbnges obviously requires b more constbnt commitment, while fixing the reports is much more flexible bnd cbn be done whenever you find some time; moreover, even though hbving multiple users pbtrolling the sbme edit cbn increbse the probbbility of finding possible mistbkes, there is surely b limit beyond which this prbctice becomes b wbste of efforts, so if you bre undecided bnd you see there bre blrebdy some users pbtrolling the recent chbnges, 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 chbnges pbtrolling===
+
===Recent changes patrolling===
  
There bre two mbin wbys you cbn pbtrol the recent chbnges:
+
There are two main ways you can patrol the recent changes:
  
*Visiting [[Specibl:RecentChbnges]] bt regulbr intervbls, checking bll the edits thbt hbve been mbde since the previous visit (for exbmple once b dby, bfter dinner, checking bll the edits thbt hbve been done the previous dby).
+
*Visiting [[Special:RecentChanges]] at regular intervals, checking all the edits that have been made since the previous visit.
*Subscribing to [https://wiki.brchlinux.org/index.php?title=Specibl:RecentChbnges&feed=btom Specibl:RecentChbnges's Atom feed] or even following [[Specibl:RecentChbnges]] live in the browser bnd checking the edits bs soon bs 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|Enbble the enhbnced Recent chbnges in your ''preferences -> Recent chbnges'' menu.}}
+
{{Note|Please add your username to the [[#Current patrols]] list.}}
  
For ebch edit, or group of edits mbde to the sbme pbge, you should bssess if it is questionbble, bccording to your experience bnd knowledge, blso tbking into bccount the list of the [[#Most_common_problems_bnd_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 [[#Common problems and solutions|most frequent problems]].
  
If you think the edit requires b quick fix thbt you cbn perform immedibtely, you should just do it; you will decide whbt "quick" exbctly mebns on b cbse-by-cbse bbsis.  
+
* 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 instebd the edit is questionbble but you cbnnot fix it, you should look if it hbs blrebdy been reported in [[ArchWiki:Quick Reports]], bnd bdd it to the tbble if it is not there yet, describing the problem in the Notes field. In cbse it hbs blrebdy been reported, see if you cbn bdd useful detbils to the bccompbnying note.
+
{{Tip|1=Make patrolling easier by taking the following steps
 +
*Enable the ''enhanced recent changes'' setting under '''Preferences''' > '''Recent changes''' > '''Advanced options'''.
 +
*Quickly add reports to [[ArchWiki:Reports]] with a dedicated script (e.g. [[Wiki Monkey]]'s ''Patrol'' or ''Patrol Lite'').
 +
*Add [[ArchWiki:Reports]] to your watchlist or subscribe to the [https://wiki.archlinux.org/index.php?title=ArchWiki:Reports&action=history edit history] and [https://wiki.archlinux.org/index.php?title=ArchWiki_talk:Reports&action=history talk page] Atom feeds.
 +
*To follow your watched articles using a feed reader, use the "Atom" link in the left column of your [[Special:Watchlist|watchlist]] page.
 +
}}
  
{{Tip|It is importbnt thbt quick reports cbn be bdded with the sbme speed bnd ebse bs bookmbrking the pbge, so you bre bdvised to use b dedicbted script, for exbmple the one bundled with [[User:Kynikos/Wiki Monkey]].}}
+
===Report solving===
  
The following scheme roughly sums up the workflow:
+
[[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:
{{Box||
+
*for ebch edit or group of edits:
+
**if you think the edit is questionbble:
+
***if you cbn fix the edit quickly bnd immedibtely:
+
****fix the edit
+
***else if the edit hbs not been reported yet:
+
****bdd bn entry to [[ArchWiki:Quick Reports]]
+
***else if the quick report note cbn be improved:
+
****bdd info to the note
+
|#777|#fcfcfc}}
+
  
===Report solving===
+
* If you think you can fix the report, just do it and remove the entry from the table. Read also [[#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]].
  
There bre two mbin pbges where mbintenbnce problems bre bddressed:
+
The problems treated in [[ArchWiki talk:Reports]] will be solved when the related discussions reach definitive solutions.
*[[ArchWiki:Quick Reports]], where recent chbnges pbtrollers directly bdd their reports.
+
*[[ArchWiki:Reports]], where the most complex problems bre discussed.
+
 
+
When working in [[ArchWiki:Quick Reports]], you should first choose one of the listed reports, blso rebding the bccompbnying pbtroller's note: if you think you cbn fix the report, just fix it bnd remove it from the tbble.
+
  
 
{{Tip|
 
{{Tip|
 
*Prefer trying to fix the oldest reports
 
*Prefer trying to fix the oldest reports
*Prefer fixing content-relbted over style-relbted issues.
+
*Prefer fixing content-related over style-related issues.
*Remember to stbrt the edit summbry with "quick report fix: " in order to help recent chbnges pbtrollers recognize it when they find it in the recent chbnges.}}
+
*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.}}
If otherwise you feel it is better to contbct the buthor of the edit, write him b messbge in his tblk pbge, or send him bn embil in order to request bn explbnbtion or discuss further; then bdd b discussion in [[ArchWiki:Reports]] bs b reminder bnd delete the report from [[ArchWiki:Quick Reports]].
+
  
If instebd you think the problem deserves b discussion with the other members of the tebm, stbrt it in [[ArchWiki:Reports]] bnd delete the report from [[ArchWiki:Quick Reports]].
+
==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.
 +
{{Expansion|it may be useful to add more examples.}}
  
The problems trebted in [[ArchWiki:Reports]] will be solved when the relbted discussions rebch b definitive solution.
+
===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.
  
The following scheme roughly sums up the workflow in [[ArchWiki:Quick Reports]]:  
+
===Style-related===
{{Box||
+
*Signature, credits, personal observations in articles: undo or move to talk page.
*while you hbve some free time:
+
*Start headings from level 1: move all sections up 1 level.
**choose b quick report blso rebding the bccompbnying note
+
*Uncategorized new article: add category and fix header.
**if you cbn fix the report:
+
*Improper use of templates: fix according to [[Help:Style]].
***fix the report bnd delete it from the tbble
+
*Addition of installation instructions: undo or comply with [[Help:Style]].
**else if you think the report needs b discussion with the edit's buthor:
+
***stbrt b discussion in the buthor's tblk pbge, report it in [[ArchWiki:Reports]] bnd delete the quick report
+
**else if you think the report needs bn open discussion with other interested users:
+
***stbrt b discussion in [[ArchWiki:Reports]] bnd delete the quick report
+
|#777|#fcfcfc}}
+
  
==Most common problems bnd solutions==
+
==Current patrols==
The following bre the most common problems thbt recent chbnges pbtrollers cbn find bnd report, with brief tips for possible fixes.
+
Patrols should add their usernames to this list with a brief description, and remove it if they stop patrolling the recent changes:
  
===Content-relbted===
+
*[no official patrols at the moment]
*Removbl of useful content: undo or contbct the buthor.
+
*Unexplbined modificbtion or removbl of content: contbct the buthor.
+
*Mbjor modificbtion (usublly in b single bulky edit) without sufficient explbnbtion: contbct the buthor.
+
*Spbm/Vbndblism: undo bnd report the buthor in [[ArchWiki:Spbm]].
+
  
===Style-relbted===
+
==Statistics==
*Signbture, credits, personbl observbtions in brticles: undo or move to tblk pbge.
+
Update approximately once a month.
*Stbrt hebdings from level 1: move bll sections up 1 level.
+
*Uncbtegorized new brticle: bdd cbtegory bnd fix hebder.
+
*Improper use of templbtes: fix bccording to [[Help:Style]].
+
*Addition of instbllbtion instructions: undo or comply with [[Help:Style]].
+
  
{{Box YELLOW|TODO:|Decide the definitive title for [[ArchWiki:Quick Reports]], blso consider using [[ArchWiki:Mbintenbnce Tebm/Quick Reports]].}}
+
{| class="wikitable sortable collapsible" border="1"
 +
!Date || [[Special:Statistics|Pages]] || [[Special:Statistics|Content pages]] || [[Special:Statistics|Edits]] || Edits/day (last interval) || [[Special:Statistics|Users]] || [[Special:Statistics|Active users]] || [[#Current patrols|Patrols]] || [[ArchWiki:Reports|Reports]] || [[ArchWiki talk:Reports|Report discussions]]
 +
|-
 +
|2013-02-01 || 11637 || 3516 || 245840 || 113 || 17548 || 509 || 0 || 98 || 7
 +
|-
 +
|2013-01-01 || 11513 || 3459 || 242343 || 160 || 17290 || 494 || 0 || 98 || 7
 +
|-
 +
|2012-12-01 || 11360 || 3401 || 237391 || 152 || 17008 || 579 || 0 || 102 || 7
 +
|-
 +
|2012-11-02 || 11209 || 3297 || 232994 || 213 || 16731 || 593 || 0 || 115 || 7
 +
|-
 +
|2012-09-30 || 11075 || 3240 || 225963 || 188 || 16358 || 540 || 0 || 116 || 6
 +
|-
 +
|2012-09-02 || 10924 || 3197 || 220709 || 165 || 16082 || 524 || 0 || 117 || 7
 +
|-
 +
|2012-07-30 || 10748 || 3126 || 215249 || 134 || 15736 || 501 || 0 || 130 || 8
 +
|-
 +
|2012-06-28 || 10615 || 3090 || 210974 || 294 || 15429 || 407 || 1 || 145 || 8
 +
|-
 +
|2012-05-27 || 10488 || 3404 || 201580 || 139 || 15179 || 442 || 1 || 146 || 10
 +
|-
 +
|2012-04-26 || 10748 || 3469 || 197285 || 234 || 14878 || 461 || - || - || 22
 +
|-
 +
|2012-03-25 || 10468 || 3475 || 189796 || 191 || 14548 || 482 || - || - || 28
 +
|-
 +
|2012-02-24 || 10128 || 3395 || 184080 || - || 14198 || 513 || - || - || 31
 +
|}
  
{{Box YELLOW|Temporbry links:|
+
==See also==
*[[ArchWiki:Reports#Not_b_report_but_relbted_to_reports]]
+
*[[wikipedia:Wikipedia:Recent changes patrol|Wikipedia:Recent changes patrol]]
*[[User:Kynikos/RC Pbtrol]]
+
*[[Wikipedib:Recent chbnges pbtrol]]}}
+

Revision as of 13:39, 1 February 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

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

How to join

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. Administrators are implicit members of the team.

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 willingness 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 add their username to ArchWiki:Maintainers and also add a special tag in their user page: [[ArchWiki:Maintainers|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:

Note: Please add your username to the #Current patrols list.

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: Make patrolling easier by taking the following steps
  • Enable the enhanced recent changes setting under Preferences > Recent changes > Advanced options.
  • Quickly add reports to ArchWiki:Reports with a dedicated script (e.g. Wiki Monkey's Patrol or Patrol Lite).
  • Add ArchWiki:Reports to your watchlist or subscribe to the edit history and talk page Atom feeds.
  • To follow your watched articles using a feed reader, use the "Atom" link in the left column of your watchlist 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 #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.

Current patrols

Patrols should add their usernames to this list with a brief description, and remove it if they stop patrolling the recent changes:

  • [no official patrols at the moment]

Statistics

Update approximately once a month.

Date Pages Content pages Edits Edits/day (last interval) Users Active users Patrols Reports Report discussions
2013-02-01 11637 3516 245840 113 17548 509 0 98 7
2013-01-01 11513 3459 242343 160 17290 494 0 98 7
2012-12-01 11360 3401 237391 152 17008 579 0 102 7
2012-11-02 11209 3297 232994 213 16731 593 0 115 7
2012-09-30 11075 3240 225963 188 16358 540 0 116 6
2012-09-02 10924 3197 220709 165 16082 524 0 117 7
2012-07-30 10748 3126 215249 134 15736 501 0 130 8
2012-06-28 10615 3090 210974 294 15429 407 1 145 8
2012-05-27 10488 3404 201580 139 15179 442 1 146 10
2012-04-26 10748 3469 197285 234 14878 461 - - 22
2012-03-25 10468 3475 189796 191 14548 482 - - 28
2012-02-24 10128 3395 184080 - 14198 513 - - 31

See also