Overview: Calendar Sharing

nextcloud / server

☁️ Nextcloud server, a safe home for all your data

https://nextcloud.com

GNU Affero General Public License v3.0

26.64k stars 3.99k forks source link

Overview: Calendar Sharing #20096

Open georgehrke opened 4 years ago

georgehrke commented 4 years ago

This is an overview ticket for feature requests / bugs related to Calendar Sharing:

Sharing

[ ] https://github.com/nextcloud/server/issues/1600
[ ] https://github.com/nextcloud/server/issues/1440
[ ] https://github.com/nextcloud/server/issues/1653
[ ] https://github.com/nextcloud/server/issues/19568
[ ] https://github.com/nextcloud/server/issues/5551
[ ] https://github.com/nextcloud/server/issues/11214
[ ] https://github.com/nextcloud/server/issues/19827
[ ] Contacts Birthday calendar should be shareable
[x] https://github.com/nextcloud/server/issues/26668
[ ] https://github.com/nextcloud/server/issues/5050
[ ] https://github.com/nextcloud/calendar/issues/2659

Publishing

Features missing for feature parity with file-sharing:

[ ] Share with e-mail address
[ ] Option for forbid resharing
[ ] expiry date
[ ] Add note to sharee
[ ] #27545 password protect (public)
[ ] Hide download (public)

georgehrke commented 4 years ago

cc @tcitworld cc @rullzer for feature planning :)

georgehrke commented 4 years ago

One of the biggest issue when it comes to publishing is that each calendar is limited to one publishing link.

This is causing many issues that you can't simply revoke a calendar without breaking embedded calendars / having to send out a new public link to people who should still have access.

In order to solve any of the publishing related tickets mentioned above, we first need support for multiple publishing links. Once we have support for that, adding support for more sharing types including "internal busy", "public busy", "public editable", "public busy editable" should be straight forward.

georgehrke commented 4 years ago

Once we have support for these public types, adding password-protected public shares or shares with expiration-link would also be straight forward.

georgehrke commented 4 years ago

Overall tasks:

[ ] discuss new columns that have to be added to dav_shares.
[ ] discuss changes to CalDAV sharing and publishing API.

georgehrke commented 4 years ago

also cc @raimund-schluessler @skjnldsv

This will require changes to cdav-library, but i aim at implementing them in a backward-compatible way.

tcitworld commented 4 years ago

Can cs:publish-url handle multiple URLs ? We'll have to go with our own thing otherwise.

georgehrke commented 4 years ago

Can cs:publish-url handle multiple URLs ? We'll have to go with our own thing otherwise.

Not as far as i can tell. We would have to move to our own implementation.

favincen commented 3 years ago

Hi. I suggest to add also a link to issue "Send invitations for shared calendars" #26668 , as it is about shared calendars expected features.

favincen commented 3 years ago

This overview of calendar sharing issues could also reference #5050 issue about sharing from MacOS Calendar.app.

ESIETP commented 3 years ago

Hi, maybe the "No invites, but invite cancellations sent from shared calendars" #20278 is also a part of this?

tcitworld commented 3 years ago

That's a bug, not a feature.

ZID-TU-Graz-Collab commented 1 year ago

I suggest to add #19994 (as mentioned in the this issue, the problem still occurs in our installation, NC Version 26.0.4)

gnrfzui commented 6 months ago

I suggest to add #19994 (as mentioned in the this issue, the problem still occurs in our installation, NC Version 26.0.4)

Seconded: #19994 is still open with NC 27.1.5 and Calendar 4.6.6