Page MenuHomePhabricator

Create Project: Section-Name-Diff
Closed, ResolvedPublic

Description

The Community Tech team has begun a new project to include the section name in the diff.

Name: Section-Name-Diff
Type: Component
Description: The Section Name in Diff (SND) project aims to enhance the diff experience. Under the current system, users cannot see the applicable section name in the diff in many circumstances. This behavior often obscures the context behind the diff. With this project, we plan to add the section name, so that users can better understand diffs in relation to page structure. This project was the #9 request from the 2019 Community Wishlist Survey.

Event Timeline

@ifried: If I understand correctly, this is a subset of MediaWiki-Page-diffs ? So it could either be a subproject, or if it was a separate top-level project there could be a Herald rule to always add MediaWiki-Page-diffs to any tasks in this new project.

@ifried: If I understand correctly, this is a subset of MediaWiki-Page-diffs ? So it could either be a subproject, or if it was a separate top-level project there could be a Herald rule to always add MediaWiki-Page-diffs to any tasks in this new project.

@ifried {{ping}} do you want this as a subproject or a separate top-lever project?

Hello, @Aklapper. I'm open to making it a subproject or a separate project tag, as long as it's easy for the Community Tech to separately track the project. This is because the Community Tech team does not generally maintain diff pages, but we will be focusing on them for a certain time when we add the section names to the pages.

What do you think, @MBinder_WMF and @ARamirez_WMF?

Aklapper claimed this task.

As subprojects have some disadvantages (membership as this is only "for a certain time"), I created a top-level project:

Requested public project Section-Name-Diff has been created: https://phabricator.wikimedia.org/project/view/4668/
Please encourage interested people to visit the project and to join the project as members, and to watch the project in order to receive updates!
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.

Note that I also created Herald rule H359:

Thank you, @Aklapper! I will add this tag to the relevant tickets.

Ah, I saw in T242264 that the Herald rule removes Community-Tech Kanban tags so I changed it to NOT add Community-Tech. It is now:

Hey, folks. Sorry I'm late to this, for some reason I either wasn't getting or wasn't noticing my notifications on this task. Glad you resolved it! Couple of things:

  • I'm glad this didn't end up as a subproject, as the Commtech team has many tags/boards like this new one, and a subproject in all of that could have been confusing (I also have just generally shied away from subprojects since top-level tags are much more flexible, though Milestones have been useful to my teams).
  • There is already a Herald for Community-Tech here: {H260}. I think the new one should probably be merged into that one. What do you think, @Aklapper ?
  • While I'm all for @Aklapper doing all this, we should probably get @ARamirez_WMF (the team's Program Manager) project-creation access, because this is a regular thing for this team. I'm already working with @ARamirez_WMF regularly, and I'm happy to help on this sort of thing in the future, including updating that Herald as the tags are created. @ARamirez_WMF , if you don't have project-creation access, let's chat about that separately and I'll point you in the right direction. :)
  • There is already a Herald for Community-Tech here: {H260}. I think the new one should probably be merged into that one. What do you think, @Aklapper ?

H359 does not add Community-Tech so it should not be merged. H260 could be edited to add Community-Tech to Section-Name-Diff tasks, though it'll have the side effect that an existing tag "Community-Tech (Kanban-Q3-2019-20)" would get replaced by Community-Tech - you know best what's good here. :)

  • While I'm all for @Aklapper doing all this, we should probably get @ARamirez_WMF (the team's Program Manager) project-creation access, because this is a regular thing for this team. I'm already working with @ARamirez_WMF regularly, and I'm happy to help on this sort of thing in the future, including updating that Herald as the tags are created. @ARamirez_WMF , if you don't have project-creation access, let's chat about that separately and I'll point you in the right direction.

Sure! See T706 :)

H359 does not add Community-Tech so it should not be merged. H260 could be edited to add Community-Tech to Section-Name-Diff tasks, though it'll have the side effect that an existing tag "Community-Tech (Kanban-Q3-2019-20)" would get replaced by Community-Tech - you know best what's good here. :)

Ah, I misunderstood. Thanks for clarifying. @ARamirez_WMF and @ifried , typically when new tags for the team are created, they'll need to be added to the H260 Herald rule. Other teams have a template task link for just such a thing. Example:

Annotation 2020-03-30 123508.jpg (407×477 px, 32 KB)

I recommend the same thing for Commtech. We can chat about this in our existing 1:1s.

Sure! See T706 :)

Yup, I'll go over this with @ARamirez_WMF . Thanks again! :)