Changes

'''SME Server Community Constitution'''

<noinclude>[[SME Constitution Main Menu]]</noinclude>

=== Release Leader(s) (RL) ===

 

== 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.

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.

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

==Build Manager==

===Build Manager===

The build manager is responsible for building and signing the RPMs and spinning the ISO.

The build manager is responsible for building and signing the RPMs and spinning 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.

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 ==

=== Contribs Support Manager ===

The Contribs Support Manager is responsible for providing services to the contribs developer(s).

The Contribs Support Manager is responsible for providing services to the contribs developer(s).

* Provide contacts and/or advice to help a contrib become tested and certified* (if requested)

* Provide contacts and/or advice to help a contrib become tested and certified* (if requested)

== Test Manager ==

=== Test Manager ===

The Test Manager is responsible for maintaining a set of test cases.  

The Test Manager is responsible for maintaining a set of test cases.  

The Test Manager works with the RL to decide the test set to be used for any given release.

The Test Manager works with the RL to decide the test set to be used for any given release.

== Testers ==

=== Testers ===

This group of volunteers comprises people who are willing to test SME Server.

This group of volunteers comprises people who are willing to test SME Server.

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:

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) ==

=== Security Sub team Leader (SSL) ===

This person shall lead the volunteers associated with security issues for the SME server.

This person shall lead the volunteers associated with security issues for the SME server.

* 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.

* 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 ==

=== Security Sub team Volunteers ===

This group is the only closed group in the organization for security purposes.

This group is the only closed group in the organization for security purposes.