[openSLE] Report #1 OpenSUSE LTS/openSLE (Long summary) (fwd)

Boyd Lynn Gerber gerberb at zenez.com
Mon Aug 24 13:25:42 MDT 2009

Below is the report I sent to the opensuse-project ML.  It is a summary of 
the things I have heard so far.  I will be making an other post to sum up 
the variour IRC discussions for this list as time permits.

Boyd Gerber <gerberb at zenez.com> 801 849-0213
ZENEZ	1042 East Fort Union #135, Midvale Utah  84047

---------- Forwarded message ----------
Date: Mon, 24 Aug 2009 13:23:01 -0600
From: Boyd Lynn Gerber <gerberb at zenez.com>
To: opensuse-project at opensuse.org
Subject: Report #1 OpenSUSE LTS/openSLE (Long summary)


Many of us have been thinking about this for years...

openFATE #306982: Create an open SLES


really started the ball rolling on this idea and gave it life.

I am reporting back the significant points from the new ML created.  To sum 
things up...

We need a set of guidelines that must be followed.  These should include...

URL's for the Guidelines we should/must reference are as follows..



We need to define a set of guidelines for either project we choose. These 
guidelines with be used and need to be reveiwed by someone with legal 
knowledge.  Once we define these guidelines we will post them as an RFC to the 
opensuse-project ML.

So to sum things up.

1.  I see us creating a server OS with long lifetime.

2.  Packages have to be 100 % binary compatible with our defined target.
      Only aberrations with removal of trademarks and or legal reasons are

3.  Every change has to be reproducable and tracked via an available SCM.

      I personally prefer GIT.  We need to make sure we keep in mind using
      an OBS as the prefered method of doing the task of building and
      releasing, and other things it provides.  This can be local BS or
      on the OBS.  The GIT GSOC project bsgit(*) provided a great front end
      to the OBS.  may assist us in this task.  The code finish code has to
      be made publically available.

4.  Every code change to the project has to have a SR and the 3 positive
     votes accepting it before it is published.  (Model after openSUSE

5.  We need legal advice on the setup of the packaging guidelines.  (What
     we have to remove to stay legal, and ...
     (Not much in the way of legal would be needed for openSUSE LTS)

6.  The guidelines should be written down and rpmlint checks made where
      possible to insure we abide by the guidelines and avoid legal issues.

There are basically two choices as the subject reports.

1.  openSUSE LTS	A longer life spam of openSUSE releases.
2.  openSLE(S,D)	A binary compatible with SLES/SLED

More information about the OpenSLE mailing list