[openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines

Thierry Carrez thierry at openstack.org
Fri Dec 11 09:47:23 UTC 2015

Jeremy Stanley wrote:
> On 2015-12-10 18:20:44 +0000 (+0000), Flavio Percoco wrote:
>> Has this been attempted? Any objections? Is there something I'm not
>> considering?
> I'm not aware of any work so far to that end, but have a feeling you
> could reuse http://git.openstack.org/cgit/openstack-infra/yaml2ical
> and make sure the schedule is maintained in a compatible YAML
> layout. You might need to write/tweak a Sphinx extension to
> transform it into RST so it can be embedded into the rendered
> version of the schedule, but if so you can get inspiration from
> https://git.openstack.org/cgit/openstack/ossa/tree/doc/source/_exts/vmt.py
> which does very similar things.

yaml2ical is very much about recurring events, and a release schedule is
a set of non-recurring dates, so I'm not sure there is that much you can
reuse there (apart from using it as an example to generate an iCal file
from yaml).

Rather than shoehorning the release schedule in the meetings yaml
format, I would come up a specific yaml format to describe the release
schedule. From that YAML you would generate a RST page very much like
the RST we now have. From all such YAML files you would generate a
global .ics calendar (containing all cycles, to avoid forcing people to
resubscribe every cycle).

The current RST is not that great to edit anyway (you have to get the
table layout right), so having all the deadlines in a YAML file would
actually also simplify maintenance.

Thierry Carrez (ttx)

More information about the OpenStack-dev mailing list