Nvm @bwang graded all the takehomes already (hero), dropping my proposed point value to 3

In case 5 points is spicy

3 points as we should ensure there's some test coverage accompanying the patch around the ID behavior

Steph to add points (2/3)

The web team is at an offsite this week. It has been marked it as "in progress" to make sure this is ready for our next sprint which begins on January 13. Our understanding is that Web and Content Transform agreed to revert it given very few people were going to be around in the last deploy window of last year and this felt like a risky change with that in mind.

Steph to re-review https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MobileFrontend/+/1101931 in the new year, then work with Jon to rescope this ticket

To be checked in presumably the new year (next week once a new schedule has been generated)

Didn't hear any objections, so moving this to signoff

Gotcha, thank you! Since it's parsoid specific we should definitely prioritize getting this fixed, but I don't believe it's related to the work we're doing right now in T374883

Moving back to ready as it's not actively being worked on - probably we should formally roll it over to next sprint (once the board is made)

Justin to confirm the title - as Kim mentioned, I can update the title in code, but I believe only Jan can publish

Interesting - do we know whether the ID of -1 is coming from the template or from the make sections transform hitting an error?

pending estimate

pending estimate

pending estimate

pending estimate

pending estimate

pending estimate

pending estimate

pending estimate

pending estimate

pending estimate

Oh wait sorry for the spam - the description did indeed update, but I'm remembering Jan said we would need to make a code change to update the title. I'll post in the team channel to figure out what next steps are for this ticket since it's either done or stalled depending on the answers to 1. Spanish and 2. title

Unless there is another chrome web store listing, I'm still not seeing the update ):

Kim to double check on the status of this

@ovasileva do we know if Jan did this?

@SToyofuku-WMF to lead estimation for this

@NBaca-WMF to follow up on this

@ovasileva as part of signoff - when should this be turned off?

@Jdrewniak to start a convo in web team channel about when to turn it off

@Jdlrobson @Jdlrobson-WMF this ticket seems to be a ghost? 👻

jk search is broken Jon to leave comment @Jdlrobson @Jdlrobson-WMF

QA would likely be ensuring search is still working on the beta cluster

Jan to quickly QA to make sure that this was indeed deployed and post here supporting evidence

Justin confirmed people are getting the survey

When picking this up, make a post in #talk-to-web and CC the author of the ticket to make sure this is a priority to be done, per our established norms

can be done in parallel with T378115, but worth coordinating to make sure we understand how to gate effectively

Changing the spirit of this ticket to be:

• help with the parts of legal review that are not on our team (session length mixin, ensuring it gets done and liaising as needed)
• legal review for the more common metrics that we typically go through legal review for

Reminder to double check day of with @sgrabarczuk!!