SIG description

gistfile1.txt

Why would I want to convert my work group to a SIG ?
 
SIGs are just about creating working groups that are not formally
attached to a specific governance body. Thierry and I observed that UC
working groups had a hard time attracting developers, creating a gap
when time came to implementing the work group priorities (and a lot of
frustration). We observed that TC working groups had a hard time
attracting users caring about a particular topic, creating a distance
resulting in misguided design and lost opportunities. And Board working
groups look like an even more impenetrable entity, probably limited to
elected Board members (hint: they are not).
 
The obvious solution is to enable work groups to be formed around
specific use cases and topics, rather than primarily define them as a
developer work group, or an operator work group, or a board work group.
To clearly mark the difference, we gave those new groups a name (out of
Kubernetes playbook): SIGs.
 
What would change in practice ?
 
Not much. Existing work groups can just continue to operate as they did.
The most visible change is the switch to the openstack-sig mailing-list
for the group discussion (instead of having the discussion exclusively
on -dev or -operators, or creating a cross-posting nightmare).
 
Otherwise in terms of processes, if anything SIGs have less constraints
than their TC/UC/Board-related parents. We only ask that the scope of
the group is clearly defined, and that it's clear how to proceed to join
the group.