On Tue, Nov 24, 2015 at 11:35:34AM +0100, Thierry Carrez wrote:
> Tony Breeds wrote:
> > [...]
> > I understand that we want to keep the number of parallel meetings to a 
> > minimum,
> > but is it time to add #openstack-meeting-5?
> 
> Some slots are taken by groups that have not been holding meetings for
> quite a long time. For good hygiene, I'd like us to clean those up
> /before/ we consider adding a new meeting channel. It might well still
> be necessary to create a new channel after the cleanup, but we need to
> do that first.

There is lots of hygiene stuff to do in the repo :)  I'll see what I can come up
with but at the very least it's going to require a bunch of people to +1 a
review to drop their meeting ;P

So there are 17 slots that are full so I'll look at them.  If a slot hasn't
been used this month I'll open a review to drop them (with appropriate CC's)

I'll go through the other slots later as they're not blocking anything right
now.
 
> It's a bit of a painful work (especially for teams without a clear
> meeting_id) so it's been safely staying at the bottom of my TODO list
> for a while...

Yeah and mine ;P
 
> > [...]
> > Confusion
> > =========
> >     So this is really quite trivial.  As you can see above we don't have an
> > #openstack-meeting-2 channel the ...-alt is clearly that, but still people 
> > are
> > confused.  How would people feel about creating #openstack-meeting-2 and 
> > making
> > it redirect to #openstack-meeting-alt?
> 
> I'd rather standardize and rename -alt to -2 (i.e. redirect -alt to -2
> on IRC, and bulk-change all meetings YAML from -alt to -2).

I wanted to go the other way as it's slightly less impactful. Most people grok
that '-alt' == '-2'.  if we redirect from 2 -> alt it's only a few people
that transparently get redirected.

If we do it the other way around everyone already in -alt needs to move.

That's arguing implementation, rather than objecting so I'll start the process
of registering #openstack-meeting-2 which requires people to:
  a) not use it ; and
  b) everyone in there to leave.

Registering only takes 30seconds, once people leave (and I'm awake).

In order to be pro-active I'll register #openstack-meeting-5 so when we *do*
need it the startup costs are smaller.

The first thing I'll do after registering the channels is give @infra access.

Yours Tony.

Attachment: pgp8wZyQ3Mswy.pgp
Description: PGP signature

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to