| Summary | Support for arbitrary recurring events |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Enhancement |
| State | New |
| Priority | 1. Low |
| Owners | |
| Requester | wahnes (at) uni-koeln (dot) de |
| Created | 01/19/2018 (2672 days ago) |
| Due | |
| Updated | 01/19/2018 (2672 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Support for arbitrary recurring events
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
repetition rule (e.g. weekly or bi-weekly), and exceptions to those
rules, which allows for quite complicated types of repeating events
already when used in combination. These kind of recurring events can
be exported and imported to and from ICS files using RRULE statements.
It would be nice if Kronolith and Horde_Date were to also support
recurring events that do not follow a clear repetition rule as well.
Sometimes there are series of events that do not follow a clear scheme.
Also, support for arbitrary recurring events would allow to import ICS
files that use RDATE to define recurring events. Currently, repeating
dates in ICS files that were defined via RDATE are silently dropped
upon import. Lotus Notes is known for generating ICS files with RDATE
statements. Kronolith users dealing with Notes users may get into
trouble because they miss repeating events they were invited to.