ESE205 Wiki:Administrators
Congrats! If you are reading this then it is very likely that you are a new administrator and you don't know how to administer this wiki. This page should address most of your questions.
Contents
Wiki Configuration
This wiki is hosted in EIT's project web server. If you are the new lecturer for this course, contact Mark Bober at EIT to change ownership of the main web source files.
Once you have ownership of the files, you can access them logging in ssh.seas.wustl.edu using your WUSTL account. The source files are located at /project/class-www/engineering/ese205. That folder is a bit of a mess, but all the relevant content is located in the core folder, which is in itself a git repository.
The most important (and almost only) configuration file is LocalSettings.php located in the core folder. In particular, when you take ownership of the wiki web source files you should edit LocalSettings.php and change the following variables to your email address, so you will get notifications when relevant or bad things happen:
- $wgEmergencyContact
- $wgPasswordSender
- $wgAccountAdministrator
- $wgConfirmAccountContact
Beginning of the Semester Maintenance
Create Class Group
Each user belonging to a particular class (either TAs or students) should become members of a particular, to help administer old wiki pages.
To create a class group, edit LocalSettings.php and add a line below the comment ## Create student group of the form:
$wgGroupPermissions['SP2017'] = $wgGroupPermissions['user'];
where SP2017 is the name of the group for Spring 2017.
Change Permits of TA users
The TAs should become members of the groups administrators, bureaucrat, staff groups. One way to add the users to these groups is:
- Go to the ListUsers page.
- Click on the TAs user name.
- Click on the User rights management link on the sidebar of the user's wiki.
- Select the desired groups for that user, and click the Save user groups button.
Define Demo Session Schedule and Reserve Space
The demo session is, by far, the most important event in the semester. To avoid conflicts, the schedule for the demo session should be defined before the first day of class, so students can check their agendas and adjust to potential conflicts. Traditionally the demo session happen at lunch time of the last Tuesday of the semester in the Lopata Hall gallery, but this is just a suggestion.
To reserve a space that can fit all the groups, their posters, and visitors, you should use the WUSTL event reservation system.
Update the Administrative Guidelines
There is a number of guidelines that contain useful information for students, such as how to print a poster, how to write a proposal, or how to reimburse in the ESE department. Minor updates must be made to these guidelines to refresh the information. In particular, here is a lines of the changes that must be made to the guidelines (note that this list is by no means exhaustive):
- Demonstration Session Guidelines: Change current semester and demo session schedule.
- ESE Reimbursement Process: Change maximum budget, if necessary.
- Final Report Guidelines: Change deadline (currently appears twice in the page).
- New Student Checklist: Change current semester in the text and in the snippets of code to add pages to the relevant categories.
Authorizing new accounts
All the new users, students and TAs, must create a wiki account, as described in New Student Checklist.
Once they request an account, the email address listed in $wgConfirmAccountContact will receive an email (or several, the extension running the user confirmation system is not very clever).
Accounts can be authorized, rejected, or put on hold, using the ConfirmAccounts page, which can only be accessed by members of the administrators group.
No account should be authorized until an email address is confirmed, this is an important rule that should be enforced, otherwise it is very hard to distinguish real accounts from spam.
Once an account is created, a similar procedure as that in #Change Permits of TA users should be used to add every single one of them to the corresponding class group. This is painful and slow (thanks Obama!), but worthwhile in the long run.
