547
edits
Difference between revisions of "Content team"
Jump to navigation
Jump to search
→Workflows
| Line 107: | Line 107: | ||
# Re-enable the recipe in Zimfarm (''a priori'' @RavanJAltaie) | # Re-enable the recipe in Zimfarm (''a priori'' @RavanJAltaie) | ||
==== Abnormal scrapes duration ==== | |||
==== Abnormal | |||
At least twice a week, it is necessary to analyze ongoing tasks at and report any task with an abnormal duration. | At least twice a week, it is necessary to analyze ongoing tasks at and report any task with an abnormal duration. | ||
| Line 131: | Line 120: | ||
- Ravan otherwise | - Ravan otherwise | ||
==== Failed | ==== Failed scrapes ==== | ||
Whenever possible and at least twice a week, it is necessary to report failed tasks in Github issues. | Whenever possible and at least twice a week, it is necessary to report failed tasks in Github issues. | ||
| Line 142: | Line 131: | ||
In both cases, the "Bug" label must be placed on the issue. | In both cases, the "Bug" label must be placed on the issue. | ||
=== | ==== 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, ... | 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, ... | ||
| Line 159: | Line 148: | ||
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. | 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 === | ==== 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, ... | 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, ... | ||
| Line 175: | Line 164: | ||
If the answer is NO to any of these questions, then the issue must be raised to Benoit for analysis. | If the answer is NO to any of these questions, then the issue must be raised to Benoit for analysis. | ||
=== Library Management === | |||
==== Deleting a ZIM ==== | |||
Deleting a ZIM which has already been published is not a negligible action. It has impact on the library and on the [https://imager.kiwix.org Kiwix Hotspot Imager], where actions must be coordinated. | |||
It is hence mandatory that, whenever a recipe/ZIM needs to be deleted, [https://github.com/openzim/zim-requests openzim/zim_requests a ticket is opened on GitHub] and assigned to both @benoit74 and @rgaudin for proper coordination: | |||
# Wait until there are no more in-progress Orders in the Kiwix Hotspot Imager that include those ZIMs (''a priori'' @rgaudin) | |||
# Delete ZIMs on the file server (''a priori'' @benoit74) | |||
# Trigger Kiwix Hotspot Imager catalog refresh right after the move so any Order created right after uses the new URL (''a priori'' @rgaudin) | |||
''Nota'': Moving a file to the archive has to be considered as a file deletion. | |||
=== (draft) Notes from former Youtube workflow (Draft) === | === (draft) Notes from former Youtube workflow (Draft) === | ||