The iCalendar spec expects a meeting vEvent to include a datetime stamp
and a unique ID for each instance. This adds these values to the
generated output.
Minor cleanup also included since I was touching code around them and
noticed little nits.
Change-Id: I4753571850665a2f28a6799b84ead4c31a275cc7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
We're running at least 3.5 in CI, so start there.
Update tox to set the environments from newest to oldest to avoid
issues with the dbm format selected for the .testrepository database
generated by the tests, to allow it to work for all tox environments
on a local system.
Change-Id: I7cde15039f782bba69ed9e0e44b08e289148019e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I87982923ab6ecda0673008070da6880536783b40
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
Add py34 as supported env. This simplifies testing on systems that are
no longer shipping python 3.3 (think: Ubuntu 14.04 LTS)
Change-Id: Iaac78ef4f40ee564496e731d616e261d2464d8b8
This commit allows for convert.py to generate .ics files on an
alternating schedule. This is denoted using alternating schedule
templates in the meeting yaml.
Added a meeting that has a biweekly schedule to test with.
Change-Id: I814eff00695a4925f9ebd6778392cfe78a0cf7b9
The jobs.py module didn't really make sense named the way it was since
the jobs are to be handled by Jenkins. This change renames files
accordingly.
Change-Id: Iaf54202dd0369e41686d134b4b723d4bccef8e54
Previously, there were two load_meetings() methods. One was in util.py
and one was a member of the Meeting object. This commit combines the two
and makes it general enough for both cases.
Update tox.ini as well as .testr.conf so that we can run some basic unit
tests. An initial test has been added so there is something to run.
Change-Id: I44fd693f1a4c0a0efcf99d935123108f22afea36
Generating the ical files from YAML requires
runtime dependencies to test, which we can easily get
with a tox environment. This makes it easier to test
the current state of the project with a single command.
Change-Id: I6583613aa89e766da5cd0d2824741c89e74c558c
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