Difference between revisions of "Zurich 2018"

Revision as of 19:16, 14 September 2018

This page summarizes the action plan for the Kiwix Google Zürich Hackathon 2018.

Goals

Mossroy

In Kiwix-js:

Stabilize and optimize the ServiceWorker mode, to try to make it the default mode (on platforms that support it). This mode should be much more sustainable in the long term. Some help would be welcome on how to use the browser cache in this context
Improve performance by using WebAssembly (on platforms that support it) for the bzip2 decompression. Preliminary tests let us hope around 30% performance improvement.
Investigate on compiling the libzim to WebAssembly. If it's technically possible, it would allow to benefit from all the features and optimizations of this library, without the need of re-implementing them. If the people from Google know this technology, it might be a topic where they would be helpful.

Isaac

In Kiwix-Android:

Work on 3.0
Download improvements (improve stability)
Search Improvements / Discussions

Julian

In Kiwix-Android:

Implement test code coverage report in Travis see https://github.com/kiwix/kiwix-android/issues/836
Help to reduce the number of crashes occurring for our users. Isaac agree the download manager code is the epicentre of many of the problems and he's planning to revise it during the hackathon. I'm happy to help with testing the changes.

Emmanuel

Conclude preparation of projects for full automation and mwoffliner improvements
Fix https://github.com/resin-io/etcher/issues/2274 if possible
Migrate our wiki to Docker

Renaud

Release Kiwix-plug installer 2.0.
Setup master builds more frequently and tie it to nigtly builds (#171).
Replace dependencies that are too exotic and problematic (pygobjects to PyQT?).
Revamp UI to fix UI-speed issues.
Update dependencies to latest stable.
Update travis/appveyor to latest stable image.
Draft pibox Documentation.
Harmonize coding style (black?).
Prepare pibox for localization (#43).
Have an alpha cardshop
Prepare the next project

Joe Reeve (ISNIT0)

Become more familiar with the MWOffliner codebase
Overhaul PhET app UI/UX
Assist with Kiwix-Android testing/development

Magnus

Get familiarised with the OpenZim codebase
Successfully compile all OpenZim tools
Resolve various bugs, build issues, and crashes

Achievements

Impact

Method

~ 8 developers meet during a week to make a few steps forward.

Place

The hackathon will take place in Zürich, Switzerland: 3 days @Google offices, the rest at the residency.

Agenda

September 16th afternoon: arrivals (suggested arrival time 5PM)
September 17th -> 23th: Kiwix hackathon (17th -> 19th @Google)
September 23th afternoon: departures (suggested departure time 3PM)

People

Emmanuel (in the field)
Isaac (Sunday - Sunday /w one day break in the middle)
Joe (Monday - Friday)
Julian (Monday - Friday)
Mossroy (Sunday - Sunday)
Renaud (Saturday - Sunday)
Magnus (Sunday - Thursday)

~~Dattaz~~
~~Rashiq~~
~~Matthieu~~
~~Guillaume~~

Costs

Accommodation: ~4500 CHF
Travels: ~700 CHF (local)
F&B: ~ 2500 CHF

-> ~

@@ Line 5: / Line 5: @@
 === Mossroy ===
 In Kiwix-js:
-* Stabilize and optimize the ServiceWorker mode, to try to make it the default mode (on platforms that support it). This mode should be much more sustainable in the long term.
+* Stabilize and optimize the ServiceWorker mode, to try to make it the default mode (on platforms that support it). This mode should be much more sustainable in the long term. Some help would be welcome on how to use the browser cache in this context
 * Improve performance by using WebAssembly (on platforms that support it) for the bzip2 decompression. Preliminary tests let us hope around 30% performance improvement.
 * Investigate on compiling the libzim to WebAssembly. If it's technically possible, it would allow to benefit from all the features and optimizations of this library, without the need of re-implementing them. If the people from Google know this technology, it might be a topic where they would be helpful.