Developer Group Roles

Release Leader(s) (RL)

A Release Leader is responsible for a given release, taking it from pre-alpha to gold. The main duty of this role is to ensure that a high quality release is made in a timely fashion. This can be achieved by effective communication with the core developers and efficient use of the community.  One becomes an RL candidate by volunteering or by nomination from the DPM or Core Developers Group.  The RL candidates will be elected by the Core Developers Group at any point in the year when a new initiative makes sense.  The term for an RL will run until the new release is issued.  The RL will work within the group to select a co-Release Leader if severe time constraints come up.

The Release Leader can be the DPM, or if not, needs to work closely with the DPM.

Build Manager

The build manager is responsible for building and signing the RPMs and spinning the ISO.
The build manager is responsible for the tools used to build the RPMs and the ISO.
The build manager has access to the code repository, and should be able to assemble an ISO for testing at any point during the build process.

Contribs Support Manager

The Contribs Support Manager is responsible for providing services to the contribs developer(s)
The Contribs Support Manager will help when requested by the contribs developer(s)
The Contribs Support Manager’s primary duties consist of:
 - Landing a new contrib in Gforge
 - Coordinate with other groups to help find volunteers (if requested)
 - Provide contacts and/or advice to help a contrib become tested and certified* (if requested)

Test Manager

The Test Manager is responsible for maintaining a set of test cases. 
The Test Manager may solicit volunteers (supported by the DPM) to help develop testing scripts.
There can be test cases for testing a new candidate release, and tests for new contribs.
The Test Manager works with the RL to decide the test set to be used for any given release.

Testers

This group of volunteers comprises people who are willing to test SME Server.
They may be testing a candidate release, or new contribs.
The testing may be planned testing following test cases, or ad-hoc testing.
All errors found in the testing should be recorded clearly in the bug database.

There is also a closed sub-team, the Security Team, that will review relevant security issues. It is hoped that there will be some overlap between the core developers group and security sub team.  The roles for this sub team are:

Security Sub team Leader (SSL)

This person shall lead the volunteers associated with security issues for the SME server.
- The SSL skill set should be one of an experienced software engineer. 
- The SSL will determine who is included in this group. 
- The term for the SSL will be two years.  The initial SSL should be a member of, or suggested by and/or a member of, the core developers team.  Subsequent Security Sub team Leaders should be nominated and elected from the Security Sub team Volunteers group.  These rules may be altered by the DPM only if volunteers are not found that meet these criteria.
- The SSL will organize any review of potential candidates prior to their acceptance into this group. 
- The SSL will prepare and present to the community a policy for how security flaws are evaluated, corrected and disclosed.  The scope of the team shall also be described in this policy.  Scope is defined as the boundaries within the five software categories (described above) where security issues will be fixed, and/or if contrib developers will be informed and/or assisted, and/or advisories will be posted after a suitable time period.  This policy must be voted on by the community for initial adoption as well as for any future changes.

Security Sub team Volunteers

This group is the only closed group in the organization for security purposes.
- The number of members is at the discretion of the SSL. . 
- People who volunteer will be reviewed by the SSL and/or other team members prior to acceptance using the common judgment and standards established by the security team. 
- Only security sub team volunteers will vote on SSL elections.  The DPM shall have a tie-breaker vote.
- The term for the volunteers is unspecified, but new recruits should always be encouraged to keep the team at a minimum staffing level (set by the SSL).