Operator: Hasteur ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 01:04, Monday July 29, 2013 ( UTC)
Automatic, Supervised, or Manual: Manual Automatic
Programming language(s): python/pywikipedia, SQLite (for maintaining who has been notified about what article DB)
Source code available: [1]
Function overview: To Traverse Category:AfC_submissions_by_date and it's decendant subcategories (starting with October 2008) to
Links to relevant discussions (where appropriate):
Edit period(s): Edits in driver data batch sets (Year-Month invocations) to prevent any one edit set overflowing the memory heap of the process. Once the Bot has given notice that to a user that there is potential to remove a specific article (Unique Submission-Author key) the bot will not notify again. Initially, bot will be ran by hand and monitored, but once the majority of the backlog of 80 thousand stale AfCs have been notified, bot will transition into a 2x a day automated maintenance process to notify as other pages become eligible. If a category has truly been emptied (no potentially eligible pages ever), configuration of the driver data will be modified to not look at those categories any more.
Estimated number of pages affected: Currently there are 80 declined AfC submissions. So I expect there to be 80 thousand null edits and 80 thousand user page notifications. As new pages become eligible, this number will go progressively up.
Exclusion compliant (Yes/No): Yes, Bot will subscribe to the afd/prod opt outs on user talk pages (though I think that this is a bad idea) using Template:Bots#Python (which i notice doesn't have the opt out logic) and will obey exclusions directed at itself (HasteurBot) globally.
Already has a bot flag (Yes/No): No
Function details: After venting my frustrations regarding the stalled progress on getting Wikipedia:Bots/Requests for approval/HasteurBot approved, @ Technical 13: suggested in IRC, that it might be useful to send out a nudge on the 180 day mark (or after) so that users are aware that CSD:G13 is going to start to be enforced and gives them time to do something about it. This also has the side benefit of starting to populate the Category:G13 eligible AfC submissions category by having all the tempaltes re-evaluated on the null edit.
Depending on the acceptance of this task, I may withdraw the HasteurBot 1 task and re-work it to only nominate submissions where the author has been given 30 days since the bot gave the nudge notice to the author. This gives an editor the 180 days from the last edit to the nudge notice and an extra 30 days after that notice before the bot could take the step of nominating.
Approved for trial (30 (for now) edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Could you include newest expired articles in your trial/initial run, so there is a higher chance the users respond and may be give feedback. Please also use a descriptive summary with links and all, since this is more than likely to deal with new/unexperienced users. Can you also post your message you are posting? If you are using {{ Db-afc-notice}}, I strongly suggest making a bot version for that. Also how are you handling blocked users? (Also, if I forget, since this isn't explicitly mentioned in edit periods, please keep a reasonable edit rate when approved.) — HELLKNOWZ ▎ TALK 21:11, 31 July 2013 (UTC) reply
The task currently says "Manual" (all edits reviewed before made, bot is just an assisted editing tool), but BRFA task 1 for bot is Automatic, how does that work? — HELLKNOWZ ▎ TALK 13:29, 1 August 2013 (UTC) reply
Just to confirm, you do skip the pages with already existing messages about the same draft? Also, why are you using level 3 headings instead of 2? And I wonder why it says "Thank you for your diligence" -- what diligence is that? They left the draft stale, if anything it's the opposite, so saying that is patronizing at best. It's best to be on the safe side with messages to new users. — HELLKNOWZ ▎ TALK 21:19, 1 August 2013 (UTC) reply
[3] - moving categories around from other messages? — HELLKNOWZ ▎ TALK 18:33, 4 August 2013 (UTC) reply
Trial complete.Ok, I seeded in some extra noms/whatnot. Standing by for the first task. I'll add more as we need to. Hasteur ( talk) 02:25, 5 August 2013 (UTC) reply
Approved. Approved as a supplementary/prerequisite task for the BRFA #1. See my full comments there that are applicable to this BRFA as well. Again, a few useful suggestion here that I hope botop will consider implementing, but currently out of this BRFA's scope. — HELLKNOWZ ▎ TALK 18:52, 18 August 2013 (UTC) reply
Operator: Hasteur ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 01:04, Monday July 29, 2013 ( UTC)
Automatic, Supervised, or Manual: Manual Automatic
Programming language(s): python/pywikipedia, SQLite (for maintaining who has been notified about what article DB)
Source code available: [1]
Function overview: To Traverse Category:AfC_submissions_by_date and it's decendant subcategories (starting with October 2008) to
Links to relevant discussions (where appropriate):
Edit period(s): Edits in driver data batch sets (Year-Month invocations) to prevent any one edit set overflowing the memory heap of the process. Once the Bot has given notice that to a user that there is potential to remove a specific article (Unique Submission-Author key) the bot will not notify again. Initially, bot will be ran by hand and monitored, but once the majority of the backlog of 80 thousand stale AfCs have been notified, bot will transition into a 2x a day automated maintenance process to notify as other pages become eligible. If a category has truly been emptied (no potentially eligible pages ever), configuration of the driver data will be modified to not look at those categories any more.
Estimated number of pages affected: Currently there are 80 declined AfC submissions. So I expect there to be 80 thousand null edits and 80 thousand user page notifications. As new pages become eligible, this number will go progressively up.
Exclusion compliant (Yes/No): Yes, Bot will subscribe to the afd/prod opt outs on user talk pages (though I think that this is a bad idea) using Template:Bots#Python (which i notice doesn't have the opt out logic) and will obey exclusions directed at itself (HasteurBot) globally.
Already has a bot flag (Yes/No): No
Function details: After venting my frustrations regarding the stalled progress on getting Wikipedia:Bots/Requests for approval/HasteurBot approved, @ Technical 13: suggested in IRC, that it might be useful to send out a nudge on the 180 day mark (or after) so that users are aware that CSD:G13 is going to start to be enforced and gives them time to do something about it. This also has the side benefit of starting to populate the Category:G13 eligible AfC submissions category by having all the tempaltes re-evaluated on the null edit.
Depending on the acceptance of this task, I may withdraw the HasteurBot 1 task and re-work it to only nominate submissions where the author has been given 30 days since the bot gave the nudge notice to the author. This gives an editor the 180 days from the last edit to the nudge notice and an extra 30 days after that notice before the bot could take the step of nominating.
Approved for trial (30 (for now) edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Could you include newest expired articles in your trial/initial run, so there is a higher chance the users respond and may be give feedback. Please also use a descriptive summary with links and all, since this is more than likely to deal with new/unexperienced users. Can you also post your message you are posting? If you are using {{ Db-afc-notice}}, I strongly suggest making a bot version for that. Also how are you handling blocked users? (Also, if I forget, since this isn't explicitly mentioned in edit periods, please keep a reasonable edit rate when approved.) — HELLKNOWZ ▎ TALK 21:11, 31 July 2013 (UTC) reply
The task currently says "Manual" (all edits reviewed before made, bot is just an assisted editing tool), but BRFA task 1 for bot is Automatic, how does that work? — HELLKNOWZ ▎ TALK 13:29, 1 August 2013 (UTC) reply
Just to confirm, you do skip the pages with already existing messages about the same draft? Also, why are you using level 3 headings instead of 2? And I wonder why it says "Thank you for your diligence" -- what diligence is that? They left the draft stale, if anything it's the opposite, so saying that is patronizing at best. It's best to be on the safe side with messages to new users. — HELLKNOWZ ▎ TALK 21:19, 1 August 2013 (UTC) reply
[3] - moving categories around from other messages? — HELLKNOWZ ▎ TALK 18:33, 4 August 2013 (UTC) reply
Trial complete.Ok, I seeded in some extra noms/whatnot. Standing by for the first task. I'll add more as we need to. Hasteur ( talk) 02:25, 5 August 2013 (UTC) reply
Approved. Approved as a supplementary/prerequisite task for the BRFA #1. See my full comments there that are applicable to this BRFA as well. Again, a few useful suggestion here that I hope botop will consider implementing, but currently out of this BRFA's scope. — HELLKNOWZ ▎ TALK 18:52, 18 August 2013 (UTC) reply