Changes

Jump to navigation Jump to search

HOWTO-Admin

3,114 bytes added, 08:40, 4 March 2017
Sync with reality
Adding new members involves the following things (list may not be complete):
* Point out some important rules: follow the [[Code Formatting Conventions]], don't break other people's builds with your commits, ..etc.* Ensure they are subscribed to scummvm-devel* Add them mailing list and suggest subscribing to SF.net scummvm-git-logs list (commit notifications) as project memberswell
** Make sure to also setup appropriate tracker access levels
** Point them to the tracker admin HOWTO below
* Add them to Github as project members.
* Forum: if they have a forum account, make sure it is in group "ScummVM Team"
* Wiki: Make sure they have an account
* Ask them to write an Introduction email to scummvm-devel* ...mailing list
== How to edit/update webpages ==
# Checkout the <code>[https://github.com/scummvm/scummvm-web</code> module scummvm-web] respository from SVN; the current website files are inside "trunk" as usualgithub.
# Edit the relevant files, e.g. for the downloads page edit <code>data/downloads.xml</code>
# Commit your changes as usual
To get any changes you made active on the webserver, you first have to login to open the SF.net shell serverfollowing URL:<syntax type="bash">ssh -t USER,PROJECT@shell.sourceforge.net create</syntax>Thenhttp:<syntax type="bash">cd /home/project-web/www.scummvm/htdocs/.org/site-update.sh</syntax> More detailed instructions can be found in the [https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service relevant sf.net page] (which also has information ask sev for http://www.chiark.greenend.organ account).uk/~sgtatham/putty/ PuTTY] under Windows)
Two important remarks:
# Some content on the webpages needs special treatment, e.g. modifying the credits or adding screenshots. If in doubt, ask on scummvm-devel.
# Not every project member has SSH access to the shell server. Project admins need to explicitly activate the "Allow access to shell server group space" for individual members. Since there is no good way to track who made which changes on the shell server, it seems like a good idea to keep the number of people with direct SSH access small (but not too small).
== How to be a forum moderator ==
TODO[[Forums|Forum]] moderators exist to deal with the everyday administration tasks on the forums found [http://forums.scummvm.org here].<br>This is mainly concerned with enforcing the [http: Explain how //forums.scummvm.org/viewtopic.php?t=17 forum rules].<br>They should also aim to answer user support requests, point users at various FAQs, wiki pages and otherwise deal with questions posted on the forums (though any developer or other forum user may do this as well).<br><p>Spam on the forum is a major issue and any user account which spams junk or commercial messages should have those posts moved to deleted topics or deleted.<br>If the account is obviously a "spammer" account i.e. only messages are spam, e-mail used is listed as a known spammer account, then the account should be deleted and the e-mail address, IP address and/or user name banned to prevent re-registraion. However, some care should be taken to ban in the way least likely to cause issues for other users i.e. banning a single IP is better than a range etc.<br>The IP address used to post can be retrieved by an admin from the post by clicking the IP button on the right hand side of the post. The cross next to that is the post deletion option.<br><br>Due to the volume of automated spambots registering accounts and then spamming, we have various questions and CAPTCHA to try to exclude mass bot registrations.<br>As this proved only partially effective, we have now enabled verification of new user accounts by moderators/admins.<br>When a user registers, an e-mail is sent to all moderators/admins asking them to verify the account. Only after the moderator/admin logs in and then clicks the required link is the account enabled.<br>When checking a user registration, the admin should first check if the e-mail address and/or username are listed as known spammer accounts [http://www.stopforumspam.com here].<br>If not, then a quick Google for the e-mail address and/or username can confirm whether this belongs to a human user properly; with known gaming interest / normal account activity.<br>This should quickly exclude most obvious spammers/spambot registrations and include game interested users with a web presence. However, if the result is still inconclusive, then a judgement call should be made.<br>This will depend on whether the e-mail address is "throwaway" i.e. webmail or other disposable account. We should really reject registrations from disposable accounts such as mailinator.com as they are likely to be problematic in future.<br>Generally though, if unsure, it is best to give the benefit of the doubt and allow the registration, rather than rejecting legitimate users.<br><br>If a user breaks one of the forum rules, some judgement on how to deal with spam; it will be required. However, the following is recommended:* New users may not be aware of the forum rules, so link them to the rules indicating the one that they are violating.* If a user persists in breaking a rule, then it is possible to "give them a warning" by setting this in their user account settings.* If the user still persists or has accumulated three warnings, then disabling their account i.e. banning them is probably warranted.* Locking threads:** Any thread which is violating a forum rule in of itself i.e. asking for non-freeware game download sites etc. should have a message linking the rule and then be locked to prevent further posts.** Locking threads should be used sparingly, but is sometimes required i.e.if a discussion has decended to a flamewar or similar.** In all cases, a message should be posted prior to locking explaining why this has occurred.
== How to triage bug reports ==
We do not have a formal project format and process for doing this, but the following are highly recommended guidelines for dealing with bugs and users reporting bugs:
* Some users prefer to ask informally in the [http://forums.scummvm.org/viewforum.php?f=2 Help and Support Forum] or in the IRC channel about a bug or problem they are having. As an admin or developer, please don't rebuke them for doing this. However, if their problem appears real and is not solved trivially/immediately, then politely suggest that they file a formal bug and link them to the [[Trackers |Bug Tracker]].
* The current [[Trackers]] do not have the ability to send notifications by e-mail or IRC based notifications on keywordsnew bugs to the [[Mailing lists#scummvm-tracker|scummvm-tracker mailing list]], which all developers should be subscribed to. However, so an admin this should not be completely relied upon for notification, especially if the "digest" option is chosen and admins should check the tracker periodically, preferably daily for any new bugs.
* New bugs should have at least a basic reply comment (preferably within a week), even if this is just thanking the bug submitter for the bug submission and indicating that it will take a little time to deal with.
* Any new bug should be assessed for the following:

Navigation menu