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 betting on promoting tasks identified by our communities as possible hackathon projects.
Let's incubate the idea here. The list of proposals will move to the event's wiki page right before T120828: Open registration for Wikimedia Hackathon 2016.
Criteria for projects
- Scope is defined enough to be possible in a couple 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.
#21: T120462: Reduce edit conflicts by treating different parts of the page as separate A very open-ended, vague proposal, but there's a small chunk that would be perfect: "Treat the addition of a template at the top of an article or a category at the end as not conflicting with the alteration of the contents in between." There's also possible room for creative devs to figure other small-scale, non-controversial improvements along those lines. Improvements here likely will also benefit T121469: Improve diff compare screen.
#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.
In addition, the organizers (Wikimedia Israel) would like to create a specific working group for developing existing/new mobile apps based on MediaWiki APIs, specifically looking at T88746: Upload photos on Wikipedia mobile app's edit screen - commons mobile app, or developing another community needed mobile app.
Additional projects recommended by WMDE-TechWish
- T70060: Couple page link notification to watchlist
- T987: [Story] Phase 0: Automate interwiki language links for Wiktionary
Additional projects recommended by Wikidata team
- T103091: [Task] research how to surface usage tracking data for editors
- T59843: [Story] Improve the listing and classification of properties
- T76229: [Story] create demo infoboxes
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).