On 1/31/19 8:26 AM, Colleen Murphy wrote:
I like the idea. One question is, how would these groups be bootstrapped? At the moment, SIGs are formed by 1) people express an interest in a common idea 2) the SIG is proposed and approved by the TC and UC chairs 3) profit. With a more cross-project, deliverable-focused type of group, you would need to have buy-in from all project teams involved before bringing it up for approval by the TC - but getting that buy-in from many different groups can be difficult if you aren't already a blessed group. And if you didn't get buy-in first and the group became approved anyway, project teams may be resentful of having new objectives imposed on them when they may not even agree it's the right direction.
As a concrete example of this, the image encryption feature[1] had multiple TC members pushing it along in Berlin, but then got some pushback from the project side[2] on the basis that they didn't prioritize it as highly as the group did.
Matt suggested that the priority could be raised if a SIG essentially sponsored it as a top priority for them. Maybe SIG support would be an aspect of creating one of these teams? I don't know what you would do with something that doesn't fall under a SIG though.
1: https://review.openstack.org/#/c/618754/ 2: http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000815....