Kiwix/Quarterly goals 18-19
As part of our grant agreement and related annual plan with the Foundation we try to set and report on quarterly goals.
Q4 (April-June)
edit| Annual plan outcome | Corresponding output | Platform | Quarterly goal | Dependencies |
|---|---|---|---|---|
| 1. People without internet access use Kiwix to access Wikimedia contents. | Release zim files built for mobile devices | KaiOS | Wikimed selection in 10-12 languages available on KaiOS' Life platform. | KaiOS |
| Topical zim generation | MWOffliner | Finish release of zim files built for mobile devices based off research. Files should be 100mb or less in size, multilingual, and topic-specific (currently 7/98). | ||
| 2. Kiwix code makes it easier for technical contributors to develop new features and maintain existing code. | Professionalize | Android | Hire Android Project Manager | |
| Android redesign | Android | Participate in Google Summer of Code | Volunteers | |
| Android redesign (from Q3) | Android | Redesign and implement library;
Fix multiple secondary usability / stability problems |
Q3 (January-March)
edit
| Annual plan outcome | Corresponding output | Platform | Quarterly goal | Dependencies |
|---|---|---|---|---|
| 1. People without internet access use Kiwix to access Wikimedia contents. | Automation of zim file generation | MWOffliner | “Fresh” content available for download with the release of a fully automated zimfarm. New versions of existing zim files would be available for download on a scheduled basis (monthly for 90% of files, bimonthly for largest). Automate zim landing pages generation | |
| 2. Kiwix code makes it easier for technical contributors to develop new features and maintain existing code. | GCI | Kiwix-android | Participate in Google Code-in | Volunteers |
| Android redesign | Kiwix-android | Redesign and implement library;
Fix multiple secondary usability / stability problems |
Q2 (October-December)
edit
.
| Annual plan outcome | Corresponding output | Platform | Quarterly goal | Dependencies |
|---|---|---|---|---|
| 1. People without internet access use Kiwix to access Wikimedia contents. | 1. Topical zim generation | MWOffliner | Release zim files built for mobile devices based off research conducted by Wikimedia Foundation Android team in 2017. Files should be 100mb or less in size, multilingual (10 languages), and topic-specific (10 topics). | |
| 2. Farming | MWOffliner | MW Offliner maintenance. Release v1.8+ | ||
| 3. Strategy | All | Publish draft strategy for Customer audience (e.g. NGOs) | ||
| 2. Kiwix code makes it easier for technical contributors to develop new features and maintain existing code. | 4. Android redesign | Kiwix-android | Kiwix Android maintenance | Volunteers |
| 5. Professionalize | OpenZIM
Kiwix-android |
Objective:
Hire contracted UX/UI designer and Android developer by end of quarter. Key results: Both contractors start working on October 1st (or closest available date). |
WMF (for UX) |
Q1 (July-September)
edit
.
| Annual plan outcome | Corresponding output | Platform | Quarterly goal | Dependencies |
|---|---|---|---|---|
| Kiwix code makes it easier for technical contributors to develop new features and maintain existing code. | 4. Android redesign | Android | Objective:
GSoC interns complete their respective projects Key results: - Improved Continuous integration setup; - Acquire baseline for code coverage; - Improved UX; |
|
| 5. Professionalize | OpenZIM
Kiwix-build |
Objective:
Recruit NodeJS and Python contractors by end of quarter. Key results: Both contractors start working on October 1st (or closest available date). |
||
| 6. Solve platform-specific issues | Android | Objective:
Zürich hackathon runs September 17-23rd; Key results: |
Google Zürich |