Jump to: navigation, search

Difference between revisions of "OpenStack SIGs"

(OpenStack SIGs (Special Interest Groups): add list header)
(47 intermediate revisions by 8 users not shown)
Line 1: Line 1:
__TOC__
+
= OpenStack SIGs (Special Interest Groups) =
  
== Purpose ==
+
OpenStack SIGs (Special Interest Groups) are teams within the community where we collaborate to bring unified discussions for all community members who share a common interest. As examples SIGs can be but are not limited to being a first stage in the development of new projects, feature requests, standards adoption, policy implementation, adjacent community work, and just general discussion(s).
OpenStack SIGs are teams within the community where we collaborate to bring unified discussions for all community members who share a common interest. As examples SIGs can be but are not limited to being a first stage in the development of new projects, feature requests, standards adoption, policy implementation, adjacent community work, and just general discussion(s).
 
  
== Current SIGs ==
+
== List of SIGs ==
=== Meta ===
 
  
== Proposed SIGs ==
+
You can find the list of current SIGs and other information about SIGs at the SIGs website:
=== Ansible ===
+
'''https://governance.openstack.org/sigs/'''
 +
 
 +
== Communication ==
 +
__NOTOC__
 +
 
 +
SIGs are not restricted in the methods and tools they use to communicate. We do however want to provide guidelines which may help those SIGs who need direction and/or assistance for onboarding.
 +
 
 +
=== Bi-weekly Newsletter/Summary ===
 +
In an effort to reduce the work on individuals writing and/or reading summaries for SIGs we are offering to follow a great tradition started for openstack-dev ML by having a bi-weekly summary sent out. In order to succeed here we have an etherpad - https://etherpad.openstack.org/p/openstack-sigs-weekly - which will be compiled bi-weekly and sent to the openstack-sigs ML and other relevant places. We ask that SIG leaders provide updates as they see fit to the etherpad; this is not a requirement.
 +
 
 +
=== non-IRC Messaging ===
 +
IRC is the preferred method of communication as it aligns with historical and current OpenStack community best practices for simple messaging; required for TC governed projects. It is understood that for some IRC does not come with enough features by default and programming a bot to offer additional features is beyond some; skill or patience to create/maintain. If a SIG does decide to use an alternative to IRC, we ask that in keeping with the Four Opens, in particular Open Community, that you do so by ensuring meeting logs are stored/archived.
 +
 
 +
==== Slack ====
 +
 
 +
Free team accounts with Slack are not sufficient enough to meet archiving/storage of logs alone. A great alternative is to connect Slack with IRC and then follow the instructions for logging an IRC channel. Refer to https://github.com/ekmartin/slack-irc for a Slack+IRC connector; a docker image is also available at https://github.com/mrhillsman/dockerize-slack-irc
 +
 
 +
=== Mailing List ===
 +
Currently we have the OpenStack-SIGs mailing list which you can sign up for here: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
 +
When using the mailing list, be sure to add the tag [topic] at the beginning of your subject line. An example of this can be found here: http://lists.openstack.org/pipermail/openstack-sigs/2017-July/000000.html
 +
( the [Openstack-sigs] tag in the example is added by the Mailman software that drives OpenStack mailing lists )

Revision as of 14:51, 6 March 2018

OpenStack SIGs (Special Interest Groups)

OpenStack SIGs (Special Interest Groups) are teams within the community where we collaborate to bring unified discussions for all community members who share a common interest. As examples SIGs can be but are not limited to being a first stage in the development of new projects, feature requests, standards adoption, policy implementation, adjacent community work, and just general discussion(s).

List of SIGs

You can find the list of current SIGs and other information about SIGs at the SIGs website: https://governance.openstack.org/sigs/

Communication

SIGs are not restricted in the methods and tools they use to communicate. We do however want to provide guidelines which may help those SIGs who need direction and/or assistance for onboarding.

Bi-weekly Newsletter/Summary

In an effort to reduce the work on individuals writing and/or reading summaries for SIGs we are offering to follow a great tradition started for openstack-dev ML by having a bi-weekly summary sent out. In order to succeed here we have an etherpad - https://etherpad.openstack.org/p/openstack-sigs-weekly - which will be compiled bi-weekly and sent to the openstack-sigs ML and other relevant places. We ask that SIG leaders provide updates as they see fit to the etherpad; this is not a requirement.

non-IRC Messaging

IRC is the preferred method of communication as it aligns with historical and current OpenStack community best practices for simple messaging; required for TC governed projects. It is understood that for some IRC does not come with enough features by default and programming a bot to offer additional features is beyond some; skill or patience to create/maintain. If a SIG does decide to use an alternative to IRC, we ask that in keeping with the Four Opens, in particular Open Community, that you do so by ensuring meeting logs are stored/archived.

Slack

Free team accounts with Slack are not sufficient enough to meet archiving/storage of logs alone. A great alternative is to connect Slack with IRC and then follow the instructions for logging an IRC channel. Refer to https://github.com/ekmartin/slack-irc for a Slack+IRC connector; a docker image is also available at https://github.com/mrhillsman/dockerize-slack-irc

Mailing List

Currently we have the OpenStack-SIGs mailing list which you can sign up for here: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs When using the mailing list, be sure to add the tag [topic] at the beginning of your subject line. An example of this can be found here: http://lists.openstack.org/pipermail/openstack-sigs/2017-July/000000.html ( the [Openstack-sigs] tag in the example is added by the Mailman software that drives OpenStack mailing lists )