Difference between revisions of "HOWTO-Admin"

Jump to navigation Jump to search
2,329 bytes added ,  08:40, 4 March 2017
Sync with reality
(Sync with reality)
 
(4 intermediate revisions by 2 users not shown)
Line 4: Line 4:
Adding new members involves the following things (list may not be complete):
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.
* 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 mailing list and suggest subscribing to scummvm-cvs-logs list (commit notifications) as well
* Ensure they are subscribed to scummvm-devel mailing list and suggest subscribing to scummvm-git-logs list (commit notifications) as well
* Add them to SF.net as project members
** Make sure to also setup appropriate tracker access levels
** Make sure to also setup appropriate tracker access levels
** Point them to the tracker admin HOWTO below
** Point them to the tracker admin HOWTO below
Line 18: Line 17:
# Commit your changes as usual
# Commit your changes as usual


To get any changes you made active on the webserver, you first have to login to the SF.net shell server:
To get any changes you made active on the webserver, open the following URL: http://www.scummvm.org/site-update/ (ask sev for an account).
<syntax type="bash">ssh -t USER,PROJECT@shell.sourceforge.net create</syntax>
Then:
<syntax type="bash">
cd /home/project-web/scummvm/htdocs/
./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 for [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] under Windows)


Two important remarks:
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.
# 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 ==
== How to be a forum moderator ==
Line 35: Line 26:
This is mainly concerned with enforcing the [http://forums.scummvm.org/viewtopic.php?t=17 forum rules].<br>
This is mainly concerned with enforcing the [http://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>
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>
TODO: Explain how to ban a user properly; how to deal with spam; ...
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 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 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 ==
== How to triage bug reports ==

Navigation menu