Page MenuHomePhabricator

Organizer Lessons Learned from Mexico City Hackathon: Ideas for next year
Closed, ResolvedPublic


We can keep an ongoing list of things to do differently here. I have already started to think of some!

Event Timeline

Rfarrand claimed this task.
Rfarrand raised the priority of this task from to Medium.
Rfarrand updated the task description. (Show Details)
Rfarrand added subscribers: Rfarrand, siebrand.
  • Lightning talk sessions, scheduled in advance @brion 's idea. I think it would be great.
  • Have somewhere public on the schedule where people can list the projects they are currently working on and want help with and where they are located (table number).
  • Number tables so people can find each other more easily
  • In WMF staff event registration, ask which sessions they would be willing to run in advance. This year we had a question about demoable projects and another question about other "optional activities" but no specific "sessions to run at hackathon" section. Having this would be helping to event organizers getting the schedule up earlier instead of having people wait until the last moment.
  • More focus on local language tracks

Better way to make public mid event announcements. On a projector or a page?

  • A new developer mentioned that it would be great if the newbie-related sessions would be scheduled as far ahead as possible, so people can plan specifically for them even if they don't know (or are not used to) our methods of updating the wiki pages.
  • Related: Install-parties for Vagrant are awesome, we should have those in every hackathon, and make sure new developers know what they need to prepare for them (if anything) in advance.
  • Power on top of the tables, not underneath.

I plan to include these with the results from the Wikimania Hackathon feedback survey

Rfarrand raised the priority of this task from Medium to High.Sep 1 2015, 10:31 PM

Have started by creating this page:

Will add these lessons to make sure they are not lost.

This is done! :) closing.