nextcloud / nextcloud/calendar
Improvements to Talk conversation creation
Open
Nobody has claimed this yet.
1. to develop
enhancement
Feature: Integration
Feature: Talk
- 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.
- If meeting is intended for internal users, new room shouldn't be public, but listable (open for users to join). Ref https://github.com/nextcloud/calendar/issues/7075
- Creation can be deferred, to fill room with event attendees afterwards
- In case it's public, (or has email attendees, and should be public atm), and password policy is enforced on instance, it would still fail, so need to be checked in UI
- in UI use 'Talk conversation' rather than 'Talk room' -> addressed in #6658
Describe the solution you'd like
👆
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing Talk conversation creation flow in the calendar app and read the linked calendar issue #7075 for the internal-meeting behavior. Check how public rooms, email attendees, deferred creation, and instance password policies are currently handled; done means these cases work consistently in the UI and creation flow. No file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100