On Wed, Nov 09, 2016 at 10:56:38AM +0100, Thierry Carrez wrote: > Our scheduling system currently only supports biweekly or weekly > meetings. We don't currently support monthly or triweekly meetings > (mostly to avoid having to detect complex conflicts with biweekly meetings). > > I guess we could evolve openstack-infra/yaml2ical to detect more complex > conflicts. We'd gain in scheduling flexibility, but lose in our ability > to pack the schedule tightly and make it pretty difficult to find empty > slots manually.
Yeah I think we should add monthly (which would more-or-less cover triweekly)
In that you could have a monthly-1st, monthly-3rd and monthly-4th events.
---
- time: '1400'
day: Monday
irc: openstack-meeting
frequency: monthly-1st # 1400 on the 1st Monday of the month
- time: '2100'
day: Thursday
irc: openstack-meeting-alt
frequency: monthly-3rd # 2100 on the 3rd Thursday of the month
- time: '0930'
day: Thursday
irc: openstack-meeting-alt
frequency: monthly-4th # 0930 on the 4th Thursday of the month
---
It isn't quite a tri-weekly rotation but may be close enough.
Of course adding this would mean adding tools to grok the data ad see if a
meeting slot is open
search-open --day Monday --time 1000 --freq weekly ?
Which could list the available irc channels or nothing. Later it could be
extended to list "nearby options"
Yours Tony.
signature.asc
Description: PGP signature
_______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
