nextcloud / nextcloud/calendar

Clarify public sharing link

Open
#5,398 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug design Feature: Public sharing
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Is your feature request related to a problem? Please describe.

Apparently it is not possible to share a Nextcloud calendar to the Google Calendar web front end.

You can integrate the calendar https://website.com/apps/calendar/p/xxxxxxxxxxxxxx in Google Calendar, but no appointments are displayed.

Describe the solution you'd like

It should be possible to release the calendar as an ICS file so that it can be integrated into other calendars.

Describe alternatives you've considered

No response

Additional context

Since you can only send appointments to external people inconveniently (ics as an attachment, no updates when appointments change) and also cannot share them with external people, the Nextcloud calendar is unfortunately only suitable for internal purposes or for individual people.

That's why I can't completely switch to my Nextcloud.

Unfortunately, I can't even integrate the Google calendar in the Nextcloud and manage the appointments here, because you can only integrate them as read-only.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the public calendar link in Google Calendar and compare it with the requested ICS/webcal behavior. Read the calendar sharing and CalDAV-related entry points, then check the RFC 5545 expectations referenced by the repository topics. Done means an externally shared calendar can be integrated and its appointments appear in Google Calendar.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.