Workflow for Groups / Centralised Attachments
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Hey there..
we try to use Deck including attachments.. but those attachments are stored in the personal space of the user who attached a file. this is a problem for us, since the personal space of each user is VERY limited.. and the membership of groups vary.. so, when a user is no longer part of a group, that worked on a deck, this results in loosing the attachments?
Whatabout centralising attachments in a specific folder?
How do you mange this with vareiing group constellation and/or limited personal space?
THX
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
The issue does not name files, tests, or entry points. Start by reviewing how Deck currently stores attachments and handles group membership, then determine how a group-specific attachment location should work when membership changes. Done means attachments are not tied to a departing user's limited personal space and remain available to the group.
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