Emulating a shared calendar: Automatically setting a default ORGANIZER & default ATTENDEE list

[delthas]

Hi,

I'm setting up a shared CalDav calendar for me and my friends. The goal is to have a single calendar that all of us can edit and let others know if we'll attend events.

The solution I've found is to have a single calendar (a regular "user" calendar, really; that everyone has R/W access to, by setting the auth config type to authenticated)). With this, everyone can add, edit, and delete events. This is working fine.

The issue is that these events are created as "personal" events, there is no ORGANIZER or ATTENDEE field set by any app by default when I create an event without explictly specifying any attendees. I could ask my friends to always manually add the 10 of us explicitly as attendees on all events they create, but this is tedious and error prone.

Without ORGANIZER and ATTENDEE, there is no way to know who created the event, or who will attend.

Instead, I'd like to tell Radicale that for a given calendar:

• by default, the ORGANIZER field should automatically be set, to the user creating the event
• by default, the ATTENDEE field should automatically be set, to a list of users (I'd put a list of all my friend emails here)

With this change, everyone would see who creates what event, and have an option in their GUI to list who will be attending what, and to specify if they'll attend.

I was going to just fork Radicale and add a one-off hardcoded change locally. But would there be a better way to do this, or to address this use case in general?

[pbiering]

if such feature should be made of generic use I recommend to put all of the configuration into new properties into .Radicale.props of such a collection. A WebUI extension would then be able to configure this somehow. If ORGANIZER should also be an e-mail, one has to assure that the radicale user is also an e-mail address to avoid any other strange magic.