Operator: Noommos ( talk · contribs)
Time filed: 11:25, Saturday May 7, 2011 ( UTC)
Automatic or Manual: Automatic
Programming language(s): PHP
Source code available: On request
Function overview: Trim the list of users eligible for autopatrol down based on set criteria.
Links to relevant discussions (where appropriate): Bot req VPP VPP
Edit period(s): Monthly
Estimated number of pages affected: 2
Exclusion compliant (Y/N): N
Already has a bot flag (Y/N): Y
Function details: Bot will run when the new table is posted each month. It trims the list down according to set criteria and begins submitting them to RFP/A, allowing the administrators working there to deal with them over time. Only edits its own log page, the original table and RFP/A.
I think, rather than post one new request every hour, it would be better to base the number of requests to post by how many are currently on the page (or are currently open?) For example, not add any new requests if there are currently >20 requests, and if there are less, then post 20 - current_number_of_requests. This would prevent flooding the page if there is a period when no admins are reviewing, and would also keep any admins who are looking there busy, rather than giving them one request and then having them think the job is done. - Kingpin 13 ( talk) 02:03, 9 May 2011 (UTC) reply
Added opt-out ( diff) and it is able to submit them now to. The only mistake is it accidentally got confused on MZMcBrides name in the Log page, which is now fixed. Noom talk stalk 17:08, 10 May 2011 (UTC) reply
I'm not sure why this bot is overwriting an existing report. Looking at Editors eligible for Autopatrol privilege ( configuration), either SvickBOT should be updated or NoomBot should post somewhere else. Competing bots are not okay. -- MZMcBride ( talk) 20:50, 14 May 2011 (UTC) reply
I thought the bot was removing blocked users? Why did it add User:Sarah777? - Kingpin 13 ( talk) 22:43, 14 May 2011 (UTC) reply
The bot seems to be running great and has been very helpful. We were manually doing the checks before, so the bot is saving us a lot of work. Thanks very much, Noom. My only suggestion would be to reduce the threshold from 20 open submissions down to 5 or 10 as there are not a lot of people reviewing at RFP/A right now. I believe you have already added the most critical requirements and that bot should continue to run as is. The other suggestions could be added at a later date when you have free time. Thanks. - Hydroxonium ( T• C• V) 02:38, 18 May 2011 (UTC) reply
Trial complete. Have reduced workload threshold, so as to not flood RFP/A. Noom talk stalk 09:47, 18 May 2011 (UTC) reply
Approved. MBisanz talk 03:46, 19 May 2011 (UTC) reply
Operator: Noommos ( talk · contribs)
Time filed: 11:25, Saturday May 7, 2011 ( UTC)
Automatic or Manual: Automatic
Programming language(s): PHP
Source code available: On request
Function overview: Trim the list of users eligible for autopatrol down based on set criteria.
Links to relevant discussions (where appropriate): Bot req VPP VPP
Edit period(s): Monthly
Estimated number of pages affected: 2
Exclusion compliant (Y/N): N
Already has a bot flag (Y/N): Y
Function details: Bot will run when the new table is posted each month. It trims the list down according to set criteria and begins submitting them to RFP/A, allowing the administrators working there to deal with them over time. Only edits its own log page, the original table and RFP/A.
I think, rather than post one new request every hour, it would be better to base the number of requests to post by how many are currently on the page (or are currently open?) For example, not add any new requests if there are currently >20 requests, and if there are less, then post 20 - current_number_of_requests. This would prevent flooding the page if there is a period when no admins are reviewing, and would also keep any admins who are looking there busy, rather than giving them one request and then having them think the job is done. - Kingpin 13 ( talk) 02:03, 9 May 2011 (UTC) reply
Added opt-out ( diff) and it is able to submit them now to. The only mistake is it accidentally got confused on MZMcBrides name in the Log page, which is now fixed. Noom talk stalk 17:08, 10 May 2011 (UTC) reply
I'm not sure why this bot is overwriting an existing report. Looking at Editors eligible for Autopatrol privilege ( configuration), either SvickBOT should be updated or NoomBot should post somewhere else. Competing bots are not okay. -- MZMcBride ( talk) 20:50, 14 May 2011 (UTC) reply
I thought the bot was removing blocked users? Why did it add User:Sarah777? - Kingpin 13 ( talk) 22:43, 14 May 2011 (UTC) reply
The bot seems to be running great and has been very helpful. We were manually doing the checks before, so the bot is saving us a lot of work. Thanks very much, Noom. My only suggestion would be to reduce the threshold from 20 open submissions down to 5 or 10 as there are not a lot of people reviewing at RFP/A right now. I believe you have already added the most critical requirements and that bot should continue to run as is. The other suggestions could be added at a later date when you have free time. Thanks. - Hydroxonium ( T• C• V) 02:38, 18 May 2011 (UTC) reply
Trial complete. Have reduced workload threshold, so as to not flood RFP/A. Noom talk stalk 09:47, 18 May 2011 (UTC) reply
Approved. MBisanz talk 03:46, 19 May 2011 (UTC) reply