Difference between revisions of "Content team"
Jump to navigation
Jump to search
(→Duties) |
|||
Line 19: | Line 19: | ||
** Keep the tickets up2date | ** Keep the tickets up2date | ||
* | * Scraping | ||
** Ensure Zimfarm works fine and contribute to its improvements with dev. team | ** Ensure Zimfarm works fine and contribute to its improvements with dev. team | ||
** Analyses failures or unexpected behaviors | ** Analyses failures or unexpected behaviors |
Revision as of 12:38, 15 December 2023
The Content team gathers people in charge of providing books in the ZIM format. It has emerged - as effort - in the early 2020s as part of a strong content strategy.
Purpose
Provide the best possible (appealing, up2date, small, 'market ready', ...) library of ZIM based books.
Goals
- Books topics should stick to needs
- Books should have proper visual formatting
- Books should be up-to-date
- Library should allow to discover quickly and nicely (new) books
Duties
- Requests
- Collaborate with requesters to qualify requests properly. Keep them informed.
- Ensure we are allowed and able to fullfill requests
- Initiate new recipes and manage first publishing if new book
- Collaborate with scraper dev. team if necessary
- Keep the tickets up2date
- Scraping
- Ensure Zimfarm works fine and contribute to its improvements with dev. team
- Analyses failures or unexpected behaviors
- Ensure recipes run properly, fix configuration when necessary and contribute to scraper improvements with dev. team
- Ensure workers are online and are properly configured
- Ensure scrapes lifecycle is correct (Reasonable pipeline size, Running scrapes progressing appropriately, not too many failures)
- CMS
- Ensure ZIM filenames and location (paths) are correct
- Ensure ZIM Metadata are correct
- Ensure ZIM are recent and kept up2date (AFAP)
- Ensure library is coherent and user-friendly
Members
- Popolechien, manager in line
- Ravan, content manager
- Benoit74, scrapers lead dev