Warning Please do not post any new comments on this page.
This is a discussion archive collecting requests for restricted access by TalBot.
See current discussion or the archives index.

2006-12 admin

For the sake of archival, the bundled nomination has been duplicated for each user.

This is a bundled self-nomination. The first applicant is the bot of the second applicant.

By request, I'm planning to do soft redirect maintenance using the pywikipedia script User:TalBot/rm-soft-redir.py. This involves the deletion of hundreds of pages, so a bot with sysop privileges is needed. The script was tested in several dry runs directly on Wikisource. The log of the run on Category:Soft redirects/September 2006 is available at User:TalBot/rm-soft-redir.py/test.log (943kb).

TalBot is active since October 2006 and was granted official bot status about a month later. It has since run and completed several tasks, making thousands of automated edits and page moves in the process.

I (GrafZahl) am active since June 2006. At the moment, most of my Wikisource time flows into operating and maintaining TalBot and writing bot scripts for users requesting tasks, but occasionally I work a little on some of James Clerk Maxwell's works or scan some pages from a book. A bot operator sometimes has to clean up after the bot, and with a sysop bot, this might require sysop rights. Otherwise, I missed the admin buttons very little. But it seems natural that the amount of community trust granted to the bot operator should never be smaller than the amount granted the bot.

I'd like to ask for a single vote for the both of us, because there is not much point in giving sysop rights to only one of us.

Lastly, I should point out the alternative of giving the bot of an established administrator sysop rights and let it run the script. This might slow down things very slightly due to the additional communications channel incurred, but is otherwise just as good.

--GrafZahl 14:58, 15 December 2006 (UTC)[reply]

  • Support both. GrafZahl has been a strong contributor since early June and has demonstrated a skill in programming that makes them an ideal choice for running an administrative bot. Their messages on various talk pages show unfailing politeness and helpfulness, qualities every administrator should have. —{admin} Pathoschild 19:35, 16 December 2006 (UTC)

2008-02 confirmation

Unanimously kept. —{admin} Pathoschild 09:44:12, 29 February 2008 (UTC)

2009-03 confirmation

Administrator since 26 December 2006 by unanimous election (see previous discussions), currently active (contributions · logs · count · crossactivity). GrafZahl will be reconfirmed automatically unless at least three established users oppose, which will trigger a vote of confidence with decision by simple majority.

Unanimously kept. Jude (talk) 07:08, 5 April 2009 (UTC)[reply]

2010-05 confirmation

Bot; Administrator since December 2006 (see previous discussions), currently active (contributions · logs · count · crossactivity). TalBot will be reconfirmed automatically unless at least three established users oppose, which will trigger a vote of confidence with decision by simple majority.

2011-05 confirmation

Confirmed. See Wikisource:Administrators/Archives/GrafZahl#2011-05 confirmationbillinghurst sDrewth 13:03, 2 June 2011 (UTC)[reply]