Tell us your story
Tell us your story
How has offline Wikipedia affected you? The Wikimedia Foundation (the non-profit that supports Wikipedia) is looking for personal, diverse and inspiring stories about how offline Wikipedia affects the world. If you have a personal story that you would like to share, please contact: stories@kiwix.org. Thank you!

Difference between revisions of "Hackathon Spring 2017"

From Kiwix
Jump to: navigation, search
(Goals: Added discussion topic on in-app device info feedback.)
(Group Discussion Topics: Added a meeting about automatic testing)
Line 52: Line 52:
 
==== Intro ====
 
==== Intro ====
 
We believe large numbers of users only use the app briefly before abandoning it. There are various ideas why this might be so. Perhaps they don't understand what the app can do for them, or they may find it hard to get started. There may be problems downloading content, etc. Also, with our growth in custom apps, including non-Wikipedia content such as PhET simulations, perhaps the user interface, menu options, and some of the functionality is a poor fit for the content and capabilities. We'd like to discuss the UX, including onboarding (getting users from first starting the app to using it productively), and consider ways we might usefully improve the UX.
 
We believe large numbers of users only use the app briefly before abandoning it. There are various ideas why this might be so. Perhaps they don't understand what the app can do for them, or they may find it hard to get started. There may be problems downloading content, etc. Also, with our growth in custom apps, including non-Wikipedia content such as PhET simulations, perhaps the user interface, menu options, and some of the functionality is a poor fit for the content and capabilities. We'd like to discuss the UX, including onboarding (getting users from first starting the app to using it productively), and consider ways we might usefully improve the UX.
 +
 +
=== Automatic testing ===
 +
When: Wednesday 5th April 2017
 +
==== Intro ====
 +
Some repos already have automatic testing (unit tests and/or UI tests). Some other ones plan to add it.
 +
 +
We should discuss our experience/ideas on that topic, and see if we could do something in common.
  
 
== Achievements ==
 
== Achievements ==

Revision as of 09:17, 4 April 2017

This page summarizes the action plan for the Kiwix Spring Hackathon 2017.

Goals

Android
  • Setup the Android automated testing up and make a proof of concept
  • Release a new version of Kiwix for Android (maybe a first version with multizim support?)
  • Implement Wikimed Feedback solution
  • Implement a solution to allow non-tech to launch/update Android custom apps
  • More sophisticated bookmark
  • Work on 2.3 release
  • Consider possible ways to enable users to provide device-info such as storage locations to help us improve support for their devices.
Scrappers (Python)
  • Fix Gutenberg scrapper and generate new ZIM files
  • Fix KALite ZIM export (for a first release)
  • Create a fully automatized solution for Stackexchange projects ZIM files
Scrapper Mediawiki (Nodejs)
  • Implement Wikihow scrapper (non-parsoid Mediawiki scraper)
  • Scrape categories
  • Support videos (if Parsoid allows it)
Phet
  • Release a new version of Phet Simulation with an improved UX
HTML5 (Javascript)
  • Launch the first pure HTML ZIM read browser extensions (FF+Chrome)
Search
  • Fix fulltext search/indexes problems
ZIM building
  • Setup a ZIM building scheduler (with Celery?)
Ideascube builder
  • Get a Qemu Raspbian image ready in Travis

Apache

Group Discussion Topics

During the hackathon we'd like to discuss various topics collectively. These include:

  • UX and particularly Onboarding
  • Desktop apps
  • Incorporating analytics

We aim to agree a topic with about a day's notice so those who wish can do some preparation, e.g. reading up, sharing ideas and notes, etc.

UX & Onboarding

When: 14:00 ish Tuesday 4th April 2017

Intro

We believe large numbers of users only use the app briefly before abandoning it. There are various ideas why this might be so. Perhaps they don't understand what the app can do for them, or they may find it hard to get started. There may be problems downloading content, etc. Also, with our growth in custom apps, including non-Wikipedia content such as PhET simulations, perhaps the user interface, menu options, and some of the functionality is a poor fit for the content and capabilities. We'd like to discuss the UX, including onboarding (getting users from first starting the app to using it productively), and consider ways we might usefully improve the UX.

Automatic testing

When: Wednesday 5th April 2017

Intro

Some repos already have automatic testing (unit tests and/or UI tests). Some other ones plan to add it.

We should discuss our experience/ideas on that topic, and see if we could do something in common.

Achievements

Impact

This hackathon gathers different kind of tasks which all in one will help to implement the Wikimed Projet and reach our goals in term of new content for 2017.

Method

~ 10 developers meet during a week to make this steps forward.

Place

The hackathon will take place in Lyon, France

Agenda

  • April 2th afternoon: arrivals (suggested arrival time 5PM)
  • April 3th -> 9th: Kiwix hackathon
  • April 9th afternoon: departures (suggested departure time 3PM)

People

Travel + Accommodation
  • Adrian
  • Elad
  • Emmanuel
  • Joe
  • Julian
  • Rashiq
  • Renaud
Sponsored
  • Hayley
Only Travel
  • Isaac
Located in Lyon
  • Matthieu
  • Mossroy
  • Guillaume

Costs

  • Accommodation: ~4.000 CHF
  • Travels: ~2.000 CHF
  • F&B: ~3000 CHF

-> ~9.000 CHF