OpenStack IRC meetings schedule
Go to file
Lance Bragstad 2cc9c12d28 Remove the policy meeting
This meeting was put in place about 18 months ago for the purpose of
getting a handle on the direction of RBAC and policy enforcement
across OpenStack. Since then we've put together community goals [0][1]
as part of a roadmap for improving policy across the platform.

Meetings on this topic have become redundant and rarely include new
topics since most involved parties understand the basic approach
behind what we're trying to accomplish. It's also apparent that we
feel pretty comfortable approaching (and being approached by) teams in
order to answer questions about policy and RBAC.

[0] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
[1] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html

Change-Id: Iebc2de0b630483709ec499b39e9418d17a2014e5
2018-07-11 16:45:10 +00:00
meetings Remove the policy meeting 2018-07-11 16:45:10 +00:00
test_tools Setup a tox pep8 check and update test-requirements.txt 2016-05-20 11:04:59 -07:00
tools Replaces yaml.load() with yaml.safe_load() 2018-03-08 14:03:36 +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
.zuul.yaml Zuul: Remove project name 2018-01-31 15:30:56 -08:00
README.rst Revert "No-op Change to force a re-publish" 2016-06-17 10:21:14 +00:00
bindep.txt bindep: Supply a bindep.txt file to avoid the 'global' set 2017-10-12 12:25:10 +11:00
meetingindex.jinja Add anchors to link to specific parts of index 2018-06-14 16:24:10 +02:00
sample.yaml Update sample.yaml 2016-07-20 16:19:47 +00:00
test-requirements.txt Update Puppet OpenStack meeting information 2017-08-03 10:07:32 -06:00
tox.ini Move irc meetings tox job in-tree 2017-12-19 07:23:32 +01: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.