Page MenuHomePhabricator

Create project tag for ReaderExperiments-ImageBrowsing
Closed, ResolvedPublic

Description

Name of the project tag:
ReaderExperiments-ImageBrowsing

Type of project:
Component

Description (read the best practices and include a sentence understandable to the public and without "This project is for tracking work related to..." noise, plus a link to further information!):
We want to make it easier for new readers to find Wikipedia useful. In order to do this, we want to be more accessible for different kinds of new readers, including visual learners. To do this, we plan on working on one of the Community wishlist focus areas: Improved discovery of media files.
Specifically, we want to experiment with a feature that will make discovery of images and videos easier on Wikipedia.
https://www.mediawiki.org/wiki/Readers/Reader_Growth/WE3.1.3_Image_Browsing

Canonical code repository URL of the project (if this project has a code base):
https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/ReaderExperiments/+/refs/heads/master
Note: this codebase is shared for multiple experimental projects (ReaderExperiments-ImageBrowsing, ReaderExperiments-StickyHeaders, ReaderExperiments-MinervaTOC)

View policy of the project itself:
Public (default)

Event Timeline

Any ticket assigned this component is part of FY2025-26 WE3.1 Engaging New Audiences & handled by Reader Growth Team
I don't know whether this is possible, but it would be great if any project tagged with this component, would automatically have both of the above tags applied as well.

Note: a lot of the work in this project has already been completed, and most - if not all - tickets should be somewhere on the Reader Growth Team workboard.
However, there are already couple of outstanding tickets, and more may follow depending on the results of the experiment.
Said workboard is rapidly filling up with work from other projects to the point that it is becoming unwieldy and I'm beginning to lose track of these.
Once this tag has been created, I will attempt to locate all relevant tickets (both open and closed) and retroactively assign them to this project.

Aklapper claimed this task.
Aklapper moved this task from Incoming to Projects to create on the Project-Admins board.

Requested public project ReaderExperiments-ImageBrowsing has been created: https://phabricator.wikimedia.org/project/view/8402/

(In case you need to edit the project or project workboard itself at some point and lack permissions, please see Trusted-Contributors.)

Interested people are welcome to join the project as members, and to watch the project in order to receive notifications on task updates.

If tasks are created under this new project which are about a specific codebase, please make sure to also add these codebase project tags to the tasks in addition.

Recommended practices for project and workboard management in Phabricator are available.

Feel free to bring up any questions you might have about Phabricator or about best ways to manage projects in Phabricator.

I've also listed this project on the ReaderExperiments description page on https://phabricator.wikimedia.org/project/profile/8040/

I created the Herald rule H475 with

H475 might want the extra condition project tags incl. their milestones include none of Reader Growth Team, in order to avoid actions like T404743#11495687 for future tasks (assuming that this sort of Herald action wouldn't be desired)

Oh very good point! Thanks so much for catching that! I should have checked if there are Sprint projects. :(
I adjusted H475:

Sorry again for that (and the noise), I restored the Sprint tags on all recently edited tasks.

No worries! I think we could've lived without the sprint tags for all those already closed, but thanks for restoring them! :)