Jump to content

Community Wishlist/Staff instructions

From Meta, a Wikimedia project coordination wiki

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

[edit]

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

[edit]

Playbook

[edit]
  • 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

[edit]

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

[edit]

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:

  1. Click on the "Mark for translation" link at the top.
  2. 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.
  3. 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:

Creating focus areas

[edit]

Wishes are assigned to a focus area by editing the wish page and adding a value (that we're calling the 'slug') for the |area= parameter. Then, the actual focus area page is created with the same slug. For example, after adding |area=Lorem ipsum to a wish, the Community Wishlist/Focus areas/Lorem ipsum page should be created.

To create a focus area page, enter its slug in the box below:

This will open the new wish page for editing in VisualEditor. You'll need to click on the focus area template and click 'Edit' to open it in the template form, from where all fields can be filled in. Alternatively, you can switch to source editing and add all required fields there.

After saving the focus area page and marking it for translation, add its slug to the list in Community Wishlist/Focus areas (and possibly the similar list on the dashboard, if it's a featured focus area).

Templates

[edit]

AbuseFilters

[edit]

Glossary

[edit]

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.
Participant
Any non-staff user who engaged in the wishlist by means of editing, including voting.
Slug
The part of a URL that uniquely identifies a wish or focus area. This is not necessarily the same as the "title". Wishes live at Community Wishlist/Wishes/<wish slug> and focus areas live at Community Wishlist/Focus areas/<focus area slug>.
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.

Notes

[edit]