Page MenuHomePhabricator

Create a village pump invitation for the 2015 Community Wishlist Survey
Closed, ResolvedPublic

Description

Let's write up an invitation at https://www.mediawiki.org/wiki/Community_Tech_team/Community_Wishlist_Survey/Invitation and then get it translated into as many languages as possible so that we can post it to lots of village pumps.

Event Timeline

kaldari raised the priority of this task from to Needs Triage.
kaldari updated the task description. (Show Details)
kaldari added a project: Community-Tech.
kaldari added a subscriber: kaldari.
kaldari renamed this task from Create and translate a village pump invitation for the 2015 Community Wishlist Survey to Create a village pump invitation for the 2015 Community Wishlist Survey.Sep 29 2015, 11:54 PM
kaldari added a project: Community-Tech-Sprint.
kaldari set Security to None.
kaldari added subscribers: Johan, DannyH.
kaldari triaged this task as High priority.
kaldari moved this task from Ready to In Development on the Community-Tech-Sprint board.
  • The second link of the Wishlist Survey invitation goes to an empty page. (If that's intentional then I welcome placeholder content.)
  • The Wishlist Survey invitation text covers phase 1 and phase 2 ("we'll ask you to vote"). "Analysis and prioritization" is probably phase 3? (I only found out about "Analysis and prioritization" after clicking the "How to submit a proposal" link. That wording implies it's only a link explaining phase 1.) I'd expect the invitation text to explain what (not) to expect from the Community-Tech team to help me decide whether to spend time participating in this Wishlist Survey.

I was clicking your links so the following items are not related to the invitation text itself:

  • "The voting methodology will be left up to the community(?)": I'd expect a clearly defined phase 2 before even starting with phase 1, without any question marks left.
  • "will be copied to a new wiki page", "will be updated on the wiki page": These strings should be links, even if only to placeholder pages.
  • What is the relation between existing items on m:Community Tech project ideas and the results of the Wishlist Survey, once available?

The second link of the Wishlist Survey invitation goes to an empty page. (If that's intentional then I welcome placeholder content.)

Done.

The Wishlist Survey invitation text covers phase 1 and phase 2 ("we'll ask you to vote"). "Analysis and prioritization" is probably phase 3? (I only found out about "Analysis and prioritization" after clicking the "How to submit a proposal" link. That wording implies it's only a link explaining phase 1.) I'd expect the invitation text to explain what (not) to expect from the Community-Tech team to help me decide whether to spend time participating in this Wishlist Survey.

Sure, you could call "Analysis and prioritization" phase 3. The reason we didn't include analysis and prioritization in the invitation is that Johan, our community liaison, suggested that we keep it as simple as possible so that it doesn't become tl;dr. What do you think about the trade-off of making the invitation longer and more complicated? Isn't it better to just link to the full explanation?

"The voting methodology will be left up to the community(?)": I'd expect a clearly defined phase 2 before even starting with phase 1, without any question marks left.

Yes, we are actively working on resolving that part of the process. In particular, we're discussing it with the TCB team on Monday so we should have a more clear voting process shortly.

"will be copied to a new wiki page", "will be updated on the wiki page": These strings should be links, even if only to placeholder pages.

Good idea.

What is the relation between existing items on m:Community Tech project ideas and the results of the Wishlist Survey, once available?

No direct relation. As the Community Tech project ideas page says, it is intended for brainstorming ideas, not prioritizing them. We will, however, be inviting people to submit ideas from that page as survey proposals.

Sure, you could call "Analysis and prioritization" phase 3. The reason we didn't include analysis and prioritization in the invitation is that Johan, our community liaison, suggested that we keep it as simple as possible so that it doesn't become tl;dr. What do you think about the trade-off of making the invitation longer and more complicated? Isn't it better to just link to the full explanation?

Ah. May I rewrite the second paragraph to drop that "Phrase 123" stuff to something like:

For the start, we're inviting all active editors to submit brief proposals: Explain the project that you would like us to work on, and why it's important. After two weeks, we will ask you to vote on the proposals. Afterwards we will analyze and prioritize them.

@Aklapper: That mostly sounds good, but isn't a completely accurate description. I'll try to incorporate some of your wording into the invitation though, especially to explain what happens after the voting phase.

Added some info about the analysis and prioritization step and submitted for translation.