Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-user settings for shared events #19827

Open
Tracked by #20096
simonspa opened this issue Mar 6, 2020 · 4 comments
Open
Tracked by #20096

Per-user settings for shared events #19827

simonspa opened this issue Mar 6, 2020 · 4 comments
Labels
1. to develop Accepted and waiting to be taken care of enhancement feature: caldav Related to CalDAV internals feature: dav

Comments

@simonspa
Copy link
Contributor

simonspa commented Mar 6, 2020

I would like to open a ticket concerning the functionality mentioned in #679. @georgehrke quoted the CalDAV sharing standard like this:

In section 5.5.4 it says:

Servers MUST support "per-user" calendar data in calendar object resources stored in shared calendars. This allows each sharee and the sharer to store their own alarms and free busy transparency status without "interfering" with other users who also have access to the same calendar object resources.

However, in the related PR #6903 only the minimal solution of silencing shared read-only calendars was implemented if I understand correctly. I would like to come back to this "full feature set" because of the following use case - which I suspect is very common:

  • I am subscribed to many calendars (read-only) with seminars, lectures, meetings
  • Some I have to attend or find interesting, so I would like to
    • set a reminder for them
    • set my own status to "busy" during these meetings

Right now I basically have to create a duplicate event in my own (writable) calendar to be able to do this. The cherry on the cake would be if this would also work for WebCal subscriptions.

@simonspa simonspa added enhancement 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Mar 6, 2020
@georgehrke
Copy link
Member

@simonspa A pull-request would be very much appreciated. Thx!

@simonspa
Copy link
Contributor Author

simonspa commented Mar 6, 2020

@georgehrke Phew, don't you think this would even qualify for "technical depth" and is a bit over the top for a rookie like me? :)

@quentinDupont

This comment has been minimized.

@tcitworld

This comment has been minimized.

@szaimen szaimen added 1. to develop Accepted and waiting to be taken care of and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Jul 28, 2021
@ChristophWurst ChristophWurst added the feature: caldav Related to CalDAV internals label Dec 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of enhancement feature: caldav Related to CalDAV internals feature: dav
Projects
None yet
Development

No branches or pull requests

6 participants