Attachment handling improvements
Open
Nobody has claimed this yet.
design
feature: api 🛠️
feature: frontend 🖌️
feature: upload & shares & voice 📤🎙️
overview
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
During the team week we discussed various improvements to solve various issues that we have:
- Too big folders
- Virtual Sync issue Mac
- Memory limit
- Amount of mount points
.attachmentsfolder hiding all apps, read from oc_preferences in server: https://github.com/nextcloud/server/issues/46309- Group by token https://github.com/nextcloud/spreed/issues/4340
- Would allow https://github.com/nextcloud/spreed/issues/6469
- Group by Year/Month/
- Still have 8k Mountpoints with this
- OCC command to migrate files after upgrade to the new architecture
- Would easily allow https://github.com/nextcloud/spreed/issues/7793
- Allow moderators to share a folder for guest / people without quota upload https://github.com/nextcloud/spreed/issues/3343
- User shares a folder one-time and then all their uploads go into this
- Contradicts a bit with the Y/M/ separation from UX
- Problem with everyone having "Shared Conversation name" or "Shared by user_id"
- Would make https://github.com/nextcloud/spreed/issues/7462 impossible
- #15309
- Sort into
.attachments/{Talk}/{token} - Allow sharing as "other moderator" not only the one that started the recording
- Not obvious when it's still "to share" or failed uploading etc.
- Video, Summary and Transcribe are not linked/grouped together
- Sort into
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 reviewing the listed attachment concerns and the linked issues, especially #15309, to understand the competing storage and sharing requirements. Done would require a decided attachment architecture that addresses the stated folder size, mount-point, grouping, sharing, upload-status, and linking concerns.
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
- 20/100