The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA. The result of the discussion was  Approved.

Operator: Kadane (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 23:48, Thursday, August 9, 2018 (UTC)

Automatic, Supervised, or Manual: Automatic

Programming language(s): Python (Pywiki)

Source code available: Will be within the next day or two

Function overview: Deliver reminders about the WP:PRWAITING backlog to editors that opt-in to receive a reminder. Users will choose which categories to be reminded about, and what interval they would like to receive the reminder.

Links to relevant discussions (where appropriate): Bot Request Current discussion Original Archived Discussion

Edit period(s): Continuous

Estimated number of pages affected: 10-200 per month. There are currently 123 volunteers at WP:PRV, so it will more than likely be towards the lower end.

Namespace(s): User_Talk

Exclusion compliant (Yes/No): Yes

Function details:

Discussion[edit]

I want to address the elephant in the room. I am a brand new editor that has used Wikipedia as a resource for a long time. Even though I have only been here a short time, I have been studying policy and making changes for most of the day (bored college student on summer vacation). I have created a template, fixed lint errors, tagged articles for speedy deletion. I have been on IRC since I started and it has been extremely helpful towards learning the community. There is still a lot that I don't know, but due to the low number of edits and uncontroversial nature of this task, I believe it is a perfect way to get my feet wet.

With that being said, if it is still consensus to close this as WP:BOTNOTNOW, I can provide the code and any explanation needed to a more experienced operator if they want to run this task. Kadane (talk) 23:48, 9 August 2018 (UTC)[reply]

Thank you Kadane! This will, I hope, be a very useful part of our peer review community. This solves the problem of: I am interested in PR, but I forget to check the waiting list. Using this process and a template on the volunteers page, editors can assign themselves a topic and a timeperiod for review updates (e.g. every month, every three months, half yearly, annually). This will be a very useful bot and, I hope, help keep one of WP's more newbie-friendly processes welcoming and active. --Tom (LT) (talk) 00:56, 10 August 2018 (UTC)[reply]
Sure thing. Glad I can help Kadane (talk) 01:16, 10 August 2018 (UTC)[reply]
Can you list who you would target on the first batch as an example? Also, please add a task description to the bot user page. — xaosflux Talk 00:58, 10 August 2018 (UTC)[reply]
@Xaosflux: Description added. Right now there are 48/123 volunteers that are using the ((PRV)) template, all of which have their contact interval set as never. I have pinged all of the people interested in the bot so that they can follow this discussion, but until a user opts-in there is no list to generate. I believe Tom (LT) is updating the rest of the users with ((PRV)) right now, although their default opt-in status will be never. Kadane (talk) 20:20, 10 August 2018 (UTC)[reply]
@Tom (LT): is it possible that you can ping a few participants that might want to opt-in, so I can generate the list that Xaosflux is requesting Kadane (talk) 01:16, 10 August 2018 (UTC)[reply]
Yep, I'll create a a dummy page for testing with me and some other editors. I'll also send out a mass message now that we've got a bot in the works to advise editors on the list to update their desired contact information. I will have to get to this tomorrow though as I'm tied up today :). --Tom (LT) (talk) 01:29, 10 August 2018 (UTC)[reply]
@Tom (LT): Sounds perfect - I made this page: User:Kadane/PRV/Jsondump/Pretty, which will log all "current" subscriptions at WP:PRV. I will ping Xaos when we have had more than just me sign up for notifications. I don't know if you need to setup a dummy page or if you just want to have them change their contact= parameter on WP:PRV Kadane (talk) 20:20, 10 August 2018 (UTC)[reply]

Update: A mass mailer was sent out today asking PRV volunteers to opt in to receive messages from the bot (diff). I move back to my college campus tomorrow, and will be back to my regular schedule Monday, August 20th. I will provide a list of people that opt-in for the first batch at that time. Kadane (talk) 16:33, 13 August 2018 (UTC)[reply]

@Xaosflux: Here is the list, which was updated on 19:40, 14 August 2018. Since then Catriona has added two subscriptions (diff). I still have not moved my personal computer and am on a laptop. I will have my computer on Thursday. When I get my computer I will run the script to update the JSON dump. The bot is ready to trial on September 1st for the first round of messaging. Kadane (talk) 18:32, 21 August 2018 (UTC)[reply]
Seems pretty low-impact, and a good idea. Let's start with a short trial. Approved for trial (7 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. SQLQuery me! 15:34, 28 August 2018 (UTC)[reply]
@SQL: I still plan on running this trial. My apologies I had a major project due this week. I have set aside time this weekend.
With that said I have a question. It has been 8 days since you approved the trial. Does that mean that the trial is now expired, or does it mean 7 days from when I make my first trail edit? If it is indeed expired may I request an extension? Kadane (talk) 18:24, 5 September 2018 (UTC)[reply]
@Kadane: - Just drop a note here when you're starting, and we'll go 7 days from that point. SQLQuery me! 22:03, 5 September 2018 (UTC)[reply]
@SQL: Perfect. I will be starting the trial in about an hour. I will only need today to make the trial edits. The next rounds of notifications that will go out after today will be in 30 days. Kadane (talk) 17:01, 8 September 2018 (UTC)[reply]

Trial complete. - @SQL: - The bot trial is complete, as mentioned above there will not be any edits outside the bot's userspace for a month. There were a total of 5 messages delivered. One mistake was made [1]. The content of the edit was fine, but there was a missing bracket in the edit summary. This edit was made on my User_talk page, so I fixed it and restarted the bot.

All other messages were delivered successfully. You can see an overview of which messages were sent, and which weren't (so far only those requesting monthly updates received a message) at this page. Diff to messages sent [2], [3], [4], [5], [6].

Pinging Tom (LT) as the requester in case they have any comments to add. Kadane (talk) 18:04, 8 September 2018 (UTC)[reply]

That's great, thank you Kadane! One small thing - could you change the part per review that says "(request)" to "(peer review") so it's clearer? --Tom (LT) (talk) 22:52, 8 September 2018 (UTC)[reply]
@Tom (LT): Sure thing, the text in the table has been changed from Article Name (Request) to Article Name (Peer Review). This will be reflected in the upcoming round of messaging next month! Kadane (talk) 01:53, 9 September 2018 (UTC)[reply]
Thanks :)!--Tom (LT) (talk) 02:55, 9 September 2018 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA.