New starters

We are always interested in new team members! This explains the criteria for adding a new member and what the process is for adding them in.

Evaluation of proposed team member

- What has their previous attitude been like? Receptive to team's comments?
- What have they got planned as their first tasks? (We do not want to add in more plugins)
- Can we add some testing actions to their first tasks
- Are they interested in handling bug reports and reviewing patches contributed by others?
- Can they look at and review bugs/patches for the plugins they are initially looking at?

Actions to add them to team

Need to know:
- Name
- Primary email for nagiosplug-team mailings
- Sourceforge id
- Type of member (translator, developer, release manager, project administrator)

1. Add member to nagiosplug-team mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-team)
and to the nagiosplug-checkins mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-checkins,
add sourceforge email address via Privacy Options->Sender filters)
2. Add Sourceforge access:
- Translator: Git access, Shell access, Release Tech (no)
- Developer: Project role: Developer, Git access, Shell access, Release Tech (no), Task Manager (A&T),
Forums (Moderator), Doc Manager (Editor)
Update Developer Permissions.
For each tracker, set to Technician (need to add all trackers first, then change to
technician for each one)
3. Add to CVS avail file (deprecated?):
- Translator: Add member to translation files
- Developer: Add member to CVSROOT/avail for all files
4. Send email to nagiosplug-team introducing new member
5. Recommend joining #nagios-devel on Freenode