Jump to: navigation, search

Latest revision as of 20:57, 7 August 2020

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-discuss 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-Discuss mailing list which you can sign up for here: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss 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 )

Retrieved from "https://wiki.openstack.org/w/index.php?title=OpenStack_SIGs&oldid=175839"

@@ Line 1: / Line 1: @@
-= OpenStack SIGs =
+= OpenStack SIGs (Special Interest Groups) =
-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). Here is the list of current SIGs:
+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).
-{| class="wikitable sortable"
+== List of SIGs ==
-|-
-! SIG !! Scope !! ML prefix !! Contact !! Other resources
-|-
-| '''[[API Working Group|API]]''' || Formerly known as the API-WG, the API SIG scope is to improve the developer experience of API users by converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow for new development, and promotes convergence of new APIs and future versions of existing APIs. || [api] || Chris Dent, Ed Leafe, Michael McCune || Meeting [http://eavesdrop.openstack.org/#API_Working_Group]
-|-
-| '''Meta''' || The SIG for SIGs so to speak. A SIG to discuss OpenStack SIGs themselves, to encourage workgroups to become SIGs, accompany them along the way, give them tools and processes to be efficient. More generally, this SIG will discuss how to best close the loop between users and developers of OpenStack. || [meta] || Melvin Hillsman (mrhillsman), Thierry Carrez (ttx) ||
-|}
+You can find the list of current SIGs and other information about SIGs at the SIGs website:
+'''https://governance.openstack.org/sigs/'''
-== SIG overview ==
+== Communication ==
-=== 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.
-==== Mailing List ====
+=== Bi-weekly Newsletter/Summary ===
-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
+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-discuss ML and other relevant places. We ask that SIG leaders provide updates as they see fit to the etherpad; this is not a requirement.
-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 )
+=== 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.
-== Proposed SIGs ==
+==== Slack ====
-=== Ansible ===
-'''Status''': Forming (Proposal: http://lists.openstack.org/pipermail/openstack-sigs/2017-July/000013.html)
-'''Description''': OpenStack's Ansible SIG is a community of practice and collaboration for developers, operators, and end users of OpenStack with Ansible. Its purpose is to facilitate cross-project collaboration amongst Ansible-related OpenStack projects and efforts, and to provide a broader feedback loop between operators and users of Ansible in OpenStack clouds and developers of Ansible-related tools for deploying, operating, and managing services in OpenStack Clouds. The Ansible SIG also facilitates awareness of improvements, project timelines, or issues relating to OpenStack in the [https://github.com/ansible/ansible Ansible] project community, and aspires to grow the collective pool of contributors across both open source projects.
+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
-==== Potential Goals====
+=== Mailing List ===
-* Provide a unified source of Ansible + OpenStack related information for developers, operators, and consumers of OpenStack cloud infrastructure
+Currently we have the OpenStack-Discuss mailing list which you can sign up for here: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
-* Build / consolidate knowledge around best practices and existing roles or playbooks for operators and users
+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
-* Grow the pool of maintainers and knowledge around development for [https://docs.ansible.com/ansible/latest/list_of_cloud_modules.html#openstack Ansible's OpenStack modules] (and the [https://docs.openstack.org/shade/latest/ Shade library]) and better understand how they are used by operators / end users
+( the [Openstack-sigs] tag in the example is added by the Mailman software that drives OpenStack mailing lists )
-* Others: TBD!
-==== Audience====
-* Users of Ansible to deploy, manage, and/or consume OpenStack and OpenStack services
-* Contributors and/or users of various Ansible-related OpenStack projects, OpenStack modules in Ansible, and/or Ansible roles for use in or with OpenStack
-* Anyone curious about using Ansible and OpenStack together
-====SIG Leads====
-* Robyn Bergeron (rbergeron)
-* Another Ansible+OpenStack Enthusiast, TBD
-====Community Infrastructure====
-* Wiki: TBD, likely https://wiki.openstack.org/wiki/Ansible_SIG
-* Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs; [ansible] for the tag
-* IRC: TBD, likely #ansible-openstack
-* Meetings: TBD, #openstack-meeting-$somenumber; Agenda / details to be linked on SIG page + meetings list
-====Other notes====
-This SIG will essentially be the same group as the OpenStack Working Group in the [https://github.com/ansible/community#groups-we-help Ansible community] (OpenStack WG request in Ansible can be found [https://github.com/ansible/community/issues/219 here.]). Most of the community-facilitating infrastructure / information will likely live in OpenStack's community space; however, pointers from one group to the other will be made as needed for clarity / necessity.

Difference between revisions of "OpenStack SIGs"