The openstacksdks team meets on the
third thursday of each month. We could
use a a monthly third-week option.
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Change-Id: I9eee4582506274a18e7146f6c241cf56fb585075
Add a recurrence option for meetings that repeat monthly. Instantiate
the ones for the first weekdays of the month for now.
Change-Id: I0fa95653594dc5a28008630f57bee67b92537d29
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
While doing so move the frequency description out of line into it's own
section.
Change-Id: If757d7192e41d29c0013c46fcda16e44e2f58aa1
Co-Authored-By: Graham Hayes <gr@ham.ie>
Rather than silently removing the skipped meeting from the calendar as
is the default behavious of exdate add a one off calendar entry for
each skipped meeting.
The aim is to show that the slot is generally consumed just that the
meeting has been explictly cancelled/skipped.
Change-Id: Idd9eb1a04fe9c9661e87978c0128a292bb8e89a4
In the OpenStack community it's common to cancel meetings while the
summit happens.
Add the ability to add a list of dates to skip. These will then be
included in the iCal
Change-Id: I1dd5ca6f3e5d6d257489fdc14bbe108abc7436e6
start_date defines when a meeting series begins. start_date
is used in lieu of the current date when rebuilding the calendar.
This will ultimately let us move away from needing to have
biweekly-odd and biweekly-even.
I also added an example.yaml with a start_date
Change-Id: I0c5f6e5951b6c15b949f599182f48aa132b76abb
While yaml2ical is clearly driven by the needs of the OpenStack
community, there is nothing inherently "OpenStack" about the job it
does.
Also, the README doesn't need to describe what the tool wants to do,
since it has, in fact, accomplished its goal.
Change-Id: I7cf026858bc52eacd7650d9eb9d4b357deb5624f
Update the documentation to note which elements of the yaml
are required. Also added the agenda_url and project_url keys
to the main doc list.
Lastly, updated the meeting/example.yaml to show usage of the new
duration, agenda_url, and project_url keys
Change-Id: Ifaa9f029ae920b22aa60ab3d47d14982707285d9
We currently hardcode the meeting duration to be one hour. This change
allows the user to specify an optional meeting duration (in minutes)
for shorter or longer meetings.
Change-Id: Ib41d56abc0e866ca50e45469e7cd57d726b053df
agenda_url is already used in the meeting file template, now it will
be attached to every calendar event.
The new key project_url is for the page describing the overall
project and it too, if present will be in the calendar event.
Closes: https://storyboard.openstack.org/#!/story/2000288
Change-Id: Ic9f823bf744b27f42359858e55557b36fcab8f0a
Signed-off-by: Brian (bex) Exelbierd <bex@pobox.com>
The README had fallen out of date with the latest code additions.
Change-Id: Ifd90703bf2853d69aeaace8160b338fc1c79086a
Signed-off-by: Brian (bex) Exelbierd <bex@pobox.com>
Besides looking for the required values, allow any extra values to be
saved and referenced from templates.
Change-Id: I7395a92f447aee943da54aa0439dd0c683da176a
Handle undefined values gracefully in the Meeting and
Scheduler definitions. Refactor the Meeting class with improved
initialization and clean up the creation of the meetings
list.
Change-Id: Iad6a712c4b05c8af440c1f89966ae81102bb3e4e
Declare a yaml2ical entry point to replace convert.py.
Clean up the useless const.py and move the only remaining constant to
meeting.py.
Change-Id: I6204aa2c9d96640e50167a9df78686a1cd25e9ec
We'll need to upload this module to PyPI in order to properly integrate
with the OpenStack Infrastructure. Unfortunately, there is already a
module there going by the 'arbiter' name. This switches the module name
to 'yaml2ical', which is not sounding nice, but at least is functionally
correct.
The git repository itself shall be renamed once this is merged.
Change-Id: I896bcbe7be8c6a017015b428c6ff0d39a4974a04
As part of the repository split between code and OpenStack-specific
meetings descriptions, this removes the OpenStack meetings YAML files.
Change-Id: Ibb2520220c0c462d50c1bc393001ea03ae051fb5
Removes support for meeting agenda in the YAML format. Meeting agendas
change every week and would trigger a lot of unnecessary reviews. Better
support them using plain wiki pages like we do today.
Change-Id: I3331f528855bfc38f88c3fe63866f0af4338d1ff
This patch added all the remaining YAML files. Please note that the
meeting information on the OpenStack wiki Meetings page will like have
been updated while this patch is going through review. So meeting
information such as agenda might not be up-to-date by the time this
patch gets merged.
The python scripts also have their copyright informations updated.
Also changed from logging.info to logging.error when conflicts are
detected.
Change-Id: I8ecf94d32f2064eac0d30fc12cfdd999b54e6497
Added explanations and example scenarios about the command line usage for
jobs.py to the README.rst file. A few syntax errors found in the
README.rst was fixed as well. Visit the following link for a preview of
the README.rst:
http://rst.ninjs.org/?n=de7d3bc022f4ba2417bd3de97e33c91c&theme=nature
Additionally, the YAML file extention has been changed to '.yaml.' The
name of the meetings have also been capitalized. Spaces were added
in front of agenda list items.
Lastly, a minor issue was fixed where the iCals files was missing the .
in the file extension. It now can handle both '.yaml' and '.yml'
extentions when writting '.ical' files.
Change-Id: Iff6805a690339303ec58bf19883dcfbbf3d37d72
Added README for the `meetings` directory where the yaml files for each
meeting is located. The README includes a link to the OpenStack Meeting
page on the wiki, a link to the meeting yaml files on OpenStack git
site, as well as brief explanation on the content inside a yaml file.
The description of the yaml content now uses | to perserve the "list"
structure. This section is further edited so that `*` are used to
format these bulleted list of agenda items instead of `-`.
Change-Id: Iab1af314dc979394bd4a61caccf902cc92bf3735
In order to run PEP8-compliance tests using PBR, the setup.py, setup.cfg,
requirements.txt, and tox.ini files must exist in the base directory of
this project. These files have been created and specified accordingly.
The specific environments to be tested using tox are specified in
requirements.txt and include the py33 and pep8 environments. Package
requirements are specified in requirements.txt and include pyyaml and
icalendar. Additional package requirements for testing are specified in
test-requirements.txt and include pbr and hacking.
Existing Python source code has been modified to pass PEP8-compliance
checks. This included adding docstrings and limiting line length.
Lastly, the README file has been renamed and files have been added
for the project license and manifest.
Change-Id: I51a50d64c579212c5c7fa756bb1d34e774666be9
rbowen