OpenStack IRC meetings schedule
Go to file
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
meetings Add explict start dates to meeting yaml 2016-01-08 12:36:34 +11:00
tools Add check_channels.py and testenv to run it 2015-11-25 17:28:39 +11:00
.gitignore In tox, write output to subdir 2015-05-26 10:28:01 -07:00
.gitreview Add .gitreview to the repo 2014-11-19 12:50:02 -05:00
meetingindex.jinja Replace hyphens with underscores for meeting_id 2015-11-04 10:33:23 -08:00
README.rst Noop whitespace change to resync calendars 2016-01-04 09:12:30 +01:00
sample.yaml Add sample.yaml and update README.rst 2015-06-16 20:27:43 +10:00
test-requirements.txt Set Calendar Name and Description on ical 2015-06-13 17:23:13 +00:00
tox.ini Add check_channels.py and testenv to run it 2015-11-25 17:28:39 +11:00

OpenStack Meetings

This project aims to provide an easier way to manage OpenStack team meetings. Currently, each team's meeting time and agenda are listed at:

https://wiki.openstack.org/wiki/Meetings

This project replaces each meeting with well-defined YAML files.

YAML Meeting File Format

Each meeting consists of:

  • project: the name of the project
  • meeting_id: the name given to the #startmeeting meetbot command
  • agenda_url the URL to the page with the agenda for the meeting, usually in the wiki
  • schedule: a list of schedule each consisting of
    • time: time string in UTC
    • day: the day of week the meeting takes place
    • irc: the irc room in which the meeting is held
    • frequency: frequent occurrence of the meeting
  • chair: name of the meeting's chair
  • description: a paragraph description about the meeting

The file name should be a lower-cased, hyphenated version of the meeting name, ending with .yaml . For example, Keystone team meeting should be saved under keystone-team-meeting.yaml.

Example

This is an example for the yaml meeting for Nova team meeting. The whole file will be import into Python as a dictionary.

  • The project name is shown below.

    project:  Nova Team Meeting
  • The schedule is a list of dictionaries each consisting of time in UTC, day of the week, the irc meeting room, and the frequency of the meeting. Options for the frequency are weekly, biweekly-even, and biweekly-odd at the moment.

    schedule:
        - time:       '1400'
          day:        Thursday
          irc:        openstack-meeting-alt
          frequency:  biweekly-even
    
        - time:       '2100'
          day:        Thursday
          irc:        openstack-meeting
          frequency:  biweekly-odd
  • The chair is just a one liner. The might be left empty if there is not a chair. It's recommended to mention his/her IRC nick.

    chair:  Russell Bryant (russellb)
  • The project description is as follows. Use > for paragraphs where new lines are folded, or | for paragraphs where new lines are preserved.

    description:  >
        This meeting is a weekly gathering of developers working on OpenStack.
        Compute (Nova). We cover topics such as release planning and status,
        bugs, reviews, and other current topics worthy of real-time discussion.

sample.yaml

If creating a new yaml meeting file please consider using sample.yaml and editing as appropriate.