Due to lack of interest, the neutron_upgrades meeting is being
cancelled. The business previously handled there will be handled in the
neutron team meeting on an ad hoc basis.
Change-Id: I9c8d3978426c89d1623d1023062290310153f6c9
With some IRC meetings having moved to team channels, we have
a lot more room in the "common" meeting rooms. To the point
where #openstack-meeting-cp and #openstack-meeting-5 are taking
up valuable bot space (bots can only join so many channels) for
very little usage.
Furthermore, the benefit of using common channels is that the
team activity is publicized to meeting channel lurkers, and
neither #openstack-meeting-cp not #openstack-meeting-5 gathered
a faithful attendance.
This propose to consolidate meetings to the other meeting channels
(#openstack-meeting{,-alt,3,4}) by moving the only two meetings
that actually took advantage of those two meeting rooms.
Once this merges, we can start the work of removing those from the
meeting bot watch.
Change-Id: Iafcba92f908f4305492737ffea2771acf85a7fbc
This is an intermediate step, but valuable, step in stabilising the IRC
meeting iCal. There are a couple of issues.
1. Every time we regenerate the iCal we set a new start point.
2. The odd/even decision is based on the start date (which defaults to
the time the ics file is generated)
By adding explicit start dates to all out meetings (which have been
reset this week) we mitigate both of these issues.
There are other aspects that require updates to yaml2ical, but this
relatively simple step while we get those items in place.
Note: this week you can verify that these start_dates are correct by
1. running tox on master
2. save output/irc-meetings.ical to output/master.ical
3. apply this patch and re-run tox
4. diff output/master.ical output/irc-meetings.ical
Change-Id: I7ae70c684884c0c708738392a0b43bbb3c1c878e
The Neutron Upgrades meeting was originally weekly but switched to
bi-weekly to accommodate yaml2ical.
With the Satori meeting gone, move to that channel and reset back to
weekly.
Change-Id: I93089372bcad0897dcb46c4262d9da36d9792123
Also switched the channel to -3 since -2 is not an official channel with
logging. Note that to pass overlapping validations, the frequency is set
to bi-weekly since the channel is used by another project meeting
(zaqar) on even weeks. We'll need to follow up on the permanent solution
for the team (ideally, we would add another supported channel to reflect
huge expansion in the number of OpenStack projects due to the big tent).
Change-Id: Icb13409510212ec3353245c340f43e14fb87873a
Nate Johnston