Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
On Wed, Dec 23, 2015 at 2:26 PM, Doug Hellmann wrote: > 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 Hi Doug, thanks for the feedback! I'll import this into gerrit and have a look at working on your suggestions. Cheers, Louis __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
Excerpts from Louis Taylor's message of 2015-12-13 08:09:24 +: > On Thu, Dec 10, 2015 at 06:20:44PM +, 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 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
Sean McGinnis wrote: > On Thu, Dec 10, 2015 at 06:20:44PM +, Flavio Percoco wrote: >> >> 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 really like this idea. If we get something in place, I'll definitely > add any Cinder related dates the the schedule. NB: you already can and should ! Please propose changes to: http://git.openstack.org/cgit/openstack/releases/tree/doc/source/schedules/mitaka.rst -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
On Thu, Dec 10, 2015 at 06:20:44PM +, 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 signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
On Thu, Dec 10, 2015 at 06:20:44PM +, Flavio Percoco wrote: > > 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 really like this idea. If we get something in place, I'll definitely add any Cinder related dates the the schedule. Good idea! Sean (smcginnis) > > -- > @flaper87 > Flavio Percoco > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
Jeremy Stanley wrote: > On 2015-12-10 18:20:44 + (+), 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) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
On 2015-12-10 18:20:44 + (+), Flavio Percoco wrote: > 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. Sounds great to me! > 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. Yep, shouldn't be too hard to add, I expect. > 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. -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines
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? Cheers, Flavio -- @flaper87 Flavio Percoco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
