Open Stack

Excerpts from Louis Taylor's message of 2015-12-13 08:09:24 +0000:
> On Thu, Dec 10, 2015 at 06:20:44PM +0000, Flavio Percoco wrote:
> > Greetings,
> > 
> > I'd like to explore the possibility of having .ics generated - pretty
> > much the same way we generate it for irc-meetings - for the OpenStack
> > release schedule and project's deadlines. I believe just 1 calendar
> > would be enough but I'd be ok w/  a per-project .ics too.
> > 
> > With the new home for the release schedule, and it being a good place
> > for projects to add their own deadlines as well, I believe it would be
> > good for people that use calendars to have these .ics being generated
> > and linked there as well.
> > 
> > Has this been attempted? Any objections? Is there something I'm not
> > considering?
> 
> I had a bit of time and started hacking up a simple version of this:
> 
>     https://github.com/kragniz/release-schedule-generator
> 
> The output of this may or may not be standards-compliant, but google calendar
> appears to accept it. You can see example output here:
> 
>     https://kragniz.eu/pub/schedule.ics
> 
> There's currently no support for project-specific events or RST output, but
> these can be added later if people think this current implementation isn't too
> bad.
> 
> Feel free to send feedback or (even better) pull requests in my direction if
> this seems okay.
> 
> Cheers,
> Louis

What you have is a really good start. Thanks for working on this!
How do you feel about importing the repository into gerrit?

A couple of things I'd like to see added:

1. Separate sections for cross-project and project-specific events.

   This would let us completely generate the RST content, as it
   appears on http://docs.openstack.org/releases/schedules/mitaka.html,
   as well as generate project-specific ICS files (some folks may want
   to only subscribe to cross-project events and their own project's
   schedule).

2. Durations for individual events.

   This would let us have single-day events, such as the final
   release date, as well as include things like mid-cycle meetings,
   sprints, etc. that may not all last 4 days.

3. The "generator" python package directory will probably need to
   be renamed to something more descriptive to let this be installed
   with other projects, which we'll need in order to integrate it with
   Sphinx.

4. That Sphinx integration will be easier if the function to construct
   the data structure representing the schedule data is separated from
   the function to format the data in different ways. That's just
   refactoring some of what's already there, so it's not a big deal.

Doug