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

Proposal

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

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

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

Acceptance

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

Community Buildsystem

Prerequisites

We provide a set of tools in the CentOS-Extras repository for building SIG packages in the Community Build System. If your development workstation is running CentOS 7:

    yum install centos-packager

Many of these tools will become the building blocks for Centpkg (HowTos/Centpkg).

If your workstation is on Fedora (23/24/25) there is a Copr available:

    dnf copr enable bstinson/centos-packager
    dnf install centos-packager

Step 1: Signing up for an account
  1. Visit the Accounts System

  2. Select 'New Account'
  3. Fill out the form with your information

Step 2: Join a Special Interest Group

Your account will not be active in CBS until you are a member of a SIG

  1. After signing in to accounts.centos.org, choose 'Group List' and locate the SIG you are interested in joining. (SIGs are listed under 's', for example, 'sig-cloud'.)
  2. Apply for membership
  3. Speak with your SIG Chair to have your request approved

Step 3: Generating your user certificate

Your user certificate bundle comes in the form of 3 files:

Filename

Purpose

~/.centos.cert

PEM file with your X509 Client Certificate and Key

~/.centos-ca.cert

The CA Certificate from FAS

~/.centos-upload-ca.cert

The CA Certificate for the lookaside

To generate your certificate you can use the 'centos-cert' tool included in the centos-packager package:

  Usage: centos-cert [OPTIONS] 

Options:
  -h, --help            show this help message and exit
  -u USERNAME, --username=USERNAME
                        ACO Username.
  -n, --new-cert        Generate a new User Certificate.
  -f CERTFILE, --file=CERTFILE
                        User Certificate.
  -v, --verify-cert     Verify Certificate.

If you've signed up with the account name tuser, you can generate your new certificate like this:

    [tuser@myworkstation]$ centos-cert -u tuser -n
    FAS Password: <password_goes_here>

Attention that centos-cert -u tuser -n will request a new certificate, so that will automatically revoke any other certificate you had in the past. If you need to use cbs/koji on multiple machines, just copy the files mentioned above on the other machine.

Step 3.1: Renewing your certificate

/!\ Your user certificate is valid for 6 months. If your certificate expires and you do not renew it after another 4 months, your account will be disabled in accounts.centos.org

To renew your certificate:

    [tuser@myworkstation]$ centos-cert -u tuser -n
    FAS Password: <password_goes_here>

ci.centos.org

Open a Bug
  1. Visit https://bugs.centos.org/

  2. Report an Issue under the buildsys project
  3. Select the 'Ci.centos.org Ecosystem Testing' Category
  4. Include the following information in your report:
    • Your Name
    • The project you are working with
    • Your Desired Username
    • Your Email Address
    • Your ssh pubkey (attach this to the bug please)

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

Devcloud

Requesting Resources

Content Signing Key

Mailing Lists

IRC Channels

Bug 'Projects' in bugs.centos.org

The SIG Sponsor (board member) handles requests for a SIG Project in https://bugs.centos.org. A 'project' is a collection of bug categories that can be assigned to members of the SIG.

Some basic strategies for assigning categories:

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

SIG Bot accounts for CBS

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

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.

CBS Tags

To request new tags in CBS open a bug Project: Buildsys Category: community buildsys

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

SIG:

Cloud

Project:

Openstack

Release String:

Kilo

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.

Meetbot Commands

We'll use some examples from previous CBS meetings.

Command

Description

Sample usage

#startmeeting <name_of_your_meeting>

Tells centbot to begin a meeting

#startmeeting CBS/Infra

#endmeeting

Ends the currently running meeting

#endmeeting

#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

Publishing the Minutes

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

SIGGuide/SIGProcess (last edited 2018-09-24 18:17:53 by AnssiJohansson)