Processes for joining or leaving team members
Admin tasks to do when someone joins or leaves the FSFE. This can be volunteer core team members, interns, staff, or GA members.
If the person leaves the FSFE or her employment ends, you have to revert most or all steps.
1. FSFE account
In the latter case, the account has to be manually activated. Ask them to write an email to email@example.com to make the account managers aware of it. They should then report back to you to allow you to execute the next steps.
2. Mailing Lists
Add the person to important mailing lists, depending on her position:
Intern/Employee: team@, staff@
GA: team@, ga@
On the server list1, you can run find_member firstname.lastname@example.org to check a person's membership of possibly sensible mailing lists.
3. LDAP team group
Add the new team member (being in the European core team, an intern or an employee) to the "team" group in the LDAP database
Log into the LDAP server (berzelius) and run
ldapvi -D 'cn=admin,dc=fsfe,dc=org' -b 'ou=groups,dc=fsfe,dc=org'
For each CN, there is a separate section. Add the person to the appropriate sections.
GA: team, ga
More info about ldapvi at: SVN:/sysadmin/Documentation/Services/LDAP/ldap_admin.txt.
4. Access to the wiki internal pages
In order to allow users to access restricted pages, you have to add them to Wiki groups by adding their FSFE accout name in a list. Please note that usernames are case sensitive!
These pages define a group of wiki users that have access to some restricted pages (usually dealing with internal team matters). See this page for further instructions.
Employees have to and interested core team members can be member of the chitchat XMPP room.
Room moderators have to add the jabberid to the access list of the room. This can be done via XMPP clients.
OTRS is our ticket system. Please add the person to the relevant queues.
Team: depends on individual interests and positions
Employee: depending on work areas
System Hackers: System Administrators
GA: depends on individual interests and positions
If a person leaves, please make sure to transfer ownership of the remaining open tickets to someone else.
7. SVN repositories
Add the new person to the "fsfe-team" list in the file /etc/apache2/svn/svnaccess on auer. The other groups are not relevant any more except for new system administrators. Please note that usernames are case sensitive!
Internal SVN repository: point the person to the usage instructions at https://wiki.fsfe.org/Internal/SVN.
8. Git / Gitea teams
Since some of our files and knowledge resides on git.fsfe.org, new people have to be added to some teams in order to access their repositories. Please note that you can only add users who logged in to Gitea at least once.
9. Welcome message
Send the Welcome Message to the new team member, replacing the FILLME placeholders with proper values.
When someone leaves
Please do the opposite for all the things explained above.
System Hackers coordinators and the FSFE Council can review this repository to see access reports.
Also, when people are leaving the organization, they sometime want to keep working for FSFE as volunteers. Please ask the person if he / she wants to keep some user account to keep doing things as a volunteer.