[FrontPage] [TitleIndex] [WordIndex

This is a read-only archived version of wiki.centos.org

Anyone may propose and/or participate in a Special Interest Group, here are some guidelines and tips related to the workings of a SIG.


Creating a new SIG requires participation from a member of the CentOS Governing Board, and a SIG must meet some requirements:

1. Requirements

  1. The topic must be related to CentOS, or a use scenario for CentOS
  2. There must be adequate control and feedback into the CentOS community
  3. Generally all communication as to the work of the SIG should be public, understanding that sometimes a matter may need to be private. In such cases, please consult with the sponsoring Governing Board member
  4. All code produced within the SIG must be compatible with a FOSS license presently used by CentOS
  5. All documentation produced within the SIG Must be compatible with the license of this wiki
  6. SIGs should be mindful of general CentOS directions from the Governing Board
  7. One member of the SIG should be a member of the Governing Board/Devteam

2. The Proposal Process

  1. Check to see if the topic of collaboration is already covered by an existing SIG
  2. Post an introductory 'RFC' email to the centos-devel mailing list and ask for comments
  3. Find a CentOS Governing board member to join the effort
  4. The board member will:
    1. Request any initial resources be created
    2. List the SIG on the SpecialInterestGroup page in the wiki


The sponsoring member of the Governing board will put the proposal at a regularly scheduled board meeting. The Board will, if the proposal is accepted, give its charter to the SIG to begin its work.

SIG founders should stay in close contact with their sponsor through this process to work out any questions arising from the proposal.

Account Setup

1. Community Buildsystem

Building in CBS

0.1. Prerequisites

To be able to submit tasks/builds to https://cbs.centos.org, you need first :

For all the steps, consider reading the Authentication dedicated wiki page

1. ci.centos.org

1.1. Open a Bug
  1. Visit https://pagure.io/

  2. Report an Issue under the centos-infra tracker https://pagure.io/centos-infra/issues/

  3. Include the following information in your report:
    • Your Name
    • The project you are working with
    • Your Desired Username
    • Your Email Address
    • Your gpg pubkey (should be already in ACO normally)

1.2. Account Approval

Special Interest Group Members: Contact your SIG Chair to comment his/her approval on the bug

Upstream Projects: We will work with you to designate a coordinator to approve new members of your project in ci

2. Devcloud

Requesting Resources

1. Content Signing Key

2. Mailing Lists

3. IRC Channels

4. Bug 'Projects' in tracker

The SIG Sponsor (board member) handles requests for a SIG Project in https://pagure.io/centos-infra/issues/.

The SIG should agree on this at a regularly scheduled meeting and contact the sponsor for next steps.

5. SIG Bot accounts for CBS

Some SIGs may want to use a bot account for automated builds in CBS from CICO or other infrastructures.

5.1. Requirements
  1. The account name is the shortname of the sig (cloud, configmanagement, cloudinstance) etc
  2. The email on the account must be deliverable to someone who can change the certificate in the production environment

The account approval process follows the usual sponsorship model. Be sure to notify one of the ACO admins and they will sponsor the account into the appropriate group.

6. CBS Tags

To request new tags in CBS open a request

Be sure to include the following information:

Tags in CBS follow the following format: <signame><centos_version>-<project>-<release_string>-{candidate,release,testing}

Example: cloud7-openstack-kilo-testing





Release String:


If the requestor is not the SIG Chair, the Chair should comment on the bug with a +1 or -1 to approve or deny the new tags.

Daily Workings (Meetings)

Running a SIG Meeting can be much easier with an agenda, and a few snippets for calling out things for the minutes.

1. Meetbot Commands

We'll use some examples from previous CBS meetings.



Sample usage

#startmeeting <name_of_your_meeting>

Tells centbot to begin a meeting

#startmeeting CBS/Infra


Ends the currently running meeting


#chair <list_of_nicks>

Meetbot chairs can do administrative commands (like #undo, #agreed, #topic). The person who starts the meeting is automatically a chair

#chair alphacc Arrfab kbsingh

#topic <text>

Starts a topic for discussion. This shows up as a section in the Meeting Summary portion of the minutes

#topic Status Updates

#info <some_text>

Adds a line in the Meeting Summary under the currently active topic

#info First Config Management SIG Meeting: Wed Mar 23 16:00:00 UTC 2016 in #centos-devel

#action <nick_of_someone> <todo_item_they_should_do>

Registers a todo item for the named person

#todo bstinson to follow up on the arm64 builder

#agreed <something_the_group_decided>

This announces a decision of the group, reached by either a vote or by lazy consensus

#agreed The meeting time will be 14h00 UTC

2. Publishing the Minutes

After the meeting is closed, your minutes will show up under: http://www.centos.org/minutes/

2023-09-11 07:23