I'll just add a history note here: Collaboration Team agreed to complete this some two years ago. There were some delays based on dependencies. But my understanding is they are cleared now.

Change 468688 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/extensions/TheWikipediaLibrary@master] Update notification language to match what was requested on Phabricator

https://gerrit.wikimedia.org/r/468688

@Samwalton9 -- is this still something you need or are waiting on? If so, we can put it in our sprint so that @Catrope can investigate and remember its status. Then we'll decide if/when to work on it.

Yes, we'd still love to have this!

Change 468688 merged by jenkins-bot:
[mediawiki/extensions/TheWikipediaLibrary@master] Update notification language to match what was requested on Phabricator

https://gerrit.wikimedia.org/r/468688

Change 469150 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/extensions/TheWikipediaLibrary@master] Use a hidden global preference to show the notification only once

https://gerrit.wikimedia.org/r/469150

While I apologize for the very long delay, technical advances in the meantime have made this easier to build. Now that GlobalPreferences exists, it was much easier to make this a notification that fires only once per global user. I also made it be based on the global edit count and registration time.

Once the above patch is merged, I think this extension will be ready for security review and deployment.

Change 469150 merged by jenkins-bot:
[mediawiki/extensions/TheWikipediaLibrary@master] Use a hidden global preference to show the notification only once

https://gerrit.wikimedia.org/r/469150

I feel like this was one of the first tickets I put in for development when I started here three years ago. I'm no longer on this team but happy to be able to look @Samwalton9 in the eye next time I see him. I know there were some issues that kept it blocked. But thanks for picking up @Catrope!

@Catrope, any idea of when that new notification will be available? That's for Tech News.

In T132084#4693920, @Trizek-WMF wrote:

@Catrope, any idea of when that new notification will be available? That's for Tech News.

It'll need to go through security review first, then be deployed to beta labs, then be deployed to production. So it'll probably be a few weeks, and I'll be able to give ample notice to you for Tech News and to @Samwalton9 .

Thanks @Catrope. If you can give that notice two weeks before it is public, that would be great. :)

I am ambiguous. Whilst enabling of resource access among editors is un-doubt-ably noble, we need to remember that there are not infinite subscription tokens.

This will lead to a massive influx of application requests from every extended-confirmed newbie (obviously, in good faith) and coordinators will have a very hard time separating the wheat from the chaff. If we need to do this; we ought to restrict the count of 500 edits to main-space.

And before introducing this on en-wiki; there needs to be a local RFC.

Change 524052 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/tools/release@master] Add TheWikipediaLibrary extension

https://gerrit.wikimedia.org/r/524052

In T132084#5343642, @gerritbot wrote:

Change 524052 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/tools/release@master] Add TheWikipediaLibrary extension

https://gerrit.wikimedia.org/r/524052

Reminder to add it to the Dev/Maintainers page. :)

Change 524059 had a related patch set uploaded (by Catrope; owner: Catrope):
[operations/mediawiki-config@master] Deploy TheWikipediaLibrary to beta labs

https://gerrit.wikimedia.org/r/524059

Change 524059 merged by jenkins-bot:
[operations/mediawiki-config@master] Deploy TheWikipediaLibrary to beta labs

https://gerrit.wikimedia.org/r/524059

Change 524052 merged by jenkins-bot:
[mediawiki/tools/release@master] Add TheWikipediaLibrary extension

https://gerrit.wikimedia.org/r/524052

https://www.mediawiki.org/w/index.php?diff=3321157&oldid=3321131&title=Developers/Maintainers

Change 524251 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[operations/mediawiki-config@master] extension-list: Add SecureLinkFixer and TheWikipediaLibrary

https://gerrit.wikimedia.org/r/524251

Does this mean the notifications are now live?!

And just a quick check - is this only going out to newly-eligible users or will people who've already crossed the threshold get a retroactive alert? Just curious.

In T132084#5346565, @Samwalton9 wrote:

Does this mean the notifications are now live?!

No. It's live on the Beta Cluster. Can't be live in production for at least 12 days' time, sorry.

In T132084#5346565, @Samwalton9 wrote:

Does this mean the notifications are now live?!

And just a quick check - is this only going out to newly-eligible users or will people who've already crossed the threshold get a retroactive alert? Just curious.

It's supposed to send a retroactive alert to people who have already crossed the threshold once they make an edit (at least that's how it's currently designed). But right now it's not working at all, neither in beta labs nor on my localhost, and I haven't yet figured out why. I'm pretty sure it worked when I first submitted it for a security review. Never mind, now it's working after all.

Please also document at https://www.mediawiki.org/wiki/Help:Notifications/Notifications_types -- Thank you!

Once this is ready to go into production two weeks from now (and once https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TheWikipediaLibrary/+/524062 has been merged), I'll enable this in test.wikipedia.org first, and @Samwalton9 and I can then discuss where to roll it out from there.

In T132084#5347112, @Catrope wrote:

In T132084#5346565, @Samwalton9 wrote:

Does this mean the notifications are now live?!

And just a quick check - is this only going out to newly-eligible users or will people who've already crossed the threshold get a retroactive alert? Just curious.

It's supposed to send a retroactive alert to people who have already crossed the threshold once they make an edit (at least that's how it's currently designed). But right now it's not working at all, neither in beta labs nor on my localhost, and I haven't yet figured out why. I'm pretty sure it worked when I first submitted it for a security review. Never mind, now it's working after all.

We're not entirely sure we'd want that to happen. Mostly because of this

In T132084#5043312, @WingedBladesofGodric wrote:

And before introducing this on en-wiki; there needs to be a local RFC.

While we could potentially get away with one notification being sent to relatively new editors, retroactively notifying editors might cause some stir we aren't prepared to handle at the moment.

Thanks @Catrope!

We're going to have a chat about how/when is best to roll this out - we're right around the corner from changing the mode of access for most of our content. As such, delaying the rollout for a few months might be a good idea. I'll confirm.

Don't forget to move the task to "announce in next Tech/News" when ready!

Change 524251 merged by jenkins-bot:
[operations/mediawiki-config@master] extension-list: Add SecureLinkFixer and TheWikipediaLibrary

https://gerrit.wikimedia.org/r/524251

In T132084#5348539, @AVasanth_WMF wrote:

While we could potentially get away with one notification being sent to relatively new editors, retroactively notifying editors might cause some stir we aren't prepared to handle at the moment.

It would be easy to change the code so that only editors who created their account after the extension goes live get this notification. It would not be easy to only notify users who qualify after the extension goes live (i.e., to eliminate retroactively-qualified users but nobody else), but it would be easy to approximate that by excluding users who created their account more than 6 months before the extension went live (or some other cutoff date).

Is there any way we could proactively notify the community about this such that they could turn a setting off to avoid the notification? Maybe I'm overthinking it, I can just see the potential for a negative reaction, even if it is just a single notification. Do you have a sense of how receptive the community has been to new notifications in the past?

If it's a choice between everyone and only folks who registered from now on, I'd definitely prefer the former. We're just about to make the library considerably easier to use so letting everyone know it's available to them like this is actually a great opportunity.

Do you have a sense of how receptive the community has been to new notifications in the past?

You can look at how https://www.mediawiki.org/wiki/Extension:GettingStarted was received.

Just an update that it's currently looking like we'd want to enable this around the end of October. Will update with a more specific date when known.

I've just noticed this thing run in beta (P9795) after editing enwiki there for the first time in a few months - are we supposed to be directing people towards a (in this case, non-beta.) wmflabs.org site?

Per the task description, https://wikipedialibrary.wmflabs.org/ is the intended target, if that's what you're asking.

@Samwalton9, I'm not sure that a notification about how to avoid a single notification is a good idea. I do think you should consider ways of staggering the effect, so that not everyone tries to sign up on the same day. Maybe notify people with 10K (or a particular user right first), and then people with 2K edits (or a different user right), etc.? And do different languages of Wikipedia on different weeks? Or split by user id number? (I'm pretty sure that's already possible in Echo's code, as part of a scheme for A/B testing.)

That's a great point.

If it's technically feasible then I'm very much on board with a staggered rollout so that we don't have a huge number of folks jumping in at one time :)

I always support staggered notifications grouped by number of edits (or whatever other statistic is easy for you to collect).

@Catrope: Hi, all related patches in Gerrit have been merged. Should this task be resolved? Or is there more to do in this task? Should you still be task assignee? Asking as you are set as task assignee. Thanks in advance!

We've conducted an investigation (T269849) into the status of this extension and will be completing the newly filed subtasks prior to deployment, which we currently expect to take place in Q4.