Hackathons/Handbook/Team

How big should your team be?
Some of the following roles can be held by the same person, but usually a team of at least three local people and two people from the WMF team is needed.

Having a good team with different roles and responsibilities is crucial to organize any kind of event. Make sure you have a diverse team with different skills.

Roles in the organizer team
As an example, the Wikimedia Hackathon 2017 in Vienna with around 270 participants was organized by a team of four people working full time in the months leading up to the event, plus a team of three people from the WMF and more dedicated volunteers during the event.
 * Project lead from hosting chapter/organization
 * Project lead from WMF
 * Logistics (venue/accommodation)
 * Finances
 * Scholarships (Co-owned by WMF and local group)
 * Registration management
 * Visa support
 * Travel support
 * Communications
 * Outreach/fundraising/engage local communities

Organizer Team
One person should ultimately be in charge of the success of the event and delegate tasks. Otherwise, many of these roles can be split between people or one person can take multiple roles.

Project lead

 * Budget management
 * works with Comptroller who handles accounting (office)


 * Provide timeline and make sure it is respected
 * Tracks progress of all groups


 * Human resources management (define and enforce roles, who does what, who does not do what)


 * Final cut

Volunteer coordinator

 * Plan for staffing needs; support for each other group


 * Identifie & screen staff & related timelines


 * Fill in any gaps

Program manager

 * Head the program committee


 * Program timetable


 * Coordinate with communications on releases


 * Coordinate with Tech & Logistics on room/hall needs

Social liaison
This is a fun task to be split among the team.
 * Plan the social events
 * How can we make this event more fun, silly, memorable?
 * How can we help the different types of people at this event succeed?

Technical coordinator

 * Define tech team needs with Logistics & Program coordinators
 * Makes sure that the Wifi works
 * A/V - streaming

Communications manager

 * Community announcements


 * Website delegations & updates


 * Write press releases and put together press materials


 * Deals with press inquiries and assignments

Sponsors manager

 * Put together sponsoring materials and find sponsors


 * Ensure communication with sponsors


 * Follow up during and after the event

Participant manager

 * Manage registration
 * Manage questions/issues/problems, off and on-site.
 * Vise letters and support

Scholarships coordinator

 * Work with scholarship committee
 * Manage attendees scholarships


 * Work with applicants to manage expectations & schedules

Emergency response team/coordinator
Handle reports of harassment and safety issues (Code of Conduct and Friendly space policy). See the Keeping events safe resource kit, and Training modules/Keeping events safe for details.

Venue logistics coordinator

 * Catering: Food, drinks and snacks


 * Accommodation, assigning rooms to participants



Event Team/Volunteers
Each event will probably have a team of volunteers helping participants find what they need.
 * Have a meeting in advance with all event volunteers
 * Daily meet-up (what went wrong what could be better)
 * Facebook or Telegram group for volunteers to communicate issues easily
 * Find a special way to thank volunteers
 * Make the volunteers easily identifiable via custom colored name badges, lanyards, or t-shirts (however this option creates daily laundry problems)

When Partnering with the WMF Engineering Community Team
This is specific information for groups who want to host and plan either the Wikimedia Hackathon or the Wikimania Hackathon in partnership with WMF Lessons from WMFR Organizer:
 * We generally use Phabricator as a task tracking tool, if you are unfamiliar with this tool we can provide training.
 * Planning in English. English is generally the official language of these events as they are international engineering events. We also generally hold our pre-event planning meetings and all spreadsheets, registration information and notes in English. There should be no problem to include track for local engineers in the local language if different than English.
 * Translation tools allow email communication between organizers speaking different languages - so the entire local organizing team does not need to be fluent.
 * Many attendee emails will come in and be answered in the local language.
 * Using google docs or EventBrite for participant tracking and registration. We are open to other options as well, however have run into problems using harder-to-use and collaborate on non-proprietary software.
 * The WMF Developer Relations Team is here to back you up whenever you run into a problem or need help, please don't hesitate to ask. It is likely that we have faced that issue before and have ideas for a solution.
 * The Developer Relations Team will work with you to manage hotel and hostel reservations for WMF staff attending the event. It is part of our travel policy that WMF staff are not required to share rooms although many of them are willing to do so. Because of this we need access to single rooms. Usually the easiest way to manage rooms for WMF staff is to reserve a block of rooms (both singles, and shared) and your contact at WMF can fill in the names of traveling WMF developers. Often we need to add a few last minute travelers (new hires, etc.), so if possible holding a some empty rooms for that would be helpful as well.
 * Generally the WMF Developer Relations Team drives the schedule, content and agenda of the event while the hosting group drives the logistics. The local team is welcome to organize a track for issues of interest local developers in the local language.
 * Registration: The local organizing team and WMF should agree on the content of the registration form. In the past we have used google forms or eventbrite successfully for registration. We have past registration forms available to copy/reuse but there will likely be a few changes each year. We open registration for this event on the wikitech-l mailing list, but can forward it anywhere else as needed. There should be a predetermined opening date for registration, a deadline for scholarships (published) and a closing date for registration. The local team and the WMF team may want to hold a few extra spots to add any last minute participants that they want to add to the the event.
 * Scholarships: WMF, the local organizing team, other Wikimedia Chapters and anyone you can convince will pool funds for scholarships. Everyone who contributed funds will have the opportunity to vote for or against scholarship recipients. The local team does flight, accommodating and visa support for scholarship recipients. It is possible for the organizing team to allow scholarship recipients to book their own travel and reimburse them after the event. There should be a plan in place for transferring money internationally for these reimbursements and the should should be completed as soon as possible after the event.
 * The roles and responsibilities of WMF vrs. the local team are flexible. We can come up with a plan that works well for everybody when we begin working together.
 * Biweekly hangout meetings starting 3-4 months with WMF before the conference (always in the evening at 6 pm CET)
 * Weekly hangouts during ramp-up to the conference (about 1 month prior)
 * Mainly contact with Rachel
 * Use phabricator as project planning tool