• SpecialInterestGroup
• SCLo

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

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 [https://www.redhat.com/mailman/listinfo/sclorg software collections mailing list].

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.

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

Further information

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