Go to file

Tony Breeds acc70666a1 Add start_dates to freezer and doc-ha

Both these meetings had inflight reviews at the begining of the year when we
added explict start_dates to all the yaml files.  This meant that they were
missed :(

It's a little hard to verify that these start dates are correct but looking at the irc-meetings.ics file the start date is set for:

Documentation HA Guide update Meeting: 2016-11-16
Freezer Meeting                      : 2016-11-10

So seomthing like:
---
 import datetime

 doc = (datetime.date(2016, 1, 27), datetime.date(2016, 11, 16))
 freezer  = (datetime.date(2016, 2, 11), datetime.date(2016, 11, 10))

 for start, end in [doc, freezer ]:
     print start
     for _ in range(52):
         d = start + datetime.timedelta(days=7*_)
         if d == end:
             print 'OK'
             break
     else:
             print 'Meeting doesn\'t match'
---

Shows that they seem to match.  The start dates were selected as the next
occurence after the merge of the approriate change
(I4f577786c473445d3e009b1979a236d78db15c39 and
I4287eca818a281a8eca78f8da7a07460f080cad7)

Change-Id: I3394c08a30de799989dae07a002226d60676ac3c

2016-11-10 20:41:21 +11:00

meetings

Add start_dates to freezer and doc-ha

2016-11-10 20:41:21 +11:00

test_tools

Setup a tox pep8 check and update test-requirements.txt

2016-05-20 11:04:59 -07:00

tools

check_chair: Actually fail if there is a problem.

2016-10-05 00:59:56 +00: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

Add a UTC clock and integrate local meeting time

2016-08-28 16:32:21 +00:00

README.rst

Revert "No-op Change to force a re-publish"

2016-06-17 10:21:14 +00:00

sample.yaml

Update sample.yaml

2016-07-20 16:19:47 +00:00

test-requirements.txt

Add helper to find full slots

2016-05-23 17:28:41 -07:00

tox.ini

Remove the check target

2016-07-27 22:32:29 +00:00

README.rst

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 of the YAML for the Nova team meeting. The whole file will be imported 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.