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

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?