Just to bump this along a bit. (yes, I'm top-posting) I'd like to flesh out http://wiki.centos.org/SpecialInterestGroup/AlternativeDesktop a bit more. I'd still like to see one or two more folks with some decent rpm/yum building experience volunteer, and some idea of deliverables. examples/thoughts - enabling epel/elrepo by default. - import epel's cinnamon / mate packages for install media - distributable install media. - xxx - yyy I'd like to get this hammered out in time to discuss in this week's board meeting. 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). > > 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. > 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. > 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. > > > > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel > -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77