No global staging area, one staging area per collection
Open
Nobody has claimed this yet.
bug
question
- Dominant language
- Python
- Stars
- 7
- Forks
- 1
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 18
Description
No reason to have dfferent rules regarding privacy than the one applied to the collection itself.
See https://github.com/openzim/cms/issues/177#issuecomment-4321236806
Contributor guide
No contributing guide indexed for this repository
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 reading the discussion linked in issue 177, especially the referenced comment, then trace how staging areas, collections, and privacy rules are represented in the CMS. The issue is complete when staging is scoped per collection and the privacy behavior matches the collection's rules, with the relevant behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100