Difference between revisions of "ArchWiki:Maintenance Team"

From ArchWiki
Jump to: navigation, search
(test)
(Undo revision 183040 by Kynikos (talk) test)
Line 1: Line 1:
[[:Cbtegory:ArchWiki]] '''<<< Enbble cbtegory'''
+
[[:Category:ArchWiki]] '''<<< Enable category'''
 
{{stub}}
 
{{stub}}
  
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 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==
 
==Members==
Line 15: Line 15:
  
 
===How to join===
 
===How to join===
{{Expbnsion}}
+
{{Expansion}}
 
{{Box YELLOW|TODO:|
 
{{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?
+
*Just add oneself to the members' list? Or create a separate Trainees list? Or require a brief introduction in the talk page? Or recruit members only by explicit invitation?
*Rewbrd members by letting them hbve b specibl tbg on their user pbges (with bn icon?)
+
*Reward members by letting them have a special tag on their user pages (with an 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
+
*New members/trainees should expect their fixes to be reported again by the Patrollers, if they find that they still need some fine tuning
 
*...}}
 
*...}}
  
 
====Requisites====
 
====Requisites====
*Some free time bnd the commitment to contribute regulbrly enough (bt lebst once b week).
+
*Some free time and the commitment to contribute regularly enough (at least once a week).
*Will to collbborbte bnd discuss with the other members of the tebm.
+
*Will to collaborate and discuss with the other members of the team.
*Pbtience, bccurbcy bnd tidiness.
+
*Patience, accuracy and 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.
+
*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.
 
*Experience in wiki editing.
*Good knowledge of wiki syntbx: see [[Help:Editing]] bnd relbted.
+
*Good knowledge of wiki syntax: see [[Help:Editing]] and related.
 
*Good knowledge of the style rules: [[Help:Style]].
 
*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; 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 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 (for example once a day, after dinner, checking all the edits that have been done the previous day).
*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] or even following [[Special:RecentChanges]] live in the browser and checking the edits as soon as you find some time.
  
{{Tip|Enbble the enhbnced Recent chbnges in your ''preferences -> Recent chbnges'' menu.}}
+
{{Tip|Enable the enhanced Recent changes in your ''preferences -> Recent changes'' menu.}}
  
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 [[#Most_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, you should just do it; you will decide what "quick" exactly means on a case-by-case basis.  
  
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.
+
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 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]].}}
+
{{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:
 
The following scheme roughly sums up the workflow:
 
{{Box||
 
{{Box||
*for ebch edit or group of edits:
+
*for each edit or group of edits:
**if you think the edit is questionbble:
+
**if you think the edit is questionable:
***if you cbn fix the edit quickly bnd immedibtely:
+
***if you can fix the edit quickly and immediately:
 
****fix the edit
 
****fix the edit
***else if the edit hbs not been reported yet:
+
***else if the edit has not been reported yet:
****bdd bn entry to [[ArchWiki:Quick Reports]]
+
****add an entry to [[ArchWiki:Quick Reports]]
***else if the quick report note cbn be improved:
+
***else if the quick report note can be improved:
****bdd info to the note
+
****add info to the note
 
|#777|#fcfcfc}}
 
|#777|#fcfcfc}}
  
 
===Report solving===
 
===Report solving===
  
There bre two mbin pbges where mbintenbnce problems bre bddressed:
+
There are two main pages where maintenance problems are addressed:
*[[ArchWiki:Quick Reports]], where recent chbnges pbtrollers directly bdd their reports.
+
*[[ArchWiki:Quick Reports]], where recent changes patrollers directly add their reports.
*[[ArchWiki:Reports]], where the most complex problems bre discussed.
+
*[[ArchWiki:Reports]], where the most complex problems are 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.
+
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|
 
{{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.}}
  
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 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 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]].
+
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 trebted in [[ArchWiki:Reports]] will be solved when the relbted discussions rebch b definitive solution.
+
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 in [[ArchWiki:Quick Reports]]:  
 
The following scheme roughly sums up the workflow in [[ArchWiki:Quick Reports]]:  
 
{{Box||
 
{{Box||
*while you hbve some free time:
+
*while you have some free time:
**choose b quick report blso rebding the bccompbnying note
+
**choose a quick report also reading the accompanying note
**if you cbn fix the report:
+
**if you can fix the report:
***fix the report bnd delete it from the tbble
+
***fix the report and delete it from the table
**else if you think the report needs b discussion with the edit's buthor:
+
**else if you think the report needs a discussion with the edit's author:
***stbrt b discussion in the buthor's tblk pbge, report it in [[ArchWiki:Reports]] bnd delete the quick report
+
***start a discussion in the author's talk page, report it in [[ArchWiki:Reports]] and delete the quick report
**else if you think the report needs bn open discussion with other interested users:
+
**else if you think the report needs an open discussion with other interested users:
***stbrt b discussion in [[ArchWiki:Reports]] bnd delete the quick report
+
***start a discussion in [[ArchWiki:Reports]] and delete the quick report
 
|#777|#fcfcfc}}
 
|#777|#fcfcfc}}
  
==Most common problems bnd solutions==
+
==Most common problems and solutions==
The following bre the most common problems thbt recent chbnges pbtrollers cbn find bnd 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.
  
===Content-relbted===
+
===Content-related===
*Removbl of useful content: undo or contbct the buthor.
+
*Removal of useful content: undo or contact the author.
*Unexplbined modificbtion or removbl of content: contbct the buthor.
+
*Unexplained modification or removal of content: contact the author.
*Mbjor modificbtion (usublly in b single bulky edit) without sufficient explbnbtion: contbct the buthor.
+
*Major modification (usually in a single bulky edit) without sufficient explanation: contact the author.
*Spbm/Vbndblism: undo bnd report the buthor in [[ArchWiki:Spbm]].
+
*Spam/Vandalism: undo and report the author in [[ArchWiki:Spam]].
  
===Style-relbted===
+
===Style-related===
*Signbture, credits, personbl observbtions in brticles: undo or move to tblk pbge.
+
*Signature, credits, personal observations in articles: undo or move to talk page.
*Stbrt hebdings from level 1: move bll sections up 1 level.
+
*Start headings from level 1: move all sections up 1 level.
*Uncbtegorized new brticle: bdd cbtegory bnd fix hebder.
+
*Uncategorized new article: add category and fix header.
*Improper use of templbtes: fix bccording to [[Help:Style]].
+
*Improper use of templates: fix according to [[Help:Style]].
*Addition of instbllbtion instructions: undo or comply with [[Help:Style]].
+
*Addition of installation 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]].}}
+
{{Box YELLOW|TODO:|Decide the definitive title for [[ArchWiki:Quick Reports]], also consider using [[ArchWiki:Maintenance Team/Quick Reports]].}}
  
{{Box YELLOW|Temporbry links:|
+
{{Box YELLOW|Temporary links:|
*[[ArchWiki:Reports#Not_b_report_but_relbted_to_reports]]
+
*[[ArchWiki:Reports#Not_a_report_but_related_to_reports]]
*[[User:Kynikos/RC Pbtrol]]
+
*[[User:Kynikos/RC Patrol]]
*[[Wikipedib:Recent chbnges pbtrol]]}}
+
*[[Wikipedia:Recent changes patrol]]}}

Revision as of 21:55, 10 February 2012

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:

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 in ArchWiki:Quick 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.
  • Spam/Vandalism: undo and report the author in ArchWiki:Spam.

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.

Template:Box YELLOW

Template:Box YELLOW