Page MenuHomePhabricator

Wishlist tasks suggested for the Wikimania Hackathon 2016
Closed, ResolvedPublic


Recommendations for the Wikimania Hackathon 2016. -- The hackathons in 2015 had great showcases of prototypes but a low impact on actual improvements for our editors and readers. In order to improve this situation, we are promoting tasks identified by our communities, as possible hackathon projects.

Criteria for projects

  • Scope is defined enough to be possible in a couple of hacking days, or there's a small-scope piece of the proposal that could be broken off from the larger idea.
  • Non-controversial, won't need further community discussion before you get started
  • Minimal design needs

Projects recommended by Community-Tech (WIP)

The priority order is based on the number of support votes the proposal got at the Technical Wishlist Survey. The full table is here, with links to the proposals:

#15: T120733: Improve date range searches on Special:Contributions Well scoped, clearly defined, minimal design.

#25: T120788: Tool to use Google OCRs in Indic language Wikisource

#27: T109561: Add non-exact title search to Special:Undelete and corresponding API Well-defined, would be very useful for admins. This task would provide a means of searching for deleted pages.

#43: T22307: Generate automatic summary /* blah */ when I manually add a section heading when editing Well-defined, not controversial, could be very helpful.

Projects recommended by WMDE-TechWish (WIP)

#34: T73808: Support tables in PDF rendering (tracking) - Since the whole story is too big for a hackathon, we have scaled it down to 3 sub tasks
Subtasks suitable for the hackathon:

Additional projects recommended by Wikidata team

Additional tasks that Hackathon attendees are interested in, or planning to work on

Start or continue the discussions, now!

Want to work on something else?

Tag your task with Wikimania-Hackathon-2016 and find someone to work with!


The Community-Tech team is organizing a Community Wishlist Survey that will result in a prioritized backlog of tasks. That team will work on some of the tasks but not all. What about using the developer energy around the Wikimedia-Hackathon-2016 to get more tasks of that list resolved?

The idea can be extrapolated to other wishlists in Wikimedia, like German Wikipedia's Technische Wünsche 2015, Wikisource's technical needs, even Possible-Tech-Projects...

We could match identified tasks with Wikimedia developers willing to work on them with local developer groups willing to participate in the hackathon (T119694).

See Also:

Related Objects

Event Timeline

Bmueller updated the task description. (Show Details)
Qgil added a subscriber: Qgil.

This task is in a sprint, and needs someone assigned to it. Assuming @Quiddity, feel free to change if this is not correct.

Qgil triaged this task as Medium priority.May 31 2016, 7:42 AM

Assuming Normal priority. Please fine tune if you disagree.