Wikimedia Developer Summit/2016

The Wikimedia Developer Summit is an invitation-only event with an emphasis on the evolution of the MediaWiki architecture and the Wikimedia Engineering goals for 2016. This summit is a combination of three events organized in San Francisco in the past: the 2014 Architecture Summit, the yearly Wikimedia Foundation Engineering All-Hands/Tech Days event, and the San Francisco Hackathon.


 * Date
 * Monday, January 4 – Wednesday, January 6, 2016

San Francisco, California, USA]
 * Locations
 * Mission Bay Center
 * [http://www.openstreetmap.org/node/2342299368 1675 Owens Street


 * and


 * Wikimedia Foundation
 * 149 New Montgomery Street
 * San Francisco, California 94105

The Wikimedia Developer Summit will be taking place the week of the Wikimedia Foundation's all-hands event. Participants of this event agree to follow the friendly space policy.

More details to follow.

Registration
"Work in progress. We plan to open registration on 14 Sep 2015."

Travel sponsorship
We have a modest travel budget that we want to use to bring key participants to the Summit. The registration form includes an option to request travel sponsorship. Candidates for travel sponsorship must be active contributors in ongoing Summit proposals (see Call for participation).

We plan to communicate travel sponsorship decisions to all candidates by 2 Oct 2015. We will keep the possibility to request travel sponsorship as long as we have budget available, evaluating new candidates as they come.

Call for participation

 * Work in progress.

The Wikimedia Developer Summit encourages proposals about updating our architecture, infrastructure and services to better support users and developers. Other topics interesting to Wikimedia developers are welcomed as well. The schedule of the first two days is build with sessions that have gone through this call for participation. The third day is reserved for unscheduled activities such as hacking, ad-hoc discussions, or networking.

The program focuses on organized discussions that start online and aim to reach to agreements during the event. Good examples of proposals include requests for comment, overlapping implementations, need-consensus topics, undefined areas and, in general, complex discussions that have chances to be resolved face to face in the context of the Summit.

Presentations and tutorials are explicitly discouraged during the Summit. These types of sessions are welcomed as Tech Talks or Lightning Talks organized before the event, especially when they can provide background materials to Summit participants.

Selection process
The goal of the Summit is to build consensus on important discussions. The process for selecting proposals aims to bring the strong proposals to the schedule and to filter out the rest, in order to focus better on them. Filling the schedule is not a goal.

This is how the life cycle of a successful proposal looks like:
 * 1) All proposals must have a task in Phabricator. You can reuse and update an existing task, or you can create a new one.
 * 2) Proposals must have an owner, a clear title, and a description kept up to date. They must be associated with the #wikimedia-developer-summit-2016 project as well as other projects related with the topic of the proposal.
 * 3) A discussion joined by the relevant stakeholders must take place at the task or in another designated URL.
 * 4) By 2 Oct 2015 all Summit proposals must have been created. Proposals created later can be handled in other venues or purely online.
 * 5) By 6 Nov 2015 all Summit proposals must have active discussions and a Summit plan documented in the description. Proposals not reaching this critical mass can continue at their own path out of the Summit.
 * 6) By 4 Dec 2015 all the accepted proposals will be published in the program. Strong candidates might be scheduled before.
 * 7) During December changes can be made to the schedule in order to avoid overlaps as much as possible. Contributors to each proposal are focusing on planning details, identifying the open questions that need answers, confirmed participants, structure of the session, and expected outcome.
 * 8) On 4-6 Jan 2015 each session runs as planned or better, arrangements for online participation are made by the session owners when needed, notes are taken and posted in the description of the corresponding task, a summary of the outcomes is highlighted, specifying the agreements made, and whether the objective of the session has been accomplished. Action points and next steps are documented as well.

Previous summits

 * Architecture Summit 2014
 * MediaWiki Developer Summit 2015