nextcloud / nextcloud/calendar

Default Event Transparency

Open
#3,992 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
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.

We can choose if an event will be expose, mark occupied, or hidden through a share, nice.
For a new event, it is by default as exposed.

Describe the solution you'd like

I would have choiced "mark occupied" for the new events by default.
Or, maybe a way to set that in occ commande ?

Describe alternatives you've considered

Or, maybe a way to set that in occ commande ?

Additional context

In a privacy perspective, When I someone open his agenda for the first time, All precedents events with possibility off privacy concern are actualy exposed.

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

The issue names no file, test, or entry point. Start by clarifying whether the default should be “mark occupied” for all new events and whether an occ command setting is also required; done should include a defined default and documented behavior that prevents unintended event details from being exposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.