User:Sonkiki/Handbook Project

This is my working page for a 3-week project as a contractor for WMF, with the goal of creating a hackathon/ event handbook.

Create a better navigation
For each chapter in the handbook, show a menu like in Help:Flow for all the other chapters,so that you can nagivate to the other chapters easily. The Template is called "TNT|Flow Navigation". Who could create something like this?

Illustrate handbook with pictures

 * stock fotos from 100 words project: m:Grants:Evaluation/100_Words_Campaign
 * "stock" Fotos from Klaudia, wmhack Vienna 17: https://commons.wikimedia.org/wiki/Special:ListFiles?limit=150&user=WWWeb.pics&ilshowall=1
 * stock fotos from other previous hackathons: c:Category:Wikimedia_hackathons_by_year

Potential future hosts: Think about hosting, still unsure if they should do it
chapters and people thinking about organising an event. they want to inform themselves about how this could even be done. they probably have already a little bit of experience with hosting a smaller event, and maybe they know someone in the WMF team, but they are unsure what would be coming their way if they applied for a hackathon.

e.g.: a local community expresses interest in being hosts for a hackathon. the executive director of that chapter thinks: could this be even possible? what would be coming our way? let's check; she visits this page to gather info.

They need

 * an overview of what's coming for them
 * comparisons to how others did it
 * a list of minimum requirements/ list to check themselves against ("you can hold an event if...")

Current Hosts: have won bid, will do event
chapters who have just applied for a bid, or have won the bid.

they may be up to 18 months away from their event.

They need

 * a resource to check wether they are still on track
 * a recipe
 * templates

Event participants / Interested readers
people who just want to read up on documentation. They may be organizers from other events (outside of the Wikimedia world) and/ or participants of hackathons/ events who are interested in getting meta-information about the event they'll be attending.

They need

 * a link to direct them to https://www.mediawiki.org/wiki/Hackathons/FAQ
 * we do not need a special section for them.

Conceptual work: Structure for new Hackathon Page
this is my proposed structure for a new /Hackathon page.

I will include the handbook for organizers, but also improve the structure for participants.



Etherpads / Meeting Notes / Phabricator Task
Etherpads: Rachel Meeting Notes: https://etherpad.wikimedia.org/p/TC_Doc_Project

Phabricator task for this project: https://phabricator.wikimedia.org/T168458

Now an archive: Collection of first thoughts/ ressources here: https://etherpad.wikimedia.org/p/Sonja

Journal
disclaimer: this journal may not be complete

Week 1
Mon, 12 June: First day, trying to get into it, clicking my way through various wiki pages, made a timeline, currently collecting everything here: https://etherpad.wikimedia.org/p/Sonja. Kick-off call with Rachel Farrand in the evening.

Tue, 13 June: encountering some issues with creating wiki pages, troubleshooting by Raimund Liebert (WMAT). Found out that Jean-Frédéric has started a handbook in 2014: User:Jean-Frédéric/Hackathon handbook and that Wenke from WMDE is working on an event guidebook in German as well.

Wed 14 June: got a lot of good suggestions for what it should look like, and what not, from WMF, Quim Gil, as well as community engagement team (Sherry Synyder, Chris Koerner, Nick Wilson, Benoit Evellin, ...).

Tips I got / what everyone wants: Thu 15 June: trying to incorporate everyone's suggestions into a structure. Will have to prioritize today, because it's a lot :). defined target audiences. testing to work with timeline templates. sorting through content-resources for handbook and giving them a score according to relevance.
 * + include glossary
 * + timeline with very specific instructions (e.g. NO:  "Think about branding", YES: "Four weeks before wedding:  Tell future mother-in-law how chic she will look in solid black mourning clothes." OR "Six months before hackathon: Assign one person to be in charge of encouraging participation by different kinds of people")
 * + clear page with comprehensive view. good examples: Help:Flow, https://www.ted.com/participate/organize-a-local-tedx-event, WordCamp Organizer https://make.wordpress.org/community/handbook/wordcamp-organizer/
 * + modular structure (example of Asian restaurant menus to build-your-own meal)
 * + keep it KISS (avoid hard to collaborate on formatting like on Help:VisualEditor/User guide)

Fri 16 June: wrote project description for phabricator task. felt a little under the weather after getting a flu shot in the morning, so had a slower day. Sat 17 June: Rachel and I consulted Nick for the final location of the handbook and merging questions. Here's the outcome:

we will: 1. publish the handbook on https://www.mediawiki.org/wiki/Hackathons/Hackathon_tips_for_organizers because this page is already well linked and has many views, i.e. people use it already. 2. add a top banner to it, telling people about the talk page, how it works, and to use it if they have questions for Wikimedia Foundation technical event organizers. 3. follow Merging etiquette (as Nick described it to us): I plan to not merge pages, but use content for the handbook and remix it. of course I want to credit the original source. Asked Nick on his expertise of how to handle that, giving specific examples. (User:Sonkiki/Handbook)
 * Mediawiki: = be bold. But leave either link-pointers (if just extracting part of the page) or redirects (if merging the entire page).
 * Meta: Consult Nick for specific examples. General rule; merging pages *within metawiki* is okay, but do not move pages over to mediawiki.
 * Outreach wiki: do neither merge nor move. just add links to them.

Yippie! I have a draft for a structure: User:Sonkiki/Handbook/Structure

Week 2
Mon, 19 June: Worked on my draft for a brand new Hackathons page including numerous sub-pages. At WMAT office, showing my work to the team (Annemarie and Raimund).

Tuesday, 20 June: creating all the sub-pages and filling them with copy+paste content (sorting the correct content to the correct pages). Meeting with Rachel in the evening, collected feedback on my structure. (positive :))

Wed, 21 June: Hump day - now officially in the second half of the project. Shifted my focus from creating structure to managing content.

Thu, 22 + Fri, 23 June: Worked on improving content and working out a plan for what to move where when we actually publish the new documentation.

Week 3
Mon 26 June: Added content, improved chapters of handbook. Took half day off.

Tue 27 June: Added content, improved chapters of handbook, prepared meeting notes next meeting with Rachel (Thursday) in the Etherpad as usual: https://etherpad.wikimedia.org/p/TC_Doc_Project and edited some meta info in this project / organizational tasks in the structure.

Wed 28: More content. Took half-day off.

Thu 29 June: Moved a few pages. In the evening, call with Nick. Learned about tools to check pages with prefixes and redirects and "what links here", and got media wiki structure questions answered. Call with Rachel after, final call in the project! Last tasks and how we proceed after project is finished, to spread the word and promote. (For all of this see etherpad).

Fri 30 June: Moved all the pages from my user sub-pages to actual wiki. Marathon day, but oh-so-satisfying!

Monday July 3: Additional day in project to compensate for two half-days off. Mayor work day: Created pages Timeline, Event week, Newcomers and Mentoring program. Fixed errors. Wrote phabricator description and wrap-up of project.

Inserted info boxes to spread word of new documentation on mediawiki and meta wiki on related pages: FINISHED ALL TO-DOs! Wohooo! It's a wrap, the project is finished. *celebrates*

Moving Plans: Moving, creating and edition pages on mediawiki
All pages transferred on Friday, 30 June 2017.

Best practice to cite sources
You only need to link the original location, in either the edit-summary or the talkpage. Whichever you prefer is fine.

Best practice for naming pages
* Caps: Sentence case for capitalization. (Just the first word capitalized)

* Wording: Both types are used, so whichever you prefer, and whichever is easiest to (potentially) translate

Checklist

 * create page


 * transfer content
 * add little notice box to the top (optional)
 * leave message on talk page


 * fix all links
 * place redirect on old user page

Text to use on talk page
Page created as part of a project to improve hackathon documentation

I created this page as part of a project to improve the documentation for hackathon organizers.

If you're interested in details, find the official project description on Phabricator: https://phabricator.wikimedia.org/T168458

or check out my working page/ construction site that I used to document my work for this project: User:Sonkiki/Handbook Project

Sources I used to create the content of this page:
 * content of the previous Hackathons/Hackathon tips for organizers page (as it was before June 30 2017)


 * content of the previous Hackathons/LessonsLearned page (as it was before June 30)
 * Wikimedia Hackathon 2017/Participants

I hope that the new structure created in this project not only proves to be helpful, but that it will be built upon, edited, improved and extended over time – like any good wiki page should be!
 * new content I created by myself, drawn from experiences of organizing previous hackathons, especially the Wikimedia Hackathon 2017 Vienna

Notice Text
This page needs a little help still. Please help update and improve its content. Thank you!

Text for edit summary
if page edited:

Content edited significantly as part of a project to improve hackathon documentation for organizers. Please see the talk page for more information on this project and sources I used to create this content.

if new page created:

Page created as part of a project to improve hackathon documentation for organizers. Please see the talk page for more information on this project and sources I used to create this content.

Content Resources: Existing pages with handbook-relevant content
main pages to draw from in this project:

>> This list was, in a reduced way that made sense, transferred to Hackathons/Handbook

Research on Hackathons:
Nothing there yet about hackathons, but the current reseach going on from Carnegie Mellon (contact Anna Filippova, via rachel Farrand) could be included here: Paper (PDF) on hackathon research: https://drive.google.com/file/d/0B0ba96_UwEK8N09zOFBTWEwtaU0/view workshop on hackathon organization: https://hackathon-workshop.github.io

plus also research going on atm from Cooperative State University Baden-Württemberg Germany to write an analysis of the current state of hackathons, contacts Alexander Finkbeiner, Sebastian Kezic und Ricco Schwarz who contacted hackathon Vienna mailingliste. The results of this survey are being collected in a IEEE whitepaper. they are currently not planning on publishing the results, but it is possible that they do so later on. Contact via Rachel Farrand, has put them in touch with Carnegie Mellon.

Testing to work with a graphic timeline template
https://en.wikipedia.org/wiki/User:Mrguyguy226/sandbox_graphical_timeline

Also:
 * https://en.wikipedia.org/wiki/Template:Graphical_timeline
 * https://www.mediawiki.org/wiki/Extension:EasyTimeline (generated the above example)
 * https://www.mediawiki.org/wiki/Extension:Graph/Demo#Timeline_.2F_lifeline (newer software, but even more complicated (imho))