Difference between revisions of "Content team"

Jump to navigation Jump to search
no edit summary
(One intermediate revision by the same user not shown)
Line 80: Line 80:
=== Custom Apps ===
=== Custom Apps ===


== Worflows ==
== Workflows ==


=== Zimfarm monitoring ===
Content team has to monitor the farm at https://farm.openzim.org


==== Abnormal task duration ====
At least twice a week, it is necessary to analyze ongoing tasks at and report any task with an abnormal duration.
An abnormal duration is a task which takes longer than 7 days to complete AND which usual duration is either unknown (new tasks) or significantly lower than current duration (few days at least).
For every task with an abnormal duration, an issue must be created in openzim/zim-request with the "Zimfarm Task Duration Issue" [https://github.com/openzim/zim-requests/issues/new/choose template].
The issue must be assigned to:
- the task requestor if the task has been manually requested in the Zimfarm
- Ravan otherwise
==== Failed tasks ====
Whenever possible and at least twice a week, it is necessary to report failed tasks in Github issues.
If the task failure is linked to an new recipe currently being fine-tuned, the failure must be reported in the corresponding existing issue in [https://github.com/openzim/zim-requests/issues openzim/zim-request].
If the task failure is linked to a recipe which already has a "Zimfarm Recipe Issue" issue opened in [https://github.com/openzim/zim-requests/issues openzim/zim-request], then a new comment must be added to the issue.
Otherwise, a new issue must be created in openzim/zim-request with the "Zimfarm Recipe Failure Issue" [https://github.com/openzim/zim-requests/issues/new/choose template]. The issue must first be assigned to Ravan for first diagnosis.
In both cases, the "Bug" label must be placed on the issue.
=== First diagnosis of "Zimfarm Recipe Failure Issue" issues ===
You may do the first diagnosis only if the issue is assigned to you. If the issue is assigned to someone else, please ask for permission first. This rule can be bypassed for obvious reasons is the person is on long leave, sick, ...
This diagnosis is expected to be done within few days, less than a week at most.
To diagnose "Zimfarm Recipe Issue", following criteria have to be analyzed:
- if this the first failure of the recipe in a row?
- do we have a previous task that worked well?
- we don't have obvious message in the scraper log that indicates the recipe is doomed to fail if ran again ?
If the answer is YES to all three questions, then the recipe must be requested again, this might have been a temporary failure.
Otherwise, either the recipe parameters have to be adjusted if the fix is obvious (e.g. "Title is too long error", ...) and the recipe requested again, or the issue must be raised to Benoit for analysis.
=== First diagnosis of "Zimfarm Task Duration Issue" issues ===
You may do the first diagnosis only if the issue is assigned to you. If the issue is assigned to someone else, please ask for permission first. This rule can be bypassed for obvious reason is the person is on long leave, sick, ...
This diagnosis is expected to be done within few hours, less than few days at most.
To diagnose "Zimfarm Task Duration Issue", following criteria have to be analyzed:
- do we still have signs of activity in scraper log (e.g. a log from less than 1 day ago) ?
- for scraper reporting progress, are the progress number relevant to have completion within 30 days ?
- is the task running for less than 30 days ?
If the answer is YES to all three question, then you should let the task continue and reassess within few days.
If the answer is NO to any of these questions, then the issue must be raised to Benoit for analysis.
=== (draft) Notes from former Youtube workflow (Draft) ===
## To create a new recipe for youtube files
## To create a new recipe for youtube files


26

edits

Navigation menu