Re-enable ACL's for Teamfolders
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
For several organizations, ACL's are really a key feature for Team folders. We should re-enable this for 35.0.1.
We disabled it to keep things simpler, but it would mean quite some orgs can't use 35's new Team folder concept. I would thus suggest simply turning it on again.
NOTE, quoting @artonge
Also, I can see an issue coming with ACL + .system folder in which we store the Teams data, which means, everybody should be able to read and write to it.
So we have to solve that first. Let's see if that is doable for .1
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 how ACLs interact with Team folders and the .system folder that stores Teams data. Resolve whether the .system folder can remain readable and writable as required, then verify that ACLs are re-enabled without exposing or blocking the Teams data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100