Community Wishlist/Staff instructions

This page documents how to administer the Community Wishlist. Technical and Movement Communications instructions are aimed at Community Tech staff, while all other instructions are applicable to all staff. Some tasks may require administrator or translation admin access.

Wish life cycle

Here is the general overview of what happens to wishes:

1. User submits a wish at Community Wishlist/Intake, which is initially given a status of "Submitted".
2. The wish shows up at the list of recent wishes at Community Wishlist, as well as Community Wishlist/Wishes.
3. Staff review the wish
   1. If it is "good", prepares it for translation and in doing so changes the status to "Open".
   2. If it needs clarification, staff will seek clarification via the talk page.
   3. If it is a policy change or incoherent, the status is instead changed to "Archived" and the wish appears at Community Wishlist/Archive

Some time later

1. Staff later assign a focus area to the wish, grouping it together with other similar wishes.
2. With or without a focus area influencing progress, the wish is eventually started and the status changed to "In progress".
3. If it is a Community Tech project, a project page will be created at i.e. Community Wishlist/Project name.
4. If something is standing in the way of the wish being completed, the status can be changed to "Blocked".
5. Once the wish is fulfilled, the status is changed to "Delivered".
6. The wish lives on happily forever and forever as reality.

Reviewing wishes

Playbook

• If a wish is unclear, ask clarifying questions on the talk page.
• If it articulates a clear problem and is well-defined, proceed to preparing it for translation.
• As needed, assign focus area as applicable and share with relevant stakeholders.

Criteria for wish inclusion

See Community Wishlist#How to write a good wish for guideline for wish authors. This is however merely a guideline. It's up to you to make the judgement call on whether the wish is worthy of inclusion.

Traits that make a good wish, which is more likely to align to a focus area include:

• Clearly demonstrates a problem
• Illustrates a potential positive outcome and/or user struggle
• Can be solved by product and tech teams or stakeholders
• Is written for anyone to understand
• May or may not offer a solution

Traits that make a valid, but less successful wish include

• Only offers a solution
• Extremely specific or niche, requiring expertise or lots of review

Traits that make an archived wish include:

• Non-product or technical related (ie, Policy change)
• Incoherent

Preparing wishes for translation

When you see a wish that is well-written and clearly fit for inclusion in the Wishlist, please proceed with preparing and marking it for translation. This is assuming the wish does need any further modifications to the description. More changes of course can be made if needed, but they will require intervention from a translation admin.

1. Make sure you are logged in with a staff account.
2. Browse to a wish pending translation, which are categorized at Category:Community Wishlist/Wishes/Untranslatable.
3. Click on the "Prepare for translation" button.
4. You are brought to the source editor for the wish, and <translate> tags are automatically added around the applicable fields.
5. Add any <tvar> syntax or other changes as deemed necessary.

For translation administrators:

6. Click on the "Mark for translation" link at the top.
7. You are then brought to Special:PageTranslation for the wish. The "Allow translation of page title" option seen towards the top should be automatically unchecked. If it is not, uncheck it.
8. Review your work once more if you'd like, and click "Mark this version for translation".

Please ensure you have read and understand these resources before engaging in administration of translations:

• mw:Help:Extension:Translate/Page translation administration
• mw:Help:Extension:Translate/Page translation example

Templates

• {{Community Wishlist/All projects}} – template used to localize the word "All projects".
• {{Community Wishlist/Status}} – displays a status chip for the given value. Used for both wishes and focus areas.
• {{Community Wishlist/Submit wish}} – localized button to submit a wish.
• {{Community Wishlist/Type}} – normalizes display of the type of a wish.
• {{Community Wishlist/Wish}} – presentation logic for wishes, with localized labels for the form fields.
• {{Community Wishlist/Focus area}} – presentation logic for focus areas.
• {{Community Wishlist/Wishes}} – used to show a table of wishes. This template wraps one of the following four templates to get the actual rows of the table:
  • {{Community Wishlist/Wishes/All}} — used the All wishes page.
  • {{Community Wishlist/Wishes/Recent}} – used on the dashboard.
  • {{Community Wishlist/Wishes/Archive}} — used the Archive page.
  • {{Community Wishlist/Wishes/<Focus area slug>}} – each focus area has its own table of wishes.
• {{Community Wishlist/Wishes/Row}} – represents a single wish or row in a table of wishes. This is used within the Wish or Focus area templates, above.

AbuseFilters

• Special:AbuseFilter/355 – disallows non-staff from changing restricted fields

Glossary

These are words that are used throughout the wishlist, either internally in the code, or on the wiki. This glossary should serve as a single go-to when you hear a term regarding the wishlist and you don't know what it means.

Affiliate (or volunteer developer)

Someone who works on a wish who is not Foundation staff.

Area

A more brief word for what is formally referred to as a "focus area".

Affected users

The primary group of users (such as administrators, readers, etc) that a wish will have an effect on.

Audience

The internal engineering term for "affected users".

Base language

The original language that a wish was proposed in. This term is mainly only relevant to engineers.

Dashboard

The landing page: Community Wishlist. This will eventually allow users to filter wishes, show statistics, and more.

Focus area

A group of three or more wishes in the same problem space. Focus areas are what participants vote on.

Focus area subpage

The /Translatable subpage of a focus area page that is used for translation. This is transcluded on the focus area page so that when participants vote, the page does not need to be re-marked for translation.

Participant

Any non-staff user who engaged in the wishlist by means of editing, including voting.

Task

Internal engineering term for a Phabricator task.

User

Any person who uses the wishlist, even as just a reader.

Voter

Refers specifically to participants who voted in the wishlist.

Wish

Also known as a proposal: a page created by a wish author that documents a technical desire.

Wish author

Also known as a proposer: the user who created the wish.