FlightGear wiki:Notes to administrators: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (+ Periodically recurring tasks, see discussion page)
m (Proper headings; Clarification; etc)
Line 15: Line 15:
== Periodically recurring tasks ==
== Periodically recurring tasks ==
{{stub|section=1}}
{{stub|section=1}}
=== Newsletter releases ===
* Layout fixes (Does not have to be done by an administrator per see)
* Creating the next newsletter (Does not have to be done by an administrator per see)
* Edit protection


* Newsletter releases
=== FlightGear releases ===
** Layout fixes (Does not have to be done by an administrator per see)
: ''See also [[Release Plan|release plan]].''
** Creating the next newsletter (Does not have to be done by an administrator per see)
* Updating development repository status templates
** Edit protection
 
* FlightGear releases (see also [[Release Plan|release plan]])
** Development status templates


== Maintenance categories ==
== Maintenance categories ==

Revision as of 20:27, 23 June 2014

This is a collection of notes to administrators to help them with the maintenance that regular users can not do.

Common tasks

Deletion

See also {{delete}} and {{delete-sp}}.
  • Before deletion check the page history.
  • An old page with lot of edits and views should probably not be deleted, but instead be turned into a redirect to a page that have a similar subject. Also, deleting a well visited page can cause a lot of broken links on the forum.

Deleting spam and blocking spammers

  • Newly registered users whose first and only contribution clearly and unambiguously was spam can safely be blocked indefinitely and have the contributions deleted.
  • Make sure the edit summary does not contain the offending links and other content, just the word "Spam" and possibly a few words more.

Periodically recurring tasks

This section is a stub. You can help the wiki by expanding it.

Newsletter releases

  • Layout fixes (Does not have to be done by an administrator per see)
  • Creating the next newsletter (Does not have to be done by an administrator per see)
  • Edit protection

FlightGear releases

See also release plan.
  • Updating development repository status templates

Maintenance categories