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 mailing list and suggest subscribing to scummvm-
cvs-logs list (commit notifications) as well * Add them to SF.net as project members
** Make sure to also setup appropriate tracker access levels
** Point them to the tracker admin HOWTO below
# 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: <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:
# 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 ==
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>
TODO: Explain how to ban a user properly; how to deal with spam; ...
== How to triage bug reports ==