On 2014-01-16 14:20:15 +0100 (+0100), Thierry Carrez wrote:
> #openstack-meeting-3 proposed at: https://review.openstack.org/67152
> Will let you know if/when accepted and merged.
Accepted and merged... The bot has joined (and so have I).
--
Jeremy Stanley
___
Thierry Carrez wrote:
> There are already conflicts as people pick times that appear to be free
> but are actually used every other week... so a third room is definitely
> wanted. We can go and create #openstack-meeting3 (other suggestions
> welcome) and then discuss a consistent naming scheme and/
On Wed, Jan 15 2014, Joe Gordon wrote:
> * Python3 - 16-May-2013
>Bi-Weekly (every other week) meetings on Thursdays at 1600 UTC
Yep, I confirm this one's dead for now. I've edited the details on the
wiki.
Thanks Joe.
--
Julien Danjou
-- Free Software hacker - independent consultant
-- htt
On Wed, Jan 15, 2014 at 8:49 AM, Sergey Lukjanov wrote:
> Looks like lbaas meeting is still alive:
>
> from eavesdrop:
>
> neutron_lbaas - 09-Jan-2014 14:01
> neutron_lbaas_subteam_meeting - 05-Dec-2013 14:00
> nuetron_lbaas - 28-Nov-2013 14:02
>
Thanks for the correction, that leaves 3 possibly
Looks like lbaas meeting is still alive:
from eavesdrop:
neutron_lbaas - 09-Jan-2014 14:01
neutron_lbaas_subteam_meeting - 05-Dec-2013 14:00
nuetron_lbaas - 28-Nov-2013 14:02
On Wed, Jan 15, 2014 at 8:24 PM, Joe Gordon wrote:
>
>
> On Wed, Jan 15, 2014 at 6:02 AM, Thierry Carrez wrote:
>
>> J
On Wed, Jan 15, 2014 at 6:02 AM, Thierry Carrez wrote:
> Joe Gordon wrote:
> >> [1]
> >
> https://www.google.com/calendar/ical/bj05mroquq28jhud58esggq...@group.calendar.google.com/public/basic.ics
> >
> > Is this calendar periodically pruned of dead meetings (for some
> > definition of dead)? If n
Joe Gordon wrote:
>> [1]
> https://www.google.com/calendar/ical/bj05mroquq28jhud58esggq...@group.calendar.google.com/public/basic.ics
>
> Is this calendar periodically pruned of dead meetings (for some
> definition of dead)? If not doing so may free up a few slots.
It's kept in sync with the Meet
On Jan 13, 2014 3:42 PM, "Lyle, David" wrote:
>
> With all the warranted meeting time shuffling that has been happening
recently, and the addition of so many projects and sub-teams, the meeting
calendar for #openstack-meeting and #openstack-meeting-alt [1] is
relatively full. So recently, when tr
Agreed that -meeting3 is ok.
BTW my main concern is a process of managing overlaps between projects
meetings time, that'll harder and harder with increasing number of meeting
rooms.
On Wed, Jan 15, 2014 at 3:32 PM, Flavio Percoco wrote:
> On 15/01/14 11:28 +0100, Thierry Carrez wrote:
>
>> Ser
On 15/01/14 11:28 +0100, Thierry Carrez wrote:
Sergey Lukjanov wrote:
I think that in case of adding additional meeting rooms, we'll need to
avoid disparity between them in names. For example, currently we have a
lot of folks in #os-meeting and not so many in #os-meeting-alt, if we'll
have #os-m
Sergey Lukjanov wrote:
> I think that in case of adding additional meeting rooms, we'll need to
> avoid disparity between them in names. For example, currently we have a
> lot of folks in #os-meeting and not so many in #os-meeting-alt, if we'll
> have #os-meeting-alt-2 then we'll have even less fol
I think that in case of adding additional meeting rooms, we'll need to
avoid disparity between them in names. For example, currently we have a lot
of folks in #os-meeting and not so many in #os-meeting-alt, if we'll have
#os-meeting-alt-2 then we'll have even less folks there and it'll be the
same
Matthias Runge wrote:
> On 01/13/2014 09:33 PM, Lyle, David wrote:
>> With all the warranted meeting time shuffling that has been happening
>> recently, and the addition of so many projects and sub-teams, the
>> meeting calendar for #openstack-meeting and #openstack-meeting-alt
>> [1] is relatively
On 01/13/2014 09:33 PM, Lyle, David wrote:
> With all the warranted meeting time shuffling that has been happening
> recently, and the addition of so many projects and sub-teams, the
> meeting calendar for #openstack-meeting and #openstack-meeting-alt
> [1] is relatively full. So recently, when tr
With all the warranted meeting time shuffling that has been happening recently,
and the addition of so many projects and sub-teams, the meeting calendar for
#openstack-meeting and #openstack-meeting-alt [1] is relatively full. So
recently, when trying to move the Horizon meeting time, the poll
15 matches
Mail list logo
