[Tickets #3965] Re: Track the Organizer of 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/3965
------------------------------------------------------------------------------
  Ticket           | 3965
  Aktualisiert Von | Ralf Lang (B1 Systems GmbH) <lang at b1-systems.de>
  Zusammenfassung  | Track the Organizer of events
  Warteschlange    | Kronolith
  Version          | Git master
  Typ              | Enhancement
  Status           | Accepted
-Priorität        | 1. Low
+Priorität        | 2. Medium
  Milestone        |
  Patch            |
-Zuständige       |
+Zuständige       | Ralf Lang (B1 Systems GmbH), Horde Developers
------------------------------------------------------------------------------


Ralf Lang (B1 Systems GmbH) <lang at b1-systems.de> (2015-01-08 19:33)  
hat geschrieben:

I think I will have a look into this, as use cases pile up where it's  
really annoying.
I'll do it as a pull request though because of the review workflow.  
I'm not sure how "core" I am these days.

Things to touch:

- Enhance db schema to include an organizer field
- Use the organizer field in Kronolith::sendItipNotification instead  
of the creator field
- Use the organizer field in Event::toiCalendar, Fall back to creator  
when no organizer value is present
- Use the organizer field in Event::fromiCalendar, leave blank if non set.
- Use the organizer field in Event::fromHash, leave blank if non set.
Open question: Set or don't set organizer field, if organizer is the  
current user?
- Use the organizer field in Event::toASAppointment, fall back to  
creator otherwise.

Open question: Do we need to handle this for Resources, app-generated  
content and Kolab as well?