[CentOS-devel] RFC: Alternative Desktop SIG
fredex at fcshome.stoneham.ma.us
Thu Mar 20 02:22:28 UTC 2014
On Wed, Mar 19, 2014 at 06:09:51PM -0500, Jim Perrin wrote:
> On 03/14/2014 05:44 PM, Stephen John Smoogen wrote:
> > On 14 March 2014 14:49, Jim Perrin <jperrin at centos.org> wrote:
> >> On 03/14/2014 12:26 PM, Stephen John Smoogen wrote:
> >>> I would like to put together an alternative desktop sig which will build,
> >>> qa, and support desktops which are not the Enterprise Linux primary or
> >>> secondary desktops (GNOME and KDE).
> >> Fantastic!
> >>> There are a couple of ground rules I would like to propose:
> >>> 1) Any desktop system needs to have 3 sponsors who are people willing to
> >> do
> >>> the work of building RPMS, coordinating user bugs with upstream, and
> >> fixing
> >>> packages. The reason for 3 is
> >>> a) that this SIG isn't a dumping ground for here is ABC-DE compiled,
> >>> goodbye.
> >>> b) that disagreements between sponsors should be deadlock free.
> >>> c) that when people take vacations, etc there is continuity of
> >> operation.
> >> How would this apply to something like EPEL, which in el6 has XFCE
> >> packaged. Would it be acceptable to pull that in, or would that simply
> >> count as 1 of the 3?
> > That was something that I figured would also need to be planned for. Where
> > do these packages live? Who is caring for them? My initial viewpoint is
> > that it would be nice if the people on a desktop were co-maintainers on the
> > package set if it were in EPEL.
> I proposed exactly this with the fedora maintainer of MATE. He's agreed
> and tagged it appropriately. It's working its way through the EPEL build
> system now.
> The main thing is to try and make sure that
> > stuff gets accidentally abandoned.
> It should only ever be INTENTIONALLY abandoned as the SIG deems
> appropriate ;-)
> >>> 2) Desktops do not keep to Enterprise lifetimes, but major version
> >> changes
> >>> to the desktop need to be announced, tested and released to a schedule.
> >>> Desktops which don't want to do that will not be part of the SIG. [A
> >>> schedule does not need to be super detailed, but just alleviate
> >> surprise.]
> >>> 3) Desktops can and will be removed from the SIG if there isn't an
> >> interest
> >>> in keeping them up. This is mainly to cover that if ABC-DE desktop no
> >>> longer has sponsors, other members of the SIG aren't obliged to support
> >>> ABC-DE if they don't want to.
> >> I would propose that anything being removed be treated as a major
> >> version change, with an announcement and warning for users.
> > Yes I agree on that. It is a major change and would need an announcement
> > and warning to users.
> >>> 4) Some level of governance needs to be established so that there is a
> >>> committee that can make sure that a desktop has 'sponsors', that it is
> >> not
> >>> just code thrown over a wall and left, and that users are not left
> >>> surprised when updates to the desktop occur. They may also make up
> >>> packaging rules and guidelines as needed to alleviate problems that come
> >> up.
> >>> As this is an RFC, these are just proposed rules to be solidified when
> >> the
> >>> CentOS board considers the SIG.
> So lets do a bit of the groundwork so that we can take this SIG to the
> board for vote/approval. Who else has the time and desire to contribute
> to this SIG?
I've previously expressed interest.
I haven't the foggiest idea what kind or amount of work is required, but if it's something I can do I will join up.
---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------
Do you not know? Have you not heard?
The LORD is the everlasting God, the Creator of the ends of the earth.
He will not grow tired or weary, and his understanding no one can fathom.
----------------------------- Isaiah 40:28 (niv) -----------------------------
More information about the CentOS-devel