Estimated at one point, but we hadn't previously anticipated this work, may need to alter sprint commitments to accommodate (CC'ing @ovasileva for context ) or consider taking this on next week - revisit at Thursday Task Sync on Oct 26

Next steps:

• Add unit testse
• Fix typescript-related build error
• @Mabualruz to review

@Jdlrobson to sync with @Mabualruz further on this re: integration testing of skins - patch and/or followup discussion

@KSarabia-WMF can you update as to current status / open questions / next steps?

@Mabualruz to review , plan to backport this week

There are pixel implications for this change - a few options available:

1. mark as valid in pixel (likely not possible)
2. include in previous release (cherry-pick to previous deploy branch)
3. delay merging this patch

Patch forthcoming to address a typo, backport planned for later today

Hi everyone -
Is there another deployment training coming up that Moh could participate in / would it be possible to set one up if not?

Trying this out again with the sprint that began on Oct 9 -- we will re-evaluate in 2 weeks

Decided not to go forward with this given other currently ongoing experiments

In T345664#9173550, @Ladsgroup wrote:

In T345664#9170904, @NHillard-WMF wrote:

• We will scope out other ways to store the preference. We have already created https://phabricator.wikimedia.org/T346375 in which @Ladsgroup gave us valuable feedback about potential considerations for storing this kind of thing in user_preferences – based on this reply, it sounds like we will need to think about other options in this space.

One thing is that storing in user_properties table for logged-in user preferences has been the canonical place to store such data in the past ten years at least. I said it's blocked because that table is exploding doesn't translate to we need to find a way around it. Adding a new competing system next to the existing one (user_properties) will lead to overhead of maintenance, migration and clean up in the next couple of months or so.

If this is blocking the team, IMHO, we should pool resources to get this fixed ASAP as if it's not fixed soon, it'll cause issues regardless of adding new user prefs to that table or not.

Hi @Krinkle -
Thank you for sharing your feedback. I understand and appreciate the concerns you’ve raised about the preference persistence mechanism.

This looks good - thanks @KSarabia-WMF

Approved

Thanks everyone for weighing in with feedback!

Resolving - great job everyone who worked on this!
The decision has been made and posted to the decision record page here

The latest on this is that we would have our first interview of this type likely the week of Sept 4

I'm Lauralyn's manager and I approve this request!

Closing this - we've conducted several interviews now with the proposed updates

Hi @Aklapper - thanks for going over these options!

@bwang to add test steps specific to this issue

We've synced with Metrics Platform about this -- more followup here: https://phabricator.wikimedia.org/T344274

This looks good - thanks @KSarabia-WMF !

This looks good - thanks @Jdlrobson and @KSarabia-WMF !

A bit late here, but this was resolved back in July - Thanks @Jdlrobson and @Jdrewniak !

Finished update of resume criteria in conjunction with Growth

Approved