User:Elitre (WMF)/draft

Group:	Discovery
Team members:	Erik Bernhardson, David Causse, Trey Jones, Guillaume Lederrey, Stas Malyshev, and Mikhail Popov
Lead:	Dan Garry (product owner)
Updates:	Status updates
Progress:	Progress reports

Starting a page[edit]

Start your project page on mediawiki.org. ^[1] This is where the community will get all the basic information about your project. Everything else will go in subpages, easily accessible from this "home".^[2] This page will have a talk page that is the main, centralized venue for the community to ask you questions and provide feedback.

A good title would look like https://www.mediawiki.org/wiki/Your_team_name/Your_project_title.

Infobox[edit]

You may copy and paste code to generate the nice little box on the right side of the page with the basic info for your project. ^[3].

Background[edit]

Add a Background section. For ideas about what goes into this section, you could answer to questions such as:

What is the rationale for doing the work?^[4]

Which research is it built upon? Were there previous attempts at fixing the same problem, what happened to those? ^[5]

What is changing[edit]

Add a What is changing section.

Describe the change in plain language. ^[6]

State who is going to be affected, and where. ^[7]

Provide examples, wireframes, everything you have to help people understand your work and give feedback about it.

Can people opt out of this change for themselves, if so they wish? If so, explain how.

Timeline[edit]

Add a Timeline section. ^[8]

Feedback[edit]

Add a section about Feedback.

Be specific about the kind of feedback you are looking for. ^[9] Make a clear, sustainable ask.

Point to the feedback page as the venue to collect feedback: if you are asking multiple questions, you can create in advance specific threads in the talk page and then point to each of those separately. ^[10]

references[edit]

↑ mediawiki.org is where most technical documentation lives. Interactions with the community are easier on this wiki as it features Structured Discussions (aka Flow) on talk pages, and the Code of Conduct applies to this technical space.
↑ Because we are editing a wiki, users are aware that content can be a draft, a work in progress. Please provide any missing information when you have it.
↑ Only the "name" and "group" parameters are required. More about the template: https://www.mediawiki.org/wiki/Template:Wikimedia_engineering_project_information
↑ It is important to define purpose and what practical outcomes are expected.
↑ Publish documentation that researches user needs to support the proposal, as well as any past attempts at solving the same issue. Wikimedians will ask you for data, and will want to see that you are not reinventing the wheel.
↑ Keep in mind all the content will be translated in other languages.
↑ Will every user in our environment be affected, or will your project target a specific group of users or wikis, for example?
↑ Even if it is just a rough estimate, information should be provided on roughly when a community member can expect to see a project, feature, or product moving forward at various stages.
↑ Are you asking people to help you pick between two alternatives? Do you need wild ideas thrown at you? Don't let people guess what it is that you need from them. It is important to be considerate of people's time.
↑ Are you thinking of more/different feedback venues? You can explore other options (link here).

[1] wiki.org is where most technical documentation lives. Interactions with the community are easier on this wiki as it features Structured Discussions (aka Flow) on talk pages, and the Code of Conduct applies to this technical space.

[2] Because we are editing a wiki, users are aware that content can be a draft, a work in progress. Please provide any missing information when you have it.

[3] Only the "name" and "group" parameters are required. More about the template: https://www.mediawiki.org/wiki/Template:Wikimedia_engineering_project_information

[4] It is important to define purpose and what practical outcomes are expected.

[5] Publish documentation that researches user needs to support the proposal, as well as any past attempts at solving the same issue. Wikimedians will ask you for data, and will want to see that you are not reinventing the wheel.

[6] Keep in mind all the content will be translated in other languages.

[7] Will every user in our environment be affected, or will your project target a specific group of users or wikis, for example?

[8] Even if it is just a rough estimate, information should be provided on roughly when a community member can expect to see a project, feature, or product moving forward at various stages.

[9] Are you asking people to help you pick between two alternatives? Do you need wild ideas thrown at you? Don't let people guess what it is that you need from them. It is important to be considerate of people's time.

[10] Are you thinking of more/different feedback venues? You can explore other options (link here).

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]