Revision 31 as of 2016-02-03 14:03:00

Clear message

Software Collections SIG

SIG Status: Approved

Board Member Helping Bootstrap: JimPerrin

The Software Collections SIG will provide an upstream development area for various software collections and related tools. Developers can build on and extend existing SCLs, so they don't need to re-invent the wheel or take responsibility for packaging unnecessary dependencies.

Goals

Resource Requirements

Mailing lists and Communications

Work with the CentOS resources and any discussions around that will take place on the centos-devel mailing list. All work related to SCL, user interactions and upstream development will take place on the existing software collections mailing list.

The SIG is usually available also on irc at #centos-devel on irc.freenode.net.

Sync-up meeting

SIG Membership

The SCLo SIG will have a steering committee and committers. The steering committee will initially consist of:

List of other members is available at https://accounts.centos.org/group/members/sig-sclo.

New committers and members may be added by the steering committee. Steering committee members may interface with the CentOS board via the bootstrapping board member.

Committer privileges, once earned, do not expire unless revoked by the steering committee.

Getting involved

Some tips for active contributors

Roadmap and initial actions

Task list

The following are things that are on the todo list:

This is a list of Software Collections from RHSCL 2.1 and their rebuild status inside SCLo SIG:

collection name

status

depends on

comment

devassist09

{OK} announced

devtoolset-3

{OK} announced ( (!) eclipse missing on centos6)

rh-java-common maven30

devtoolset-4

(!) being build with external deps

rh-java-common maven30

https://bugs.centos.org/view.php?id=9792

git19

{OK} announced

httpd24

{OK} announced

mariadb55

{OK} announced

maven30

(./) published

rh-java-common

only deps for other SCLs, no need to announce

mongodb24

{OK} announced

v8314 rh-java-common maven30

mysql55

{OK} announced

nginx14

{X} built

nginx14 SCL was never considered GA quality, so there are no plans to release it

nginx16

{OK} announced

nodejs010

{OK} announced

v8314

perl516

{OK} announced

php54

{OK} announced

httpd24

php55

{OK} announced

httpd24

postgresql92

{OK} announced

python27

{OK} announced

python33

{OK} announced

rh-java-common

(./) published

maven30

only deps for other SCLs, no need to announce

rh-mariadb100

{OK} announced

rh-mongodb26

{OK} announced

v8314 rh-java-common maven30

rh-mysql56

{OK} announced

rh-nginx18

{OK} announced

rh-passenger40

{OK} announced

ruby193 ror40 ruby200 rh-ror41 rh-ruby22

rh-perl520

{OK} announced

rh-php56

{OK} announced

httpd24

rh-postgresql94

{OK} announced

rh-python34

{OK} announced

rh-ror41

{OK} announced

rh-ruby22 v8314

rh-ruby22

{OK} announced

rh-varnish4

{OK} announced

ror40

{OK} announced

ruby200 v8314

ruby193

{OK} announced

ruby200

{OK} announced

thermostat1

{OK} announced

rh-java-common maven30 rh-mongodb26 v8314

v8314

(./) published

only deps for other SCLs, no need to announce

This is a list of Software Collections that are not part of RHSCL:

collection name

status

depends on

comment

sclo-ror42

(!) in development

rh-ruby22 v8314

Further info about SCLo RoR builds

sclo-vagrant1

{OK} announced

rh-ror41 rh-ruby22

Further info about Vagrant SCL

Requesting CBS tags

If you want to create tags and targets for a new collection follow these steps:

Building packages for SCLo

Currently there is still no dist-git repositories available for the SCLo packages, but we can build packages directly like this:

cbs add-pkg sclo7-rh-mariadb100-rh-candidate --owner=sclo rh-mariadb100-mariadb
cbs build sclo7-rh-mariadb100-rh-el7 rh-mariadb100-mariadb-10.0.18-1.el7.src.rpm

Once build, we want to tag them to the -testing repos,

cbs add-pkg sclo7-rh-mariadb100-rh-testing --owner=sclo rh-mariadb100-mariadb
cbs tag-build sclo7-rh-mariadb100-rh-testing rh-mariadb100-mariadb-10.0.18-1.el7

Then we may test them by installing the packages from CBS repository:

yum-config-manager --add-repo=http://cbs.centos.org/repos/sclo7-rh-mariadb100-rh-testing/x86_64/

When we want to release them, the process is the following:

cbs add-pkg sclo7-rh-mariadb100-rh-release --owner=sclo rh-mariadb100-mariadb
cbs tag-build sclo7-rh-mariadb100-rh-release rh-mariadb100-mariadb-10.0.18-1.el7

The collection naming breakdown

Software collection's name is cohesive identification that was chosen by author and is not supposed to be broke down to separate parts.

However, since the naming usually follows some guidelines, there is an example of sclo-vagrant1 software collection:

A prefix in the collection name:
1) allows "others" (users in particular) to have a distinguishing name per their requirement
2) SCL authors have one "collection name" wherever the collection will appear
3) users (open source projects, paying, whatever) have one collection name to target irrelevant of platform
More on the prefix available at: https://www.redhat.com/archives/sclorg/2015-February/msg00022.html

Further information