Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 27 June 2017 at 23:47, Sean Dague wrote: > I still think I've missed, or not grasped, during this thread how a SIG > functions differently than a WG, besides name. Both in theory and practice. I think for the most part SIG is just a more fitting moniker for some of these

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On Wed, Jun 21, 2017 at 8:59 AM, Thierry Carrez wrote: > Hi everyone, > > One of the areas identified as a priority by the Board + TC + UC > workshop in March was the need to better close the feedback loop and > make unanswered requirements emerge. Part of the solution is

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 2017-06-27 15:42:05 +0200 (+0200), Thierry Carrez wrote: > Sean Dague wrote: [...] > > I wonder if we're going down this path, if some kind of tooling like > > standard tags for issues/patches should be added to the mix to help gain > > the effectiveness that the k8s team seems to have here. >

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 06/27/2017 09:42 AM, Thierry Carrez wrote: > Sean Dague wrote: >> I also think it's fine to rebrand WG to SIG, but we should also be >> honest that it's mostly a rebrand to consolidate on terminology that k8s >> and cncf have used that people find easier to understand so it's a way >> in which

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Sean Dague wrote: > On 06/21/2017 01:10 PM, Michał Jastrzębski wrote: >> One of key components which, imho, made SIGs successful in k8s is >> infrastructure behind it. >> >> When someone proposes an issue, they can tag SIG to it. Everyone in >> this SIG will be notified that there is an issue they

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 06/21/2017 01:10 PM, Michał Jastrzębski wrote: > One of key components which, imho, made SIGs successful in k8s is > infrastructure behind it. > > When someone proposes an issue, they can tag SIG to it. Everyone in > this SIG will be notified that there is an issue they might be > interested

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On Wed, Jun 21, 2017 at 11:55 AM, Matt Riedemann wrote: > On 6/21/2017 11:17 AM, Shamail Tahir wrote: > >> >> >> On Wed, Jun 21, 2017 at 12:02 PM, Thierry Carrez > > wrote: >> >> Shamail Tahir wrote: >> > In the

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 21/06/17 08:41 PM, Zhipeng Huang wrote: > 2. Enhance dev/non-dev comms. I doubt more meetings will be the solution. > > a. I would suggest projects when doing their planning at Forum or > PTG, always leave a spot for requirement from WGs. And WG chairs > should participate this

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

to put my public cloud wg hat on, I think the lack of coordination is a common problems among OpenStack WGs but I think transitioning WGs to SIGs will help solving the issue alone. I think from my observations from existing WGs, the mechanism that are now in place works great, we have many

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 06/21/2017 11:55 AM, Matt Riedemann wrote: > On 6/21/2017 11:17 AM, Shamail Tahir wrote: >> >> >> On Wed, Jun 21, 2017 at 12:02 PM, Thierry Carrez >> > wrote: >> >> Shamail Tahir wrote: >> > In the past, governance has helped (on

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

One of key components which, imho, made SIGs successful in k8s is infrastructure behind it. When someone proposes an issue, they can tag SIG to it. Everyone in this SIG will be notified that there is an issue they might be interested it, they check it out and provide feedback. That also creates

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 6/21/2017 11:17 AM, Shamail Tahir wrote: On Wed, Jun 21, 2017 at 12:02 PM, Thierry Carrez > wrote: Shamail Tahir wrote: > In the past, governance has helped (on the UC WG side) to reduce > overlaps/duplication in WGs

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On Wed, Jun 21, 2017 at 12:02 PM, Thierry Carrez wrote: > Shamail Tahir wrote: > > In the past, governance has helped (on the UC WG side) to reduce > > overlaps/duplication in WGs chartered for similar objectives. I would > > like to understand how we will handle this (if

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Shamail Tahir wrote: > In the past, governance has helped (on the UC WG side) to reduce > overlaps/duplication in WGs chartered for similar objectives. I would > like to understand how we will handle this (if at all) with the new SIG > proposa? I tend to think that any overlap/duplication would

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Hi, In the past, governance has helped (on the UC WG side) to reduce overlaps/duplication in WGs chartered for similar objectives. I would like to understand how we will handle this (if at all) with the new SIG proposa? Also, do we have to replace WGs as a concept or could SIG augment them? One

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Matt Riedemann wrote: > How does the re-branding or re-categorization of these groups solve the > actual feedback problem? If the problem is getting different people from > different groups together, how does this solve that? For example, how do > we get upstream developers aware of operator

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 6/21/2017 9:59 AM, Thierry Carrez wrote: Hi everyone, One of the areas identified as a priority by the Board + TC + UC workshop in March was the need to better close the feedback loop and make unanswered requirements emerge. Part of the solution is to ensure that groups that look at specific