[Tickets #14769] Support for arbitrary recurring events

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14769
------------------------------------------------------------------------------
  Ticket           | 14769
  Erstellt Von     | wahnes at uni-koeln.de
  Zusammenfassung  | Support for arbitrary recurring events
  Warteschlange    | Kronolith
  Version          | Git master
  Typ              | Enhancement
  Status           | New
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


wahnes at uni-koeln.de (2018-01-19 13:47) hat geschrieben:

Kronolith currently supports recurring events that follow a clear  
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.