User:Qgil-WMF/Sandbox

Good practices

 * Common understanding
 * We are a community with a foundation, not a foundation with a community.
 * All documentation in mediawiki.org - including value proposition and user documentation.
 * Easier to maintain, promote and watch.
 * OSS development context clear. Links to/from Bugzilla etc are natural.
 * Simplified, adapted intros can be created in Wikimedia projects when deployment comes.
 * Calls for feedback point to a central point in mediawiki.org.
 * Criticism happens next to the core docs and it's easier to integrate.
 * Less risk of Wikipedia-centrism. Neutral field for all Wikimedia projects and 3rd parties.
 * Less risk of duplicated discussions in different places.

Document how the organization of content and schedule works in Wikimedia hackathons

 * To be inserted in Hackathons. Please post your feedback at T130592.

Planning and scheduling content before the hackathon
While hackathons and planning might seem almost incompatible, there are some plans that will help bringing interesting people with interesting skills to the event. Travel sponsorships and local developer outreach will be more effective with a public hackathon plan in place. This plan will also help increasing the number of newcomers and diversity in general.

The ingredients of the plan: (((The content below still needs to be processed)))
 * Community Wishlist tasks. The Technical Collaboration team selects 3 - 5 Community Wishlist tasks with lead developers confirmed, and help recruiting volunteers and organizing the work prior to the event.
 * Development tracks. The Technical Collaboration team reaches out to the Wikimedia tech community in order to identify groups that have a specific goal for the hackathon, from WMF teams to consolidated projects with capacity of mobilization.
 * Local projects. The local organizers have an option to select hackathon goals in line with the priorities of the chapter and their community, and the Technical Collaboration team will help finding lead developers and volunteers.
 * Activities for newcomers. A track of introductory sessions will be pre-scheduled with all the details and links to resources, allowing newcomers to prepare in advance. A collection of microtasks (from the Google Code-in pool or similar kinds) will be published in advance, with identified mentors.

Reach out to Community Wishlist recommendations Tasks for newcomers Schedule
 * local Wikimedia developers
 * local tech ambassadors / technical translators
 * local projects using Wikimedia tech or MediaWiki
 * local developer groups
 * 1) WMF Community Tech team to make a pre-selection of tasks suitable for the hackathon
 * 2) Create task in Phabricator to decide the CW tasks to focus
 * 3) Send an email to Hackathon registered participants asking them to express their interest in tasks (using Phabricator's Slowvote?)
 * 4) Select a very short list of tasks with owners and/or volunteers having expressed interest.
 * 5) Promote these tasks before the Hackathon and help the volunteers getting organized.
 * Publish empty schedule
 * Schedule sessions of track for newcomers providing as much detail as possible, links to prepare the session, etc.
 * Also information about speakers and facilitators, including pictures.
 * Try Phabricator Calendar to allow people to RSVP / subscribe?