nextcloud / nextcloud/whiteboard
Allow to use existing nextcloud-spreed-signaling backend to simplify setup
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
Whiteboard requires separate backend for live collaboration.
Would be nice to merge whiteboard backend with nextcloud-spreed-signaling if possible to simplify setup and maintenance.
For future consideration: one common nextcloud signaling backend for all nextcloud applications that need live collaboration.
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 with the Whiteboard README's websocket-server section and the linked nextcloud-spreed-signaling project to understand the two backend setups. The issue does not identify files, tests, compatibility requirements, or concrete completion criteria, so a design and implementation scope would need to be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100