pimutils / pimutils/vdirsyncer

Feature request: option to only sync calendar event time start and time end

Open
#1,083 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: enhancement
Dominant language
Python
Stars
1.9k
Forks
185
Avg merge
11h 49m
Merged PRs (30d)
1

Description

It would be great if folks could specify which specific elements of the calendar events they would like to sync. It would be great if I could make a calendar event on a secure calendar, filled with sensitive information, and then see a "blank" calendar event pop up for the same time slot on a much less secure public facing calendar.

I use nextclouds appointment calendar system so people can schedule meetings with me. The app looks through exsisting calendar events to determine which default slots to present to the user who wants to schedual the meeting.

IE, if someone wants to meet with me, they can schedual a meeting where the 1am, 12pm, 1pm. But if I already have a calendar event at 12:30, the 12 and 1 slots wont be availible. This is essential to prevent double booking and conflicts.

The problem is there are many calendars I use which have events / meetings that contain a great deal of sensitive info, info which is too sensitive to be synced to the public nextcloud instance. But to make calendar appointments work, the nextcloud calendar needs to have those slots filled with something. Currently I have to go through and manually add a bunch of blank busy events, despite having a bunch of neat syncing tools like vdirsyncer.

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

No files or tests are named. Start by locating the calendar event synchronization and configuration entry points, then determine how an option could select only event start and end times while preserving busy slots. Done means a configured sync can omit sensitive event fields and still create usable events for conflict detection.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.