Go to file

Tony Breeds ecf5f08660 Remove the check target

Move checking channels from the check target into pep8.  The general
idea is that pep8 will be for style and linting type checks and ical
will be for generating iCal files and HTML.

Change-Id: I14648e39132369d4d4c865ca835a020f62a5c978
Depends-On: I7ddfa03606aa750308e2e8c6b9c77e9f226bead1

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

meetings

Merge "Proposing OpenStack SWG Meeting"

2016-07-21 18:03:26 +00:00

test_tools

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

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

tools

Check chairs are in the 'correct' format as part of pep8

2016-07-26 13:16:39 -05: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

Merge "Give example #startmeeting command"

2016-05-23 09:19:00 +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.