As far as I can tell, the Puppet-OpenStack team meeting
has not been happening since August, 2017.
Let's clean up the meeting slot to let someone else take it.
Change-Id: Idb73a580b6cfbe9ee9a25237841f43316152f395
Recently it was decided[0] to drop the recurring meeting and switch to
a more adhoc basis. This change is to update the meeting information
and release the slot in #openstack-meeting-4
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120410.html
Change-Id: Icadb78dbf8cb242716c3d11f8ae236767192c220
We've asked for quite some time that meeting chairs be of the form
Full Name (IRC_Nick) with multiple chairs separated by a ','.
This patch reduces the debt here by filling in those details from:
www.openstack.org/community/members/
It doesn't complete the task as some meeting chairs do NOT have matching
entries in that database.
Also no effort has been made to verify that the listed meeting chair is
in fact the regular meeting chair.
Change-Id: If1abfb43c8ae6f1cd8d3f676c8e5131e3937e86a
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
Sync meeting times with current state on the wiki.
Removed meetings that were not in #openstack-meeting channels.
Temporarily mark ux-team-meeting and telco-wg-meeting in specific
IRC channels since yaml2ical reports them as conflicting otherwise
(due to a bug in biweekly conflict detection).
Change-Id: Ia418c18ae0149b8c22719330c2a8fb0f7e938630
Thierry Carrez