nextcloud / nextcloud/server

Create API/service to build VTIMEZONE components for events

Open
#42,145 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement feature: caldav feature: dav
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

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

As a Nextcloud developer I may have to create a VEVENT object in the backend. I might have a timezone id available, but for a full fledged VEVENT component there is no easy way to create the VTIMEZONE spec.

Describe the solution you'd like

Create an API/service to build such VTIMEZONE components for a given timezone ID.

https://github.com/nextcloud/calendar/pull/5339 added a simple approach for this for Calendar. For a holistic solution we might have to ship timezone data.

Describe alternatives you've considered

N/a

Additional context

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 reviewing nextcloud/calendar pull request #5339 and the linked Sabre vobject discussion to understand the existing approach and constraints. The work is done when the server has a defined API/service that builds VTIMEZONE components from a timezone ID, including an agreed approach for shipping timezone data.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.