opendev/yaml2ical
Code Issues Proposed changes

Add adhoc to the README

Browse Source 
This change documents the adhoc frequency for scheduling.

Change-Id: I9cd593c76fcecd8676c4993b7685fd313bbf0469
This commit is contained in:
Alex Schultz 2017-08-02 10:23:26 -06:00
parent f2f98285ef
commit 2bc859072f
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@ -157,8 +157,8 @@ will be import into Python as a dictionary.
* The schedule is a list of dictionaries each consisting of `time` in UTC, * 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 `day` of the week, the `irc` meeting room, and the `frequency` of the
meeting. Options for the `frequency` are `weekly`, `biweekly-even`, and meeting. Options for the `frequency` are `weekly`, `biweekly-even`,
`biweekly-odd` at the moment. `biweekly-odd`, and `adhoc` at the moment.
`biweekly-odd` are weeks where the ISO week number is an odd value. `biweekly-odd` are weeks where the ISO week number is an odd value.
Correspondingly `biweekly-even` are weeks where the ISO week number is even. Correspondingly `biweekly-even` are weeks where the ISO week number is even.
@ -166,6 +166,10 @@ will be import into Python as a dictionary.
2015 has 53 ISO weeks (an odd value) and then the first week of 2016 is week 2015 has 53 ISO weeks (an odd value) and then the first week of 2016 is week
1 (also an odd value). 1 (also an odd value).
`adhoc` can be used to list the possibility of something in the schedule but
will not actually generate any calendar events. This can be used for
placeholders and will act as a noop when generating the calendar.
:: ::
schedule: schedule: