Open Stack

> […]
> One idea I've been considering is eliminating the one and only sacred
> one-hour weekly TC meeting, and encouraging ad-hoc discussions (on
> #openstack-dev for example) between change proposers and smaller groups
> of TC members present in the same timezone. That would give us a good
> feel of what everyone thinks, reduce noise, and happen at various times
> during the day on a public forum, giving an opportunity for more people
> to jump in the discussion. The informal nature of those discussions
> would make the governance reviews the clear focal point for coordination
> and final decision.
> 
> It's clearly not the perfect silver bullet though, so I'd very much like
> to hear other ideas :)

Sold! As far as I’m concerned. :)

As a version of this idea, I was thinking of an #openstack-tc IRC channel, but wanted to give it another thought before bringing it up. :) While I don’t have the intention to necessarily increase the number of IRC channels we have, this would give us the ability to follow the TC related discussion better.

By being experienced with working remotely, I like channels with smaller well defined scope/purpose as I can prioritize which one to read first and I don’t need to filter that much of the different, sometimes parallel threads to catch up on what happened. Also when I see activity on these channels I get a better indicator whether I need to/want to look into the discussion immediately and be part of it or not. I don’t want to decrease the importance of #openstack-dev (or any other already existing channel), but rather noting that it has a broader scope that might be distracting.

My 2 cents.

Thanks,
Ildikó


> 
> -- 
> Thierry Carrez (ttx)
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev