Wikipedia:Bots/Requests for approval/Tigraan-testbot
- 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: Tigraan (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 17:57, Sunday, June 25, 2017 (
Automatic, Supervised, or Manual: Supervised or Manual
Programming language(s): Python 3
Source code available: Github
Function overview: Notifies the original poster (OP) of a Wikipedia:Teahouse thread that was archived by lowercase sigmabot III.
Links to relevant discussions (where appropriate): Wikipedia_talk:Teahouse/Archive_14#Special_archival_bot_that_notifies_new_users (which itself followed a suggestion from earlier in Wikipedia_talk:Teahouse/Archive_14#Teahouse_archiving) establishes the basic consensus for the bot. In a follow-up we came to a consensus to notify every non-blocked user, even IP editors and editors will lots of edits / advanced userrights.
Edit period(s): Daily
Estimated number of pages affected: ~20/day (depends on the traffic at Wikipedia:Teahouse)
Namespace(s): User talk pages exclusively, except maybe a dedicated logging page in the bot's userspace.
Exclusion compliant (Yes/No): Yes (posting is done by Pywikibot, which obeys it).
Function details: The bot parses the page history of
You may take a look at User_talk:Tigraan-testbot/THA_log which is where the notifications went in my last testing phase before coming here (I used test.wikipedia before but I could not substitute the template there). add_text's always
flag is currently off which makes it ask for confirmation before each edit, but I would prefer to run it supervised (flag on).
The endgame plan is to merge the functionality into HostBot's codebase (maintainer Jtmorgan) and run it as a cron job. (EDIT 18:07, 25 June 2017 (UTC): just to be clear, the idea is to run the task supervised or manual under Tigraan-testbot for a trial period, and if all is well to convert it to a HostBot task.)[reply]
Discussion
- Regarding this config file-related concern, have you tried putting the configuration file in your home directory (specifically, $HOME/.pywikibot on Mac/Linux and %HOME%\.pywikibot on Windows)? Enterprisey (talk!) 03:36, 27 June 2017 (UTC)[reply]
- I tried a lot of things, but not that particular one - I will give it a shot before running the trial. Thanks for the tip. (I am not a fantastic Python coder, and I did not find PWB's manual pages very clear, to be frank). TigraanClick here to contact me 11:34, 27 June 2017 (UTC)[reply]
- It worked, yay! Thanks. TigraanClick here to contact me 19:58, 27 June 2017 (UTC)[reply]
- I tried a lot of things, but not that particular one - I will give it a shot before running the trial. Thanks for the tip. (I am not a fantastic Python coder, and I did not find PWB's manual pages very clear, to be frank). TigraanClick here to contact me 11:34, 27 June 2017 (UTC)[reply]
- Approved for trial (50 edits or 5 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. — xaosflux Talk 03:59, 27 June 2017 (UTC)[reply]
Probably too much detail of how the test run went. Will post a summary once over. TigraanClick here to contact me 22:48, 30 June 2017 (UTC)[reply]
|
---|
|
Trial complete. I failed at counting before running the last test and the bot made a total of 51 edits - I apologize for that. The bot did not make any erroneous notifications or exaggerated resource requests during the trial that I am aware of. I changed the codebase slightly during testing, in order to:
- remove leading and trailing spaces when matching thread names
- query the full revisions of the last 10 days at Wikipedia:Teahouse via mw:API:Revisions'
rvcontinue
parameter - change the edit summary left by the bot
I believe the bot is good to go technically. TigraanClick here to contact me 14:23, 2 July 2017 (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.