-
Notifications
You must be signed in to change notification settings - Fork 144
Create OpenStack Working Group (note: not-quite-standard WG request) #219
Comments
Leaving as CWG until I wrap this up and turn it into owg. :) |
Does the OpenStack WG have IRC meetings, or should issues for discussion be raised at another meeting, such as core? |
There is no real OpenStack WG AFAIK. |
Alright, so most of the OpenStack issues and PRs were already labeled, I now finished it off. We may want to call out on a pinboard to the existing and past contributors to engage them in a discussion ? cc @gundalow |
What would be required to start the WG? I see that there is already team_openstack that ansibot knows about... |
This is what I usually do:
Then wait a few days to see the response, and update the $team in BOTMETA.yml. Sometimes we already can tell who is very active or an authority in Ansible, in other cases people step forward and take active roles. |
I am going to close this ticket. We now have an OpenStack Wiki space and an OpenStack pinboard for collaboration. Now we need members and actions! |
WORKING GROUP NAME: OpenStack
WORKING GROUP PURPOSE: Facilitate cross-community work with the OpenStack Community.
AT LEAST TWO INITIAL WORKING GROUP MEMBERS:
For context: Also starting an Ansible SIG in OpenStack; these two groups (this one, and the openstack one) will basically be the same group, pointing to one another as appropriate, reviewing items from both community's intended work queues. The Ansible SIG in openstack is actually the first SIG in that community, so ... working through a bit of being a guinea pig over there.
Right now: I just need wiki space, label, directory; want to hold off on irc channels, etc. until the likely members sort out where those things will likely live and how / who maintains them. Largely making this request in advance of having all the details for transparency. :)
For reference:
The text was updated successfully, but these errors were encountered: