Page MenuHomePhabricator

Migrate Community Wishlist to CommunityRequests extension
Closed, ResolvedPublic

Description

Background

For years, we've utilized bots and gadgets to power the annual Community Wishlist Survey, and now the ongoing Community-Wishlist. We have always wanted to have an extension, but went the gadget route in the interest of time. The usual bot/gadget solution is working quite well, albeit with numerous hacks and quirks, and scalability will likely eventually become a problem.

This task is for planning the migration.

Road map

Translations

Extension

NOTE: scope is limited to feature parity with the gadget, except for pagination of wishes
Data persistence

The Community Wishlist is to be fully data-driven. We need APIs to build out a proper dashboard, provide pagination, etc. For now we should aim for a mix of both structured data in database, while still having wiki pages be the initial source of the data.

Presentation

The Vue code doesn't change much between gadget and extension, so this can come last. Ideally most of it will be in place for the security review, but the translations and data persistence are the more important bits because the gadget can be adapted to use APIs.

Details for QA

As this is a parent task for various other tasks, QA could be done once all it's children of this task are resolved.

Related Objects

StatusSubtypeAssignedTask
Resolved MusikAnimal
Resolved Jly
Resolved MusikAnimal
Resolved MusikAnimal
ResolvedBUG REPORT MusikAnimal
ResolvedHMonroy
Resolveddmaza
Resolveddmaza
Resolved MusikAnimal
ResolvedHMonroy
ResolvedGoal MusikAnimal
Resolved MusikAnimal
Resolved MusikAnimal
Resolved MusikAnimal
Resolved MusikAnimal
OpenNone
Resolved MusikAnimal
Resolvedtstarling
Resolved MusikAnimal
Resolved MusikAnimal
Resolved MusikAnimal

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Change #1092415 merged by jenkins-bot:

[integration/config@master] Zuul: [mediawiki/extensions/CommunityRequests] Add Translate as Phan dependency

https://gerrit.wikimedia.org/r/1092415

We need the equivalent of T387961 but for focus areas, and it should be a subtask of T388216. Scratch that. I guess we won't be using Vue (and thus need an API) to show focus areas.

One thing that's confusing me… I believe we are actually using parser tags and not functions. The reason is T279094. We ran into the same issue when working on MediaWiki-extensions-Phonos, see T317112#8216296,

EDIT: Clarified at T388219#10621637 that we aim to use parser tags for presentation, parser functions for storage.

Change #1074321 abandoned by Samwilson:

[mediawiki/extensions/CommunityRequests@master] Add translation button to DiscussionTools threads

Reason:

This functionality is being added to the DiscussionTools extension.

https://gerrit.wikimedia.org/r/1074321

MusikAnimal claimed this task.
MusikAnimal updated the task description. (Show Details)

What does this mean for Wishlist intake gadget? Should those tickets and the codebase get archived? If yes, then please follow Projects-Cleanup.

What does this mean for Wishlist intake gadget? Should those tickets and the codebase get archived?

+1, I have the same question :)

@KSiebert: Would you maybe have an answer to the previous question? Thanks in advance!

@Aklapper Yes, the wishlist extension has replaced the gadget completely and tickets can be archived and codebase can be archived. @dmaza is there anything left in the codebase we might need?

@Aklapper Yes, the wishlist extension has replaced the gadget completely and tickets can be archived and codebase can be archived. @dmaza is there anything left in the codebase we might need?

Not that I'm aware. This work is complete as far as I know.