Wikimedia Hackathon 2015/Lessons Learned

This page is a combination of feedback from a survey sent to participants and ideas from the organizers.

This page will focus heavily on improvements for next time and things that went poorly. However remember that 97.5% of the people that responded to the feedback survey stated that their overall experience with the hackathon was either "Positive" or "Very Positive."

Suggested changes for the next Wikimedia Hackathon

(Main suggestions for next time, more coming soon) The best!: The worst!:
 * We will continue to use the buddy system during hackathons, they will be optional not mandatory. We will add buddy system participation questions to registration.
 * There will be an opt-in during registration for name, interests and contact information to be put on a wiki so participants can talk in advance of hackathon and self organize.
 * The opening session of the hackathon will have time for project pitches and allow people to find others working on the same thing
 * We will do our best to have better wifi at the next hackathon
 * We will have better food options for vegetarians at the next hackathon
 * Meeting new people, spending time working with people they know, and discussing new ideas
 * The location, the city, the venue/venue atmosphere, the outdoor area
 * Social events (especially the retro-gaming)
 * Wifi quality
 * Vegetarian food options
 * Presentations in French without ::3a:f5:1b:da/find format all settings Chromebook wifi

Background on Feedback Survey

 * rfarrand & acella created the feedback survey using google forms (we will move to qualtrics for future events)
 * The Feedback Survey was sent out to participants on June 4th, 2015
 * The Feedback Survey closed on August 12th, 2015
 * The survey received 81/200 responses (40.5% response rate)

Considerations for Next Year
This section is based on the fill-in-the-blank/comment sections of the feedback form. Some of these comments will be contradictory. We are mostly trying to include common themes and issues that were felt by groups of people. This section is a bit more subjective than the  section below and suggestions may be paraphrased and combined with each other.

(improvements to this section coming soon)

Information from Newcomers, how could we have supported them better?

 * More sessions with information on how to actually get started instead of just an overview of what is possible would be appreciated
 * Intro sessions for each of the main areas of work would have been appreciated, or some easy way for a newcomer to understand all of their options.
 * Request for documentation about what to expect if attending a hackathon for the first time. (This has already been mostly completed since the hackathon here)
 * The buddy system was helpful, WMF staff could have been more productive in reaching out to new volunteers instead of the reverse
 * People were available and receptive to helping newcomers, but sometimes it was hard to figure out who to ask for help

Opening

 * More focus needed, too much logistic info
 * Use this time to introduce projects, pitch ideas and help people find inspiration. Projects can “call for voluneers”
 * English only in mandatory sessions, the majority of the audience only spoke english. The long french speeches with no context were unsettling.  The translations were not helpful.

Demoable Project Showcase/Closing

 * Messy, should have set clearer expectations for presenters
 * Please enforce time limit
 * The demo session was too long, make it shorter or separate by subject area.
 * Cool to see what others are working on
 * Liked the focus on demoable projects
 * Do this in the main room so that people can keep working during if they want and if it takes a long time people wont mind.
 * If it is going to be difficult to connect laptops to the projector, people should be encouraged to pre-record their demo and play it during the closing or there should be a rule of publicly hosted demos only. Don’t make exceptions.

Q&A with Lila

 * Would have been better to have her around the hackathon interacting with people more informally instead of doing the Q&A
 * Instead, Lila participate in the actual hack sessions/discussions to get a better understanding of what we developers are doing
 * Q&A’s with Lila are not good for hackathon, better for Wikimania
 * Too many questions from WMF staff, not enough from volunteers. If WMF are asking that many questions than they should be given other opportunities to ask things.

Common themes:

 * Last minute “haphazard” pairing does not work, it should be done in advance or more mindfully. Don’t call people onto stange and awkwardly make poor pairings.
 * Buddy system is great, nice to work with new people, helpful
 * Make it optional, felt forced, specifically WMF staff did not like to be forced into it
 * Unclear Expectations, define goals more clearly.

Other ideas and themes:

 * Would be nice if experienced participants would reach out more proactively
 * Share a room with your buddy (optional)
 * Pair people up with projects instead of people, that way you can meet multiple new people in a structured way
 * Create an easy and positive way to hand off buddies if the fit does not work out, also provide documentation on best practices for mentorship and what to do in situations where things are not going right.
 * Add buddy system to registration form, and publicize information to  help people pair themselves by publicly providing more information about intended work at hackathon
 * Buddies might distract mentors for getting their work done or collaborating with other people
 * Newbie focused social events so they can meet each other too
 * Birds of a Feather (BoF) board instead of buddy system

Technical:

 * The internet connectivity and speed was terrible on the first day, it got better but was still not perfect by the end. We need better wifi, this is the most important thing to consider.
 * Don’t take the wifi down at 6pm on the last day. It should stay up all night and into the next morning.
 * It was OK that there was no wifi access in people’s rooms, it encouraged people to be social and collaborative.
 * Add more power strips, especially outside

Social Events:

 * The Retro-gaming was great, people liked it the most
 * BBQ was great (except for vegetarians), outside with good weather, good food, good wine,
 * It would have been nice to have at least one offsite/historical social event

Food:

 * Better food for vegetarians/kosher, have protein and warm food. After wifi this was the biggest complaint of the event.
 * Next time label all of the food so people know what they are eating, it also makes it easier for vegetarians
 * Dinner was never on time (1 hour late) and food was brought in stages which made people miss out on all the options
 * More snacks should be available
 * More soda should be available
 * The food was often the same, sometimes they re-served things for dinner that they had already served at lunch.
 * It would be nice to have food available for longer periods of time so people don't have to rush and wait in a long line or miss out
 * Food was good, coffee availability was good

Location:

 * Some people liked that the venue was far away from downtown. It forced people to stick together and stay around the same location which lead to more interaction. Liked that the venue was in nature and not in a busy place.
 * Other people wished the venue had been closer to the city, it hard to get downtown.

Transportation:

 * The transportation strikes made transportation more difficult for everyone
 * Getting from the airport to the venue was difficult and took too long, it was also too expensive (up to 100 EUR)
 * Location should be close to lots of public transportation options
 * Don’t use Uber again as an official transportation option, not everybody has it, not everybody wants to use it and not everybody can use it.  

Rooms:

 * There was only one key per room, but people had to share rooms
 * Towels should be cleaned every day

Name tags:

 * Name tags should have had bigger writing
 * Name tags should have been double sided. Not having this was very upsetting to people.

People's opinions of their own biggest accomplishments during the hackathon:

 * Unfortunately nothing very newsworthy, mainly lots of smaller things. Was happy to meet many new people and hear about their experience on translation issues.
 * fixed one of my oldest gadgets that is used more than 8'000 times on several wikis, including enwiki and dewiki
 * Running 2 MediaWiki-Vagrant install parties and helping an additional large number of people via irc and face to face troubleshooting.
 * Introducing many people.
 * Meeting with the other 3rd party users and getting some organisation around our efforts.
 * https://phabricator.wikimedia.org/T100161
 * Accessibility settings gadget.
 * * Natural language parsing to generate SPARQL queries
 * Meeting people and discussing everyone's projects!
 * We deployed revscoring for frwiki in time to demo it at the showcase.
 * We put together an actionable plan to better represent the MediaWiki community and further a strong relationship with the WMF and related projects. We're going to present our findings at Wikimania.
 * Releasing next pywikibot version Creating a usable documentation system for pywikibot
 * Talks with various people and learnt things about MediaWiki internals
 * Having https://github.com/Commonists/SurfaceImageContentGap already working and production reports :)
 * Adding coordinates to ~2000 listed buildings on the Dutch Wikipedia
 * More than 10 Visual Editor bug reports filled.
 * Turning some co-workers into friends, probably.
 * Wikipedia web application (no phabricator task) http://chimeces.com/webkipedia/
 * Presenting the final product at the demo.
 * meeting new people :)
 * MediaWiki 1.25 general release
 * Working mockups, as a complete newcomer to Java and Android, that was a big accomplishment.
 * The Wikipedia for Apple Watch app!
 * Mentoring my buddy (which is what most of my effort went into). In hindsight that was probably not an optimal use of time though.
 * Joining the web of trust
 * Disentangling a nasty part of code that needed to be fixed for a long time.
 * I'm not a frontend developer, so I was pretty proud of the extensiondistributor UI updates.
 * meeting researchers getting oversight about actual problems and projects
 * Minimum Viable Product for Newsletter extension agreed with GSoC mentor, student, and stakeholders present at the event.
 * I helped a newby get started w media wiki. Also connected him w Android folks for getting his Wikipedia app Android dev environment set up.
 * Finally having documentation online
 * I could finalize on how the Newsletter extension I am mentoring should take form. I could interact with various stake holders of the extension, got to know various test cases - and understood how misleading our initial idea on the same was. Apart from that - meeting other devs, exploring part of the Lyon city - and many more ;)
 * Simply getting a new app written in Swift that actually sort of worked!
 * write sql to fetch names in all available languages from OSM
 * MediaWiki Stakeholders now have an action plan and a lot of motivation. See results in Mexico

Projects that people saw that impressed them the most:

 * The services team stuff was really impressive!
 * 1.25 release :)
 * Wikidata: natural language to SPARQL translator
 * SPARQL queries for Wikidata
 * The mobile UI that used Elastic Search's "morelike" to enable rabbit hole digging.
 * The Mutt-style C CLI interface to Flow was awesome. And from a total group of newcomers too!
 * Revision scoring
 * Actually useful - Various things including minimal web interface for Wikipedia. Cool factor - C Flow UI
 * pywikibot - COI of course ;) Wikidata Mobile
 * Apple Watch
 * Video.js
 * Many many nice projects at the closing session. I probably liked the natural text to SPARQL, videojs and the Apple watch thing most
 * Wikisource export.
 * Webkipedia
 * Loved the hover-over revision history.
 * Graph extension
 * Implement gl-vector in-browser rendering
 * Apple watch!
 * Possibly that pywikibot converted to json i18n.
 * Apple Watch project Maps for Wikipedia
 * Forrestbot is very very helpful
 * The blame tooltip project The presentation by librarians without borders was very moving imo.
 * Ok, that Apple Watch thing was neat, but these three were the best. https://github.com/geekuillaume/wiki-hoaxbuster https://phabricator.wikimedia.org/p/Forrestbot/feed/ https://doc.wikimedia.org/pywikibot/
 * Everything done by the French students.
 * the Graph extension and MW at NASA
 * There were too many to say.
 * Sorting out our train deployment workflow and having a rough consensus about what we want to achieve.
 * Wikipedia on a smart watch
 * Haiku generator
 * The userscript for revision "blame" functionality was probably the coolest thing I saw.
 * Of the projects that was showcased - I liked the Video JS player and the Mediawiki on Apple watch. Everything in https://phabricator.wikimedia.org/T96378 looks equally great though!
 * The natural language SPARQL query system
 * * Wikidata SPARQL endpoint
 * sparql support in askplathypus
 * There were a lot of cool projects, I think the apps ones were all great, and Joaquin's mobile app is a really cool demonstration of where Wikipedia's web UI/UX could go.
 * https://phabricator.wikimedia.org/T100106 (The coolest demo was by far the natural language based wikidata query interface, but I'll hold back judgement until I see that actually performing well in real-world usage :)
 * Created at hackathon: https://phabricator.wikimedia.org/T100315 Created earlier: The extensions created/presented by the NASA guys, especially https://www.mediawiki.org/wiki/Extension:WatchAnalytics

Data
(planning to reformat this section, but if you are reading it now the data is formatted as: Answer, # of people responding with that answer, % of responses that answer got out of everyone who answered that question)

Supporting Newbies
(Only people who were attending a Wikimedia Hackathon for the first time were directed to answer this question)