OpenStack IRC meetings schedule
Go to file
Thierry Carrez 90d0c47dd3 Consolidate openstack-meeting channels
With some IRC meetings having moved to team channels, we have
a lot more room in the "common" meeting rooms. To the point
where #openstack-meeting-cp and #openstack-meeting-5 are taking
up valuable bot space (bots can only join so many channels) for
very little usage.

Furthermore, the benefit of using common channels is that the
team activity is publicized to meeting channel lurkers, and
neither #openstack-meeting-cp not #openstack-meeting-5 gathered
a faithful attendance.

This propose to consolidate meetings to the other meeting channels
(#openstack-meeting{,-alt,3,4}) by moving the only two meetings
that actually took advantage of those two meeting rooms.

Once this merges, we can start the work of removing those from the
meeting bot watch.

Change-Id: Iafcba92f908f4305492737ffea2771acf85a7fbc
2019-01-03 13:58:38 +01:00
meetings Consolidate openstack-meeting channels 2019-01-03 13:58:38 +01:00
test_tools Setup a tox pep8 check and update test-requirements.txt 2016-05-20 11:04:59 -07:00
tools Consolidate openstack-meeting channels 2019-01-03 13:58:38 +01: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 day_specifier from recurrence 2018-11-07 18:00:34 +00:00
sample.yaml Update sample.yaml 2016-07-20 16:19:47 +00:00
test-requirements.txt add day_specifier from recurrence 2018-11-07 18:00:34 +00:00
tox.ini Use python3 to run pep8 job 2018-11-07 18:23:09 +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.