Changes

'''SME Server Community Constitution'''

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

==Development Guidance==

 

'''Development Guidance'''

The SME Server is a Linux server distribution focused on simplicity, stability, reliability, and security. It is built using only components that have an extensive track record in these areas. The server is designed to be maintained by people with little or no technical background.  

The SME Server is a Linux server distribution focused on simplicity, stability, reliability, and security. It is built using only components that have an extensive track record in these areas. The server is designed to be maintained by people with little or no technical background.  

== Package Categories ==

=== Package Categories ===

The SME Server packages are considered to be sorted into the following categories. Each level requires, but does not influence or control, the levels below it.

The SME Server packages are considered to be sorted into the following categories. Each level requires, but does not influence or control, the levels below it.

When a particular package is built with the intention of being included in a release, the necessity to fork upstream packages must be agreed upon in advance, by a method to be determined by the core developers and the Development Manager (DM).

When a particular package is built with the intention of being included in a release, the necessity to fork upstream packages must be agreed upon in advance, by a method to be determined by the core developers and the Development Manager (DM).

== Additional Package Details ==

=== Additional Package Details ===

 

 

 

== Core Distribution ==

Packages from the base distribution will not be rebuilt. The core infrastructure and smecore will be rebuilt and signed by the community. This means that all packages in the core distribution will be signed.  

Packages from the base distribution will not be rebuilt. The core infrastructure and smecore will be rebuilt and signed by the community. This means that all packages in the core distribution will be signed.  

The community will maintain a copy of all source code that make up the core distribution to be fully compliant with license requirements. It must be possible to build the complete SME Server distribution from these copies.

The community will maintain a copy of all source code that make up the core distribution to be fully compliant with license requirements. It must be possible to build the complete SME Server distribution from these copies.

 

=== Release Cycle ===

== Release Cycle ==

{| class="wikitable"

{| class="wikitable"

It is the responsibility of the maintenance team to make all releases for each of the maintenance branches. The release will be maintained for as long as the base os is maintained which could be for seven years.

It is the responsibility of the maintenance team to make all releases for each of the maintenance branches. The release will be maintained for as long as the base os is maintained which could be for seven years.

== Security Monitoring and Patching ==

=== Security Monitoring and Patching ===

 

All base, core and feature packages will be monitored for security vulnerabilities. Smeaddons packages will be monitored as closely as time and resource constraints permit. Smetest packages will not be monitored for security vulnerabilities.

All base, core and feature packages will be monitored for security vulnerabilities. Smeaddons packages will be monitored as closely as time and resource constraints permit. Smetest packages will not be monitored for security vulnerabilities.

If a table of packages is maintained then people can see for themselves that “sendmail isn’t in the load, so the SME Server is not vulnerable”.  We need to include packages in the smeaddons tree, at least for those available through standard yum channels.

If a table of packages is maintained then people can see for themselves that “sendmail isn’t in the load, so the SME Server is not vulnerable”.  We need to include packages in the smeaddons tree, at least for those available through standard yum channels.

== YUM Repository ==

=== YUM Repository ===

All packages are expected to be distributed via the YUM software. A channel will be maintained for each of the following package types, for each SME Server release, plus any others deemed necessary. Each of the channels will be hosted by at least three mirrors.

All packages are expected to be distributed via the YUM software. A channel will be maintained for each of the following package types, for each SME Server release, plus any others deemed necessary. Each of the channels will be hosted by at least three mirrors.

|}

|}

== GForge ==

=== GForge ===

All smetest and smeaddons packages are expected to be hosted on the the community website using GForge, see http://gforge.org/.  Appropriate provision will be made for packages that are under active development or are actively maintained, as opposed to packages that are simply posted to the site.  A process will be designed to enable developers to request their own space in GForge for each package.

All smetest and smeaddons packages are expected to be hosted on the the community website using GForge, see http://gforge.org/.  Appropriate provision will be made for packages that are under active development or are actively maintained, as opposed to packages that are simply posted to the site.  A process will be designed to enable developers to request their own space in GForge for each package.

Packages hosted elsewhere can be fetched with yum, but will not be included in the standard yum channels.

Packages hosted elsewhere can be fetched with yum, but will not be included in the standard yum channels.

== Smedev & Smeaddons ==

=== Smedev & Smeaddons ===

   

   

A process will be designed to move custom packages between Smedev and Smeaddons. The selected packages will be moved into smetest during this process. At a minimum, the process will ensure that the packages:  

A process will be designed to move custom packages between Smedev and Smeaddons. The selected packages will be moved into smetest during this process. At a minimum, the process will ensure that the packages:  

* Have been determined not to require the modification or replacement of any of the base or core packages

* Have been determined not to require the modification or replacement of any of the base or core packages

== Smeaddons & Smecore ==

=== Smeaddons & Smecore ===

A process will be designed to move custom packages between Smeaddons and Smecore, or directly into the Smecore.  At a minimum, the process will ensure that the packages:  

A process will be designed to move custom packages between Smeaddons and Smecore, or directly into the Smecore.  At a minimum, the process will ensure that the packages: