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.



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


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

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 inside SCLo SIG and their status: [/CollectionsList]

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, the CI should run the sanity tests and then we may tag them to the -testing repository, like this:

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

Putting packages to the testing repository

There is a workflow, that grabs all packages tagged with -testing tag every few hours and make them available at the testing repository at [].

In order to happen that way, every collection must be added to the workflow, only for the first time, by creating a ticket like this: []. Then, users may install it by installing and enabling the following repo:

yum-config-manager --enable centos-sclo-rh-testing

Releasing the packages

When we want to release the packages, the process is similar as releasing in the testing repository, i.e. 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:

Further information

SpecialInterestGroup/SCLo (last edited 2016-02-03 14:33:20 by HonzaHorak)