WIP: [RFC] Calendar composition #21
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DGNum/metis#21
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In a large enough organization (e.g. my life or ENS), there will be a point where many calendars are so atomic that it is difficult to work and share them without sharing a bundle of calendars, plus, sometimes, we would like to rewrite events to hide private details or show only the occupied status for scheduling purpose.
An nice way to perform this in a low-tech fashion is to create a new calendar as a composition of different calendars, through synchronization with, e.g. vdirsyncer.
It would be interesting to see how can we implement this in our project to enable calendars of AGs, return to school, etc.