Wikimedia Technical Conference/2018/FAQ

How is this conference different?
This year’s TechConf is different than Developer Summits in the past. It is squarely focused on a single topic - the Platform Evolution Program - and the conference itself is meant to be a venue for structured discussions that will aid in developing the long term planning for this program.

What is Platform Evolution and why is it important?
Our platform is used to fulfill our mission of enabling the dissemination of knowledge throughout the world. Not only the Wikimedia projects, but also a multitude of 3rd party projects depend on MediaWiki. But our technology platform has grown into a large and complex system over the past 15 years, with increasing maintenance costs and difficulties in building new features.

Many people both within and outside of the Wikimedia Foundation have tried to address these issues, but at the same time have been burdened with simply maintaining the technology and have had little time to make the changes needed to improve the system for all and better enable us to accomplish our mission.

To change this, the Wikimedia Foundation has developed and funded the Platform Evolution Program to provide space to have these discussions, make plans and actually build and implement solutions.

This program starts in July and for much of the first year will be focused discussing and planning these changes.

A key part of this is the Technical Conference as it provides a venue to bring representatives from the many stakeholder groups into the same place.

What will the specific topics be?
The content for the conference is just starting to be developed.

The Platform Evolution Program itself doesn’t officially kick off until July and the team doing the primary planning is forming at that time, so much of the content will be developed after that time. Expect more information on topics coming during the summer. Ideally we would know the specific topics before we start nominations, but because the conference is only a few months away (October) and so we need to give everyone time to book and plan their travel. However we do know the general topic and we do know we want to have people that can provide perspectives on how specific platform changes will affect their work, organizations and lives.

Why nominations?
Because of this, a large variety of people in different roles depend on our software - and not just engineers, but designers, content creators, moderators, product managers, data scientists, etc… the list goes on. In order to make decisions and fully address the issues and aspirations we have of our platform, we need a good cross section of people in the room. We need people who can create and architect solutions, as well as those who actually make decisions on funding for our projects.

However, we have only six people on the conference program committee, and while we know some people we should invite, we don’t know them all. This is why we are asking you all to make nominations for those who you feel will be able to contribute to this discussion from different perspectives.

How do I know who to nominate?
Good question! While we have given some general ideas above about who we would like to attend, it is helpful to provide some more concrete details… we are looking for diversity along many different dimensions to ensure we get the widest and best feedback and discussion.

These lists are not exhaustive. While we are doing our best to provide good examples… the entire point of using a nomination system is acknowledging that we have blind spots and don’t know everyone we should invite. Just because you don’t see an organization, skill, or role that you feel is important, doesn’t mean that you shouldn’t nominate them. It just means that we need you to tell us why they are important.

Diverse organizations and groups:

Diverse experience and skills:
 * WMF, WMDE, MediaWiki Stakeholders Group, TechCom, Wikia, Other Chapter organizations, Code Stewards, volunteer contributors, other 3rd party users, etc…

Diverse users:
 * Mediawiki, extension, Wikibase/Wikidata, Javascript, apps, services (SOA), operations, releasing/building, CI/testing, performance, machine learning, API design, UX/UI design, internationalization, product/program managers, engineering managers, researchers


 * Main page/featured article/portal maintainers, bot authors, moderators

How will you make selections?

 * An open form will be provided for individuals to nominate others (or themselves) by selecting which one(s) of the qualities (backgrounds, experience, and skills) we are looking for that they would be provide value (through surfacing problems, designing solutions, evaluating solutions, and approving budgets for implementing solutions). View the list of qualities
 * The Program Committee will strive to invite people who bring new perspectives where possible.
 * The Program Committee will make selections based on the nominations with input from relevant stakeholders (eg: community members or Wikimedia staff).
 * The list of nominations will be kept private to the Program Committee. We want people to nominate whoever they feel (including themselves) is best fit for the work but we also want to respect the privacy of those who are nominated (including those who are not selected or those who decline attendance for personal reasons).
 * This year’s event has a limited scope as well as a limited number of attendees. Those who are not selected are encouraged to apply next year and know that not attending this year will not have a negative impact on their future chances.
 * Note: The Program Committee already plans to invite the relevant budget owners thus there is no need to nominate them explicitly.

When will nominations start and when will invitations be sent?
Nominations will start in a few days and close on June 8th.

After that the Program Committee will review nominations and begin sending out invitations on a rolling basis. We hope to send all the invitations out before the end of July.

When nominees receive their invite, they will be given a registration form that they will need to fill out as soon as possible. Members of the Program Committee will follow up to help with travel and other logistic questions.