Define publication strategy per catalog + apply it on catalog generation
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- Python
- Stars
- 7
- Forks
- 1
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 18
Description
From https://github.com/openzim/cms/issues/100
@rgaudin do you recall exactly what this meant to you?
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 referenced issue #100 and the single comment on this issue to recover the intended publication strategy. No files, tests, or entry points are identified, so first clarify the per-catalog rules and the expected catalog-generation behavior; done criteria are not yet specified.
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
- 25/100