Revision 12 as of 2015-10-28 16:54:34

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:

Other members are:

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 Collectoions from RHSCL 2.1 and their rebuild status inside SCLo SIG:

collection name

status

depends on

comment

devassist09

{*} built

devtoolset-3

{*} built

rh-java-common maven30

devtoolset-4

(!)

rh-java-common maven30

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

git19

{*} built

httpd24

{*} built

mariadb55

{*} built

maven30

{*} built

rh-java-common

mongodb24

{*} built

v8314 rh-java-common maven30

mysql55

{*} built

nginx14

{*} built

nginx16

{*} built

nodejs010

{*} built

v8314

perl516

{*} built

php54

{*} built

httpd24

php55

{*} built

httpd24

postgresql92

{*} built

python27

{*} built

python33

{*} built

rh-java-common

{*} built

maven30

rh-mariadb100

{*} built

rh-mongodb26

{*} built

v8314 rh-java-common maven30

rh-mysql56

{*} built

rh-nginx18

(!)

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

rh-passenger40

{*} built

ruby193 ror40 ruby200 rh-ror41 rh-ruby22

rh-perl520

{*} built

rh-php56

{*} built

httpd24

rh-postgresql94

{*} built

rh-python34

{*} built

rh-ror41

(./) published

rh-ruby22 v8314

rh-ruby22

(./) published

rh-varnish4

(!)

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

ror40

{*} built

ruby200 v8314

ruby193

{*} built

ruby200

{*} built

thermostat1

{*} built

rh-java-common maven30 rh-mongodb26 v8314

v8314

(./) published

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

collection name

status

depends on

comment

sclo-vagrant1

(./) published

rh-ror41 rh-ruby22

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:

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

Further information