Feature Request: make public calendars writeable

[tessus]

I came across a few use cases where it would be helpful to use a shared calendar with people who

• have the link to the shared calendar
• do not have an account

What do you think? Does this make any sense? Can this be done easily or does this require a major code change?

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[georgehrke]

What do you think? Does this make any sense?

Yes, makes sense. Especially when combing with sharing only the dates but not every detail of the event. As some kind of public free busy.

Can this be done easily or does this require a major code change?

Major as far as i can tell

[tessus]

Thanks for the reply.

Especially when combing with sharing only the dates but not every detail of the event. As some kind of public free busy.

Although, this should be optional. In most of my use cases I want a group of people (who do not have an account) to add, change, delete events on a public calendar (maybe there's even a way to allow a combination of access permissions). The calendar is only public, if someone has the link anyway. :-)

Major as far as i can tell

A few thoughts:
Maybe you can use some sort of virtual user in the backend, thus the logic would be the same as using a regular user. When it comes to authentication and authorization of that "public" (virtual user), it just falls through. The end user would not even have to know anything about this "user".

[georgehrke]

Just noticed that this is a duplicate of nextcloud/server#3509