irc-meetings/meetings/monasca-team-meeting.yaml
Tony Breeds bad8c72421 Add explict start dates to meeting yaml
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
2016-01-08 12:36:34 +11:00

18 lines
755 B
YAML

project: Monasca Team Meeting
meeting_id: monasca
agenda_url: https://etherpad.openstack.org/p/monasca-team-meeting-agenda
schedule:
- time: '1500'
day: Wednesday
irc: openstack-meeting-3
frequency: weekly
start_date: 20160106
chair: Roland Hochmuth (rhochmuth)
description: >
To provide a multi-tenant, highly scalable, performant, fault-tolerant
monitoring-as-a-service solution for metrics, complex event processing
and logging. To build an extensible platform for advanced monitoring
services that can be used by both operators and tenants to gain
operational insight and visibilty, ensuring availabilty and stability.
Everyone is welcome to attend our meetings and add agenda items.