Wikimedia Hackathon 2017/Report



19 – 21 May 2017 | Vienna, Austria

Budget


Exchange rate: 1 EUR = 1,09 USD

Results

 * The Vienna Hackathon was one of the biggest Hackathons in terms of the number of participants: We hosted 250 people over the course of three days
 * The 2017 Hackathon set new standards for inclusivity with the mentoring program and other big and small activities to make the event as diverse and welcoming as possible
 * 56 newcomers were coached by 30 mentors
 * 24% of the participants identified as female or non-binary
 * The event was one of the most productive hackathons ever with a showcase which comprised 46 projects
 * This year's Hackathon got very good feedback from newcomers and old hands alike
 * WMAT as the hosting organisation contributed to sustainable and good practices for this event series and the movement in general, by developing extensive documentation for Hackathons and re-usable templates and materials

Learning and Innovation
WMAT has been preparing this event for two years, attending two Wikimedia Hackathons (Lyon and Jerusalem) and several similar tech events from like-minded organisations and communities. This enabled us to create our own vision for the Mediawiki Hackathon and to make it an event that not only has the desired impact on our own local context but also improves the event format for future Hackathons in the wider Wikimedia movement. We can only encourage this process for other Wikimedia events, especially the ones which travel to different countries and communities from year to year. Instead of just copy and pasting things from the past it can be worthwhile to be bold again and question and re-think exisiting patterns and also look for inspiration outside the Wikimedia movement.

What we learned from others
Amsterdam / Zurich / Lyon Hackathons
 * One of the big learnings of previous hackathons was that hacking and sleeping at the same venue together with a constant supply of food and drinks 24/7 is the best way to cater for the needs of our tech community and provide the basic conditions for a productive event. Hence, we put a lot of thought into choosing the right venue and decided to make the not unrisky financial decision to rent out the complete venue exclusively for the weekend. It required us to make the Hackathon bigger (in terms of participants) - one of the biggest so far in fact - in order to scale the investment and making it worthwhile.

Jerusalem Hackathon
 * Two new ideas that started in Israel were incorporated and refined in our concept for the Hackathon:
 * Pre-Hackathons: There was one held in Palestine just before the main event in Jersualem in 2016. While this event was a reaction to the challenge of closed borders and limited geographical mobility, we decided we want to use the same idea but to celebrate the freedom of mobility and absence of borders in Europe, by cooperating with our partners in the CEE region to host local Pre-Hackathons there and invite the organizers and some of their newcomers to the main event in Vienna. Thanks to the great spirit of collaboration the CEE community, there were Pre-Hackathons in Greece, Romania, Hungary, and the Czech Republic. This helped to spread the impact an event like the Hackathon can have beyond the borders of the hosting country. A summary of what we learned from the Pre-Hackathons across the region can be found in our joint session at the 2017 CEE meeting.
 * Hackathon preparation meetings: Related to the idea of Pre-Hackathons was the a local pre-event in order to help newcomers to get started with Mediawiki and get the best possible preparation for participating in the main event. Wikimedia Israel invited all registered newcomers shortly before the main event for an install party of Mediawiki and a general introduction to the Wikiverse. We build on this idea by hosting twtaptjmgpjtapwdugdtpno pre-events (one for female/non-binary only (see below) and one for all genders), but organized them 6 weeks prior the main event and opened them for all interested participants (not only registered Hackathon attendees) as we thought some newcomers might need to get a taste of the Wikiverse before they want to commit a whole weekend to an event.

Jugend hackt / Ladies that FOSS / Rails Girls
 * We learned about the concept of mentoring programs by attending the Youth Hackathon "Jugend Hackt" in Linz in 2016. We were impressed by the results this event has in teaching young people to code, enabling them to generate first results and success stories in the course of a weekend and creating a sense of belonging in such a short time among a group of strangers. By adapting these pedagogical concepts for our vision of a Hackathon, we realized similar things have been tried before in even more like-minded communities and expanded our benchmarking to these ressources by talking to organizers from Rails Girls and Ladies that FOSS, whch was co-hosted by WMDE. Many of their ressources (e.g. handbooks, training material for mentors etc.) and learning went into the creation of our mentoring program and can be found in the documentatやなまion we created together with our outreach freelancer around Hackathons. We presented a summary of what we learned from others in our 2017 Wikimania session "Hackathon goes Hog家並み中指やは弱は山からなたさやなさなwarts".

New things we tried
Outreach and Mentoring Coordinator
 * As growing the international and national tech community was one of the main goals of the Hackathon, we reflected this emphasis by establishing the role of a Outreach and Mentoring Coordinator. The goal was to find new contributors (from like-minded communities etc) in Austria and coordinate with similar efforts by the WMF on an international level. In addition, it was the first time a mentoring program was applied to a Wikimedia tech event, we needed to adapt the concept, onboard potential mentors and coordinate mentors and newbies. As we did not have the capacity for this in our team, we hired a contractor to specifically work on these topics, as diversity and inclusion take time and resources, especially if we want to reach new audiences and promote equity in our movement. In the long run, if the mentoring program will continue we believe that a lot these tasks can be done by a group of experienced mentors but until then we recommend to allocate sufficient resources as part of the event team. The success of Vienna Hackathon shows that this is time and money well invested.

Stakeholder track
 * A group that has not systematically been catered for by Wikimedia Hackathons are the external stakeholders who work with MediaWiki and Semantic MediaWiki outside of Wikimedia projects, often in a professional capacity. This target group not only contributes to the code but are also potential supporters and sponsors of Wikimedia tech events. Hence we decided to collaborate with the MediaWiki Stakeholders' Group and set up a track during the Hackathon that specifically adresses the interests of these contributors. The track was on the first day of the Hackathon, to cater for business attendees who can't participate on weekends and could be attended independently from the Hackathon. We also asked to buisness participants to support the event with a voluntary contribution towards our expenses. Many of them did, so that the additional participants did not strain the budget of the main event.

Additional communication channels
 * In addition to established means of communication (mailing lists, IRC, Wikis) we decided to also use a chat app which especially for newcomers might be the most intuitive communication channel with the lowest barriers to particpate. We chose Telegram, as other Wikimedia events (e.g. Wikimedia Conference) had good experiences with it and it also has advantages in terms of privacy and data decentralisation compared to other similar apps such as What's App and Facebook chat and can be used from smart phones and laptops likewise. The result of this experiment was quite positive, it created a sense of community among participants even before the event started as people shared travel tipps and helped each other with practical issues (which in a positive side effect also unburdens the event organizers to a certain extent), blog posts and other interesting information were shared during the event, and even months after the event some participants send updates avbout their progress on the projects that they started during the Hackathon. It was also the most convenient means of communication for coordinating sub-groups of event stakeholders such as the mentors or the event organizers. However, we also noticed that especially long-standing community members really do not want to miss their established communication routines, so it should be clearly seen as a supplement and not a replacement for existing channels.

Plushie friendly event
 * Stuffed animals and mascots (some of them organized in the so-called Wikimedia Cuteness Association) became an integral part of our movement. Cuteness is the perfect ice-breaker between strangers and adds to an overall more fluffy and welcoming atmosphere at events. In addition there is scientific evidence that cuteness promotes productivity and positive social motivation. Hence, we proactively wanted to encourage cuteness at the Hackathon, inviting participants to bring their plush friends and making them feel welcome and appreciated by preparing special tiny name tags for them. We also had a cute welcoming committee at the registration desk, which became one of the most popular photo subjects of the event. The name tag idea already caught on and was successfully replicated at WikidataCon in Berlin.

Post-event engagement
 * In addition to the Pre-Hackathons we also wanted to create opportunities for post-event engagement. As Wikidata was the most accessible project for many newcomers we hosted a Wikidata workshop in Vienna in fall which was organized by hackathon participants and also send two of them to attend WikidataCon to Berlin. Further similar activities are planned for 2018.

It does not always need to be a T-shirt
 * When planning our budget our main aim was to have enough resources for the mentoring program, enough food in good quality, and stable WiFi. Hence, give-aways such as T-shirts for all participants were not planned from the start but labeled as a "nice to have" in case there would be enough money left in the end of the day. We finally ended up to provide water bottles, as they were a lot cheaper, easier to handle (no different sizes etc), were the perfect match for an event hosted in Vienna (with excellent mountain spring water from the tap), and was the perfect give-away for a tech event where - compared to glasses and cups - closed bottles are less of a peril for laptops and phones.

Sustainable event materials and consistent corporate design
 * One of the advantages of attending several other Wikimedia Hackathons in preparation of our own event was to get a feeling of which resources could actually be re-used from year to year, so that not every team needs to buy them again only to be used for only one time before being disposed of. We started the process with Wikimedia Israel last year, by asking them to let us re-use their white boards for the tables. We extended this idea to other materials such as roll-ups and banners which we designed in a way that they are not branded specifically for the Vienna Hackathon and can be re-used by the organizers of the 2018 event and beyond. This was made possible by the fact that we worked together with the WMF communication team to create a corporate design for the Hackathon: Instead of having a new logo every year, we now have a consistent concept which matches the CI of the Wikimedia Foundation and the same logo every year, but can also be customized to the local context (with icons etc.) when necessary.

Main Take-Aways


It is worth looking for inspiration outside of our movement
 * For some challenges such as how to make our events more inclusive and newcomer friendly there are some interesting and proven concepts to be found in like-minded communities - we just have to be bold enough to try something new instead of just copying what we used to do before.

Productivity vs. inclusiveness
 * It’s not a zero-sum game: With careful preparation and by managing expectations in advance we can create events that provide productive working conditions for our existing communities while at the same time caters for the needs of newcomers and suitable learning environments.

Teaching newcomers takes committment, time, and resources
 * We also need to support and cherish mentors and their work if we want to become a truly inclusive movement.

More information and further reading

 * Extensive documentation for Hackathons
 * Participant feedback
 * Wikimedia Blog: What we learned by making both newcomers and experienced participants feel connected and engaged at the Vienna Hackathon
 * Wikimedia Blog: How Technical Collaboration is bringing new developers into the Wikimedia movement
 * Wikimedia Blog: How two Wikimedians spent their time at the Montreal Hackathon