Automatically disable ZF recipe if problem is in scraper
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 #100
This still has be be refined. This revolve around the central question of how we organize interactions between Zimfarm operators and CMS operators. We are still in the infancy of this discussion.
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 linked context in #100 and the discussion described in this issue. No files, tests, or entry points are named; the work is not ready until the interaction between Zimfarm operators and CMS operators is refined and the expected behavior for scraper problems is defined.
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