The two big Wikimedia hackathons of 2015 had impressive showcases (achievement unlocked!) but then there was an unclear path between those hackathon projects and anything deployed in production.
We need to evaluate what happened and discuss how can we improve in 2016. The outcome of this task could be a blog post with useful data and a first attempt of drawing conclusions and recommendations.
See also:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | Qgil | T125545 Phabricator Q&A session for Community Liaisons | |||
| Resolved | Qgil | T116025 Goal: Align Community Liaison and Developer Relations project management practices | |||
| Resolved | Qgil | T119387 Community Liaison and Developer Relation quarterly goals for January - March 2016 | |||
| Resolved | Chen_WMIL | T120828 Open registration for Wikimedia Hackathon 2016 | |||
| Resolved | Qgil | T119703 Goal: Connect the priorities of the Community Wishlist and other tech priorities with the Wikimedia Hackathon 2016 | |||
| Duplicate | Aklapper | T119862 Improve momentum of Hackathon projects | |||
| Declined | Qgil | T117563 Recommendations for hackathon projects in 2016 events based on the lessons learned in 2015 |
I don't know whether to close this task as Declined or Accepted. I didn't do all I wanted to do, but the fact is that I had recommendations for the next hackathons, and this is why we agreed to T119703: Goal: Connect the priorities of the Community Wishlist and other tech priorities with the Wikimedia Hackathon 2016.
I'm not sure a blog post would be useful at this point, and I'm very busy to write it. Maybe a blog post comparing results of the hackathon this year and last year, around mid April?
Declining.