In T230831#5433325, @Aklapper wrote:

Alright, my understanding is that we go for subprojects. Correct me if I misunderstood. :)
One warning: Soon-to-be-parent project #GrowthExperiments has two members but Projects that are parents of subprojects cannot specify members. Instead, the members of all its subprojects are treated as being is members.
Then, if I get it right, I could:

• Due to T224421: move_project script does not check if task is in both future parent and future subproject and does not remove future parent project, silently mass-remove the #GrowthExperiments soon-to-be-parent project tag from the currently 83 tasks which already have one of the #GrowthExperiments-*soon-to-be-sub project tags.
• Run CLI script to convert those 8 projects above into subprojects of #GrowthExperiments.
• Because "If a project has no subprojects, but then one is added, the existing Project becomes a “parent” Project and all of its members shift to that first Subproject", potentially remove these members again from the first subproject created.
• Update project tag description by removing all the "See Also" links in https://phabricator.wikimedia.org/project/profile/3716/
• (Reminder to myself: A task can be associated with more than one subproject of the same parent project, so nothing to fix/worry there.)

If that's all fine with you, then please feel free to assign this task to me.

The Growth-Team discussed this and will keep an eye on it but we can not take this work on at this moment because we have planned feature work to do. I am adding members of the Editing-team as well as a result of their future work with Talk pages.

It appears someone else is working on this. So the Editing-team is moving this to external.

The Editing-team isn't actively working on this particular skin

Putting this in investigating since @Esanders is still getting input on it

In Triage we determined to move this to Design Review since the patch is done and @ppelberg is okay with this change. Once @iamjessklein puts her final seal of approval on this we can deploy.

We will take a look at this ticket when we have a lull in feature work.

There doesn't appear to be an action for the Editing-team at this time

The team tried to do a quick backport and it appears it did not work, for that reason I am moving this to the freezer.

In Triage we determined we will move forward with what @Esanders suggested in the last line

@ppelberg will confirm whether this task is necessary or if Megan and Neil will do with T230367

Once the VE as Default work is complete we will pull this work into our current sprint

We would like to consider this ticket with the lede edit button T203151 so when we start that work we will return to this ticket

@ppelberg is working on this and will create children to this task

@Esanders made some changes to make it quicker, but there aren't plans to do much more with it at this time

Hey @SubrahamanyamVarma when should we expect to start paying attention to this?

Due to the release of Edit Cards v3 this task is no longer valid

During Triage, we discussed this task representing the divergence between desktop and mobile but we have now we are shifting focus to Talk Pages so for that reason this task is deprioritized.

This specific case has been resolved, so for that reason the Editing-team is closing this ticket.

The overlay fix, is it for the Editing team to fix or Readers Web @Esanders ?

In the Humans of the Web meeting it was determined that all of the changes that needed to happen on the Editing side did (it was shrunken down). At this point, the ball is in Readers Web court to either shrink it on their end as well or determine you all feel comfortable with the inconsistency.

Hey @dchan what would be the level of effort to implement something like this?

This appears to be done so I am removing Jess' tag

@iamjessklein will put the results in this ticket. Once done she will remove her tag and then move it to Peter's column on the current work board.

Hey @ppelberg this is ready to be closed. @DLynch and @Esanders it looks like you're still commenting on this thread, should the conversation be migrated to an investigation ticket (spike)?

Hey @ppelberg we need you to close this out

@Esanders it looks like you and @iamjessklein is working on this together?

Looks like this is being worked on.

Thanks for getting on this so quickly @MNeisler and @Neil_P._Quinn_WMF !

@marcella and @MMiller_WMF are going to discuss this

Hey @SBisson are you still planning to work on this or should we reassign?

This is actually an epic so I am moving this to the correct column

Just moving this to the proper column on the VE workboard

@ppelberg it is your call to determine if this is high priority or should go in the freezer