-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Labels
1. to develop
Accepted and waiting to be taken care of
enhancement
feature: caldav
Related to CalDAV internals
feature: dav
Comments
simonspa
added
enhancement
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
labels
Mar 6, 2020
@simonspa A pull-request would be very much appreciated. Thx! |
@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? :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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
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
I would like to open a ticket concerning the functionality mentioned in #679. @georgehrke quoted the CalDAV sharing standard like this:
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:
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.
The text was updated successfully, but these errors were encountered: