Overview of Initiative
Initiative Overview
This all started with openFATE 306982 [1] and openSUSE moving from a 24 month cycle to an 18 month cycle.
openSUSE[2] and SUSE Linux Enterprise Desktop (SLED) [3] provide a good Desktop solution. So there will be no openSLED option.
There are basically four options.
- openSUSE [4] Server CD: Server Edition, somewhat alike the GNOME and KDE media https://features.opensuse.org/305664.
- openSUSE [5] LTS longer term security and support, community driven complete release.
- openSUSE [6] LTS subset (a reduced core of openSUSE[7]) with mainly Server SW.
- openSLES a CentOS equivalent for SLES[8] based on SUSE Linux Enterprise[9].
We need a set of guidelines based on openSUSE Packaging[10] and Fedora Packaging Guidelines [11]. Once we finish the guidelines we will need rpmlint checks where possible for the guidelines.
These guidelines will need another review by someone with the legal knowledge to assist us to make sure we are following all the proper rules and regulations. The finished code has to be made public.
We should model our initiative after the openSUSE[12] factory. Every code change to the selected option, should have an Server Request (SR) created and receive 3 positive comments or votes before accepting and publishing it.
It should be binary compatible with our defined target. Only aberrations with removal of trademarks, branding and/or legal reasons are allowed.
Every change has to be reproducible and tracked with an available SCM. I think we should use git for this purpose. Depending on our choice we may need to setup our own local Build Service (BS). The GIT GSOC project bsgit [13] could assist us in this project. We maybe could work with the openSUSE Team[14] or other teams or individuals to do a back end interface for a complete git solution.
Pro's and Con's for each option of the initiative:
Novell® is a registered Trademark.
SUSE® is a registered Trademark.
openSUSE® is a registered Trademark
