#acl HonzaHorak:read,write,delete,revert,admin Default

== 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 ===

 * Act as upstream git repository for [http://www.softwarecollections.org SoftwareCollections.org]
 * Work with developers to accept contributions for newer software collections.
 * Establish release management duties  to act as gateway to build/sign/distribute packages.
 * Build and distribute software collections packages via centos.org as well as [http://www.softwarecollections.org SoftwareCollections.org]
 * Work with upstreams like OpenShift Origin and foreman to provide compatibility. 

=== Resource Requirements ===
 * Full control of project space on [http://git.centos.org] - sig-sclo or similar.
 * Rights for SIG release engineering to SIG branch under the /rpms namespace on [http://git.centos.org] for builder access / control
 * Build privileges and related targets for [http://cbs.centos.org/koji]
 * Ability to sign packages for distribution
 * Possible use of [http://bugs.centos.org] for tracking

[[Anchor(communications)]]
=== Mailing lists and Communications ===

Work with the CentOS resources and any discussions around that will take place on the [http://lists.centos.org/mailman/listinfo/centos-devel centos-devel mailing list]. All work related to SCL, user interactions and upstream development will take place on the existing [https://www.redhat.com/mailman/listinfo/sclorg software collections mailing list].

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

[[Anchor(sync-up-meeting)]]
==== Sync-up meeting ====
 * at least in the beginning we hold (almost) weekly meeting on irc at #centos-devel on irc.freenode.net
 * currently the meeting is held on Wednesday, 4pm UTC
 * invitation to the irc meeting is sent to both mailing lists above usually one day before

=== SIG Membership ===

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

 * Brian Gollaher
 * Honza Horak
 * Radek Vokal
 * Joe Orton
 * Adam Miller
 * ThomasOulevey

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.


[[Anchor(getting-involved)]]
=== Getting involved ===
 * see [#communications mailing lists and other communication channels info]
 * simple contribution doesn't require access to the dist-git and CentOS Build System (CBS)
 * have you some bug reports, patches to contribute, other things to discuss, use the [https://www.redhat.com/mailman/listinfo/sclorg sclorg@redhat.com] mailing list until there are some better ways (still working on this)

==== Some tips for active contributors ====

 * get familiar with the [https://www.softwarecollections.org/en/docs/guide/ Software Collections guidelines] and [https://fedoraproject.org/wiki/Packaging:Guidelines Fedora Packaging Guidelines]
 * send introduction to the mailing list above (share some basic info about yourself, your intentions within SCLo SIG, which collection you plan to help with)
 * for gaining access to CentOS Build System, follow steps at http://wiki.centos.org/HowTos/CommunityBuildSystem


=== Roadmap and initial actions ===

 * Define initial package set and deliver binaries.
 * Establish git workflow
 * Define criteria for contributions
 * Provide documentation for community users as well as contributors
 * Establish policy/practice for bug submissions
 * Set release cadence and upgrade policies


=== Task list ===

This is a list of Software Collectoions from RHSCL 1.2 that are ordered according to its importance based on their download statistic and inter-collections dependencies. We can simply start with collections from top.

##begin-tasks
|| '''collection name''' || '''built in sclX--testing tag?''' || '''built in sclX-release tag?''' || '''comment''' ||
|| v8314 || {X} || {X} || ||
|| ruby193  || {X} || {X} || needs v8314 ||
|| php55 || {X} || {X} || ||
|| python27 || {X} || {X} || ||
|| httpd24 || {X} || {X} || ||
|| postgresql92 || {X} || {X} || ||
|| mariadb55 || {X} || {X} || ||
|| php54 || {X} || {X} || ||
|| python33 || {X} || {X} || ||
|| nginx14  || {X} || {X} || ||
|| ruby200  || {X} || {X} || needs v8314 ||
|| ror40  || {X} || {X} || needs ruby200 ||
|| perl516 || {X} || {X} || ||
|| devtoolset-3 || {X} || {X} || ||
|| nodejs010 || {X} || {X} || ||
|| maven30 || {X} || {X} || ||
|| mongodb24  || {X} || {X} || needs v8314, maven30 ||
|| mysql55 || {X} || {X} || ||
|| nginx16 || {X} || {X} || ||
|| devassist09 || {X} || {X} || ||
|| git19 || {X} || {X} || ||
|| thermostat1  || {X} || {X} || needs mongodb24 ||
##end-tasks

=== Further information ===

 * [http://www.softwarecollections.org SoftwareCollections.org]

=== TODO list for this page ===
 * proper example for SCM request at bugs.c.o
 * some real example of building RPMs for SCLo