Ciao Sam, thanks for filing this. I'll be scheduling something with you soon.

Thanks for meeting with me @Elitre! Noting here what we discussed:

• To reduce the potential for editor complaints, we should consider a few implementation changes which would reduce the scope of who receives the notification. Suggestions included:
  • Limit the 500 edits to those made in namespace 0.
  • Don't send the notification to an editor who hasn't been consistently active recently, perhaps making their first edit after a long period of time.
• Instead of, or in addition to, the Echo notification, we might want to explore a VisualEditor notification, like the 'add a link' popup editors get when using it for the first time. We discussed that we might want a deeper VE integration beyond this, always having a link to TWL for example. This is probably a future project.
• In terms of translation, we should try to get the notification translated into as many languages as possible in advance of sending it out.
  • It's OK to send it in English if a translation isn't available, but we need to confirm that the English fallback works as expected.
  • We should do our due diligence to ensure that we've invited folks to add their translations.
  • On the notification destination page (the library card homepage) we could have some kind of notice for users coming from the notification apologising if they didn't receive it in their native language.
• We could post on some Village Pumps in advance, letting folks know the notification is coming and where to point folks who have questions

Follow-up thoughts:

Limit the 500 edits to those made in namespace 0

I expect this would be technically complex. We're currently getting the total edit count directly with one query to CentralAuth. Summing over specific namespaces would, as I understand it, require us to make a substantial number of queries per-user every time we wanted to update that figure. Is that accurate @jsn.sherman?

Don't send the notification to an editor who hasn't been consistently active recently, perhaps making their first edit after a long period of time.

I understand the intention with this suggestion, but I'm not sure it's worth the time investment. A user who only edits periodically is likely to have a number of other notifications (e.g. talk page notices) anyway, so would we really expect much pushback from these folks? Additionally, the library might prompt such editors into contributing again if they find it valuable.

It's OK to send it in English if a translation isn't available, but we need to confirm that the English fallback works as expected.

@jsn.sherman @Scardenasmolinar Do we know if this is currently the case? We could probably verify this on beta, right?

We should do our due diligence to ensure that we've invited folks to add their translations.
We could post on some Village Pumps in advance, letting folks know the notification is coming and where to point folks who have questions

If the timing works out we could add a note about this to our upcoming project page announcement (T272367).

Do we know if this is currently the case? We could probably verify this on beta, right?

This should be the case, although we can definitely test it on Beta before we deploy it.

Re: the village pumps heads-up, listing all the precautions taken not to inconvenience folks necessarily may help.
Another thing brought up by my team, which I think you've heard already, is not notifying all the wikis and all the users at the same time to avoid system failures (the latter ties into my suggestion of using tiers for notifications, so you could start from folks with +100k edits, then another day you target the +50k ones, then +10k, +1k, -1k...

@Keegan status?

In T271936#6925149, @Elitre wrote:

@Keegan status?

This work is scheduled for mid-Q4, it's still underway.

@Samwalton9 is this still planned for this quarter?

I think there's a good chance this launch happens next quarter. Best case end of June.

In T271936#7066623, @Samwalton9 wrote:

I think there's a good chance this launch happens next quarter. Best case end of June.

All right, I'll be available when we're ready to start work on this. If it slips into next quarter I'll adjust the tag. Thanks!

@Samwalton9 assuming this is delayed.

Thanks for the ping, yes we're now expecting this launch to happen Q1 FY21/22.

In T271936#7171846, @Samwalton9 wrote:

Thanks for the ping, yes we're now expecting this launch to happen Q1 FY21/22.

Hi again Sam, a reminder to please get in touch with set deadlines and specific requests for help when you are ready, as Keegan is now in a different dept. TY.

Thanks @Elitre - feeling good about this overall at the moment.

Current expectation is for this to start rolling out in early September.

In T271936#7271710, @Samwalton9 wrote:

Thanks @Elitre - feeling good about this overall at the moment.

Current expectation is for this to start rolling out in early September.

In T271936#7271710, @Samwalton9 wrote:

Thanks @Elitre - feeling good about this overall at the moment.

Current expectation is for this to start rolling out in early September.

Hey, how are things?

Hey! This is pushed back a bit, new estimate early October :)

We expect this will begin in the next 1-2 weeks, pending details of deployment. Will update when I have a clear date.

@Samwalton9 thanks for the update. No deliverables expected from my team, correct?

Correct :)

The rollout is happening over the course of the next 3 weeks :)