Recommendations for the [[https://wikimania2016.wikimedia.org/wiki/Hackathon|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 [[ https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results | here ]], with links to the proposals:
#15: {T120733} Well scoped, clearly defined, minimal design.
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Moderation_and_admin_tools#Improve_date_range_searches_on_Special:Contributions
#25: {T120788}
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Wikisource#Tool_to_use_Google_OCRs_in_Indic_language_Wikisource
#27: {T109561} Well-defined, would be very useful for admins. This task would provide a means of searching for deleted pages.
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Search#Provide_a_means_of_searching_for_deleted_pages
#43: {T22307} Well-defined, not controversial, could be very helpful.
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Editing#Generate_automatic_summary_.2F.2A_blah_.2A.2F_when_I_manually_add_a_section_heading_when_editing
== Projects recommended by #TCB-Team (WIP) ==
#34: {T73808} - The TCB-Team is going to scale down Hackathon suitable sub tasks before June 10, if possible.
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Templates#Inserting_templates_.28tables.29_in_PDF_and_Books
== Additional projects recommended by #Wikidata team ==
* {T103091}
* {T59843}
* {T76229}
== Additional tasks that Hackathon attendees are interested in, or planning to work on ==
Start or continue the discussions, now!
* #11: {T3790}
* #17: {T120746}
* #98: {T120745}
* #14: {T2674}
* #68: {T88620}
* #23: {T48580}
* #36 {T97672}
* #6: {T120451}
* {T132574}
* {T131417}
* {T15303}
* {T131582}
* {T91201}
* {T135882}
* {T131714} (further work on the blocking tasks)
== Background ==
The #Community-Tech team is organizing a [[ https://www.mediawiki.org/wiki/Community_Tech_team/Community_Wishlist_Survey | 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 [[ https://de.wikipedia.org/wiki/Wikipedia:Umfragen/Technische_W%C3%BCnsche_2015 | German Wikipedia's Technische Wünsche 2015 ]], [[ https://etherpad.wikimedia.org/p/wscon2015needs | 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:**
* {T120092}