This project aims to provide an easier way to track CentOS related meetings. Every project meeting is defined by a YAML files. These are combined using yaml2ical into a web page listing all meetings and an .ical file that can be read by your calendaring application of choice.

For the actual calendar, please see:

• CentOS IRC meetings schedule
• iCalendar meeting schedule (.ics)

Instructions for adding or changing a meeting are also there.

This system is based on the fantastic work done by the OpenStack Project as documented at https://opendev.org/opendev/irc-meetings for managing their internal meetings.

Each meeting consists of:

• project: the name of the project

• project_url the URL to the page 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, Atomic SIG Team Meeting should be saved under atomic-sig-team-meeting.yaml.

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

• The project name is shown below.

    project:  Software Collections SIG Sync-up
  

• 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 documented in the yaml2ical docs (https://opendev.org/opendev/yaml2ical)

    schedule:
        - time:       '1600'
          day:        Wednesday
          irc:        centos-meeting
          frequency:  weekly
  

• The chair is just a one liner. The might be left empty if there is not a chair.

    chair:  Honza Horak
  

• The project description is as follows. Use > for paragraphs where new lines are folded, or | for paragraphs where new lines are preserved.

    description:  >
        Discussions related to the Software Collections SIG.  The SIG will provide an upstream development area for various software collections and related tools. Developers can build on and extend existing SCLs, so they don't need to re-invent the wheel or take responsibility for packaging unnecessary dependencies. 
  

The correct command line arguments are provided in the script doit.sh, but you will likely have to modify the specific paths in that script for your particular setup.

yaml2ical can be installed via dnf install yaml2ical, but this might not be the version you need, depending on when you're reading this.

Commit the generated files to the /content/community directory in https://git.centos.org/centos/centos.org

Note that doit.sh copies the files into the correct directory if your directory structure matches (ie, the centos website is in ../centos.org in your directory layout) so you'll just have to go commit that change and create a PR at git.centos.org