Wikipedia talk:Bot Approvals Group/Archive 4

message: Hi! I've tested a few changes, and wanted to propose that we make them permanent:
*I've removed all the transclusions and trials from the BRFA page and replaced them with usages of . There is no visual effect, however it means less typing when we move stuff around.
*I'd also like to switch the way we archive old requests: expired, withdrawn, or denied would go to the same place, only using this template, for simplicity. That would work like this:



*And I'd like to change the way we archive completed requests to use the same template using either Approved or Already Flagged. From there, if necessary, a crat would change the status to Flagged, and it would automatically show the link to the log.
There are no visible changes, instead, it makes clerking easier. Any problems with this? --ST47Talk·Desk 13:11, 27 July 2007 (UTC)
replies: text: I like it.  Mucho.  I assume that the bot name is still case-sensitive, so the bot doesn't croak?  And that /Approved is still its own subpage, so bureaucrats can watch it?  — Madman bum and angel (talk – desk) 13:43, 27 July 2007 (UTC)
replies: text: Yes and yes. :) --ST47Talk·Desk 13:52, 27 July 2007 (UTC)

text: We can subst them once they are flagged? --ST47Talk·Desk 19:18, 27 July 2007 (UTC)
replies: text: Sure.  — Madman bum and angel (talk – desk) 19:22, 27 July 2007 (UTC)
replies: text: Heh.  Clearly not.  Subst:ed ParserFunctions != good. — Madman bum and angel (talk – desk) 19:28, 27 July 2007 (UTC)
replies: text: No, add subst: to the start of the parserfunctions. Problem=solved. Matt/TheFearow (Talk) (Contribs) (Bot) 21:52, 27 July 2007 (UTC)
replies: text: ... you can't do that.  You'd save the template, it would be evaluated with all parameters' default values, and then there would be no more parser functions.  — Madman bum and angel (talk – desk) 22:49, 27 July 2007 (UTC)
replies: text: No, the includeonly bits mean it only substs it when you subst the template. It works great. Matt/TheFearow (Talk) (Contribs) (Bot) 05:14, 28 July 2007 (UTC)
replies: text: Doesn't seem to for me.  User:Madman bum and angel/Sandbox 3.  Since the whole thing's includeonly, if you subst: the ParserFunctions, you get this.  And if you remove the containing  and just  the subst:s, that sandbox is what you get – the parser doesn't work that way.  — Madman bum and angel (talk – desk) 17:23, 28 July 2007 (UTC)
thread_title:  Conversion of Templates 

message: TheFearow was rejected when he applied for membership, I would like instead of trying to ignore the community consensus that TheFearow apply by a standard discussion instead of the trial method. ∆ 05:59, 1 August 2007 (UTC)
replies: text: If BAG can just decide to reapply the old method whenever, what's the point? Andre (talk) 06:04, 1 August 2007 (UTC)

text: There was a strong opposition against TheFearow joining,  Please remove TheFearow from the list. ∆ 06:07, 1 August 2007 (UTC)
replies: text: If I have done anything wrong as a member of BAG, please point it out. All my actions have been appropriate (I believe), and I have not been objected to (in this period). I see no issues with this current setup, but if a current member of BAG that has been a member before the beginning of the trial believes I should be removed, I will resign and re-apply under the old method. Matt/TheFearow (Talk) (Contribs) (Bot) 06:33, 1 August 2007 (UTC)
replies: text: I don't think that TheFearow needs to be removed from the list.  He has done a fine job so far, and has helped to quicken the bot approvals rate tremendously over the past couple of days. —METS501 (talk) 12:21, 1 August 2007 (UTC)

text: Normally I'd agree with you, Beta, in regards to any user that was previously rejected for a position then assuming that position and being automatically accepted due to a change in policy.  However, I haven't seen any major problems; the only thing that came close was this, and per discussion on IRC, I don't think that will happen again.  I think it's been pretty clear that this is a trial and that things may change dramatically, for better or for worse; things like this are just a part of it.  I gave my moral support above and I think he still deserves it.  — Madman bum and angel (talk – desk) 14:27, 1 August 2007 (UTC)
replies: text: Beta, I will resign if you can point out somewhere where I have messed up, and another user (anyone, doesn't have to be BAG) agrees that it was out of line. Unless that happened, I believe I have helped, so I am staying for now. Matt/TheFearow (Talk) (Contribs) (Bot) 21:25, 1 August 2007 (UTC)
thread_title:  Issue 

message: Per the discussion above (Wikipedia talk:Bots/Approvals group#Issue), would people recommend I offically request to join under the "old" system? I'm reasonably confident I would pass, but is this necessary/recommended? Matt/TheFearow (Talk) (Contribs) (Bot) 04:16, 3 August 2007 (UTC)
replies: text: I don't know, it's awfully soon since the last request, but you have been contributing to BRFAs, so it's up to you.  I'd still support, for the record. —METS501 (talk) 04:40, 3 August 2007 (UTC)
replies: text: Since I have done a lot of work for BRFA and as a member of BAG, I can't see me getting a huge amount of opposition, but i'm wondering whether I should officially run or stay as a member under the trial. Matt/TheFearow (Talk) (Contribs) (Bot) 04:49, 3 August 2007 (UTC)
replies: text: Why don't we just wait and see how the trial goes?  If more than one person calls for a reconfirmation, then perhaps you should do that.  — Madman bum and angel (talk – desk) 05:26, 3 August 2007 (UTC)
replies: text: Ok, i'm going to do that. Matt/TheFearow (Talk) (Contribs) (Bot) 09:53, 3 August 2007 (UTC)
thread_title:  Confirmation 

message: Per the CleanupBot BRFA, which I just denied, I have stated the following:
In future, any requests from you should include: source code, exact regex patterns and/or information on the matching algorithms. If using pywikipedia, pywikipedia module names/commands, or a package such as AWB, details on the settings should be given. Any request by you not meeting these criteria can be denied by 'any' user if the information is not presented within an hour of posting the BRFA. It wastes time if you refuse to give any details or even comment giving an idea of the timeframe until such information is available.
I wanted to post here so people notice this, and for any objections/etc to be raised. It was wasting time, and they have posted 4 denied bot requests, each time providing no information and almost always answering none of the questions. Criticisms/comments? Matt/TheFearow (Talk) (Contribs) (Bot) 08:27, 9 August 2007 (UTC)
replies: text: Well, something had to be done, and that's not bad.  Especially since he's moved on to WP:BOTREQ.  — madman bum and angel 16:11, 9 August 2007 (UTC)
replies: text: It was either that or warning for disruption - except I hate giving warnings or doing anything to cause a block of a good faith user. Matt/TheFearow (Talk) (Contribs) (Bot) 21:25, 9 August 2007 (UTC)
thread_title:  {{user|PNiddy}} 

message: Hey.
Just so you know, Betacommand is a 'special' person insofar that he has old BRFAs that ArbCom invalidated, so he's using '/BetacommandBot Task \d' - this doesn't affect the template negatively.
Additionally, both relevant to beta and other users, the standard form: If a user is an established bot operator, it's probably OK to bypass most of that as long as there is ample description: We don't need to know the language, the bot probably has a flag and an established edit rate, and such, the only important part is really . --ST47Talk·Desk 23:33, 12 August 2007 (UTC)
replies: text: I disagree with the form - it takes seconds to fill out and is a much easier way of seeing the information, especially if it's on another page and/or doesnt give info on certain things like editrate. If they say all the information (or even just a basic summary) on that page, it isn't a huge problem, but it still can be a little annoying. Matt/TheFearow (Talk) (Contribs) (Bot) 23:41, 12 August 2007 (UTC)
replies: text: I agree with TheFearow: the form is very quick and things like edit rate and language are crucial.  Keep in mind, the language can change for different tasks (for example, I have different tasks coded for my bot in python, C#, and AWB. —METS501 (talk) 01:53, 13 August 2007 (UTC)
replies: text: Maybe we need a new rule at the top of the BRFA page, stating that requests that do not use the proper form will be removed or denied? It would make everyone use the form, and almost everyone would follow it, so it wouldn't affect too many BRFA's. Matt/TheFearow (Talk) (Contribs) (Bot) 02:05, 13 August 2007 (UTC)
replies: text: I disagree with that.  New users basically always use the template anyway, and it will just seem like we're being a dick to the established users.  Should it be mandatory, yes, but mandatory without punishment. —METS501 (talk) 02:17, 13 August 2007 (UTC)

text: Matt, I would suggest that you go back and read the MFD where a group of users suggested disbanding the BAG.  I think that you will find that such a punitive process is the exact type of thing that concerned many of the delete voters. --After Midnight 0001 03:17, 13 August 2007 (UTC)
replies: text: Sorry, it seems you misunderstood me, I meant that it is removed/denied if they do not use the template, but to state that if they recreate it using the template it can continue. By removing (my preferred option), I meant un-transcluding, or we could just not continue to trial or such without it? I didn't mean punishment, I just meant halting the process until the template is used. Matt/TheFearow (Talk) (Contribs) (Bot) 03:25, 13 August 2007 (UTC)
replies: text: Yeah, but IMHO I still think it's more trouble than it's worth. —METS501 (talk) 04:33, 13 August 2007 (UTC)
replies: text: The template is useful for documenting bots, but should not be a "requirement" to get the information needed to approve bot operations.  We've approved plenty of bots without it before.  From a standards approach, it should be encouraged though, but bot operators should not be bitten for not using it.  The original purpose of the template was so that the recurring questions that were asked of every request would be pre-answered.  I do disagree that User:Betacommand is exempt from something by virtue of being "special", but he is a knowledgable bot operator and deserves some slack based on that. — xaosflux Talk 05:18, 13 August 2007 (UTC)

text: Halting a bot request, even temporarily, for such a minor issue is just punitive.  As long as the request for approval has all the information we need (edit rate requested, programming language, etc.), it's fine.  In this case, Betacommand's request did not have that information.  — madman bum and angel 13:04, 13 August 2007 (UTC)
replies: text: In all the cases I have seen where they have not used the form, several peices of information have not been provided. With the form, it reminds them to fill it all out. I do agree that it should not be halted if they dont use the form but provide all the necessary information on the BRFA, however I have always seen important information missed out when the form is not used. Matt/TheFearow (Talk) (Contribs) (Bot) 22:54, 16 August 2007 (UTC)
thread_title:  Betacommand 

message: :From my analysis of ST47's message above, I interpret his general concern that there are a lot of fully-qualified people who could and should be more involved with the bot approvals process in a more substantial way. However, they are discouraged by the fact that entry into this "approvals group" is too bureaucratic, which causes the other issues (lack of speed, lack of community involvement). For example, I could ask to join and help out analysing whether a bot should run and if it a) meets the bot policy and b) will enjoy the support of and improve the community. This is what I do every day when I close deletion discussions as an administrator, and block users. However, I would probably be rejected into this "approvals group" if I nominated myself, hence the concern about bureaucracy.
:I appreciate why you should regulate who can approve bots - not doing so can lead to bad decisions and possible harm, especially if any new user can join, possibly even a single-purpose sockpuppet of the person requesting a bot to approve it. However, I have no doubt that anyone who displays some technical knowledge in this area (ie. to understand at least the basics of how bots affect and benefit Wikipedia), have some experience on Wikipedia, and do not lack the community's trust (note lacking it: not having proven trust, ie. RfA, but rather not having it disproved), would be a benefit to improving the approvals process. However, with the current setup, they can do nothing really, because they lack the centred 'governing power', so to speak, to actually approve bots.
:I could nominate myself to join the BAG right now. What do I have going for me? I have a Toolserver account and am currently developing a number of bots for primarily Wikinews and possibly one for here as well. I am very active on Wikipedia, and enjoy the bare minimum of community trust that someone should to approve bots (in my opinion). However, I would fail in any bid to join the approvals group because I have barely participated in approvals prior. That isn't to say that I couldn't go any worse of a job than those currently in the group. And I wouldn't consider my lack of participation all my own fault - the current structure of the bot approvals process makes it very difficult to prove a persons' worth as an approvals member.
:What I propose is this: allow any user which is experienced on Wikipedia and has at least some knowledge of bots on Wikipedia, whether evidenced by contributing to the approvals process before or not, can add their name to the list at WP:BAG. They can then do everything a BAG member can at the moment, and if they do it properly, fantastic, another positive effect on the approvals process. If they screw it up continually, show ineptitude, or have a drastic lack of community trust, then bring the issue up on this page and we can discuss it then. In this kind of situation, being reactive is better than proactive, because the exclusion factor amounts to a negative net effect on this process.
:The question you ask: why should you believe/listen to me? What would I know? Well, I encountered a similar problem with clerking, and the best result was to adopt a policy like the above mentioned for both the process and to keep the peace. I fear that if the BAG doesn't change its' ways sooner rather than later, it will end back up at MfD, as has been noted on at least one noticeboard in the last couple of days. 
:When I was in your position with the clerking issue, my first reaction was to raise my hands in the air and run around screaming. I wasn't the only one. However, as the discussions developed at Wikipedia:Community sanction noticeboard/Archive3 and Wikipedia:Bureaucrats' noticeboard/Archive 6, the arguments put forward to adopt a more open system were fundamentally better than those against change. I see distinct parallels between the clerks and the BAG, and I urge all members of the BAG and the community to comment and discuss any possible options to altering the way approvals for bots are handled. I would prefer to see changes at this level rather than an MfD which causes resistance and heavier disruption. I'm sure we all would prefer that, for that matter.
::Daniel 10:42, 20 July 2007 (UTC)
replies: text: That is what I believe BRFA should be. There should be some requirements, such as having contributed to at least 2 BRFA's and having over 200 edits, which are both reasonable and important for someone in trust, but apart from that everything seems good. I would definately support a method like that. Matt/TheFearow (Talk) (Contribs) (Bot) 10:53, 20 July 2007 (UTC)
replies: text: Rather than putting a numerical thing on it, there should be a message saying how you must have at least some substantial experience with Wikipedia as well as understand the bot policy and how BRFA works. Other than that, a simple caution to compliment the common sense idea that "proceed slowly at the start of your time giving assistance to the approvals process", and extend an invitation to new users to possibly join an IRC channel or email/other contact methods to hone their skills in helping out approving bots. But that's just me. Daniel 11:00, 20 July 2007 (UTC)

text: There should still be some sort of list so random users with no bot knowledge won't approve bots. ~ Wikihermit 14:22, 22 July 2007 (UTC)
replies: text: Yes. However, getting your name on this list was the cause for concern. Daniel 01:39, 23 July 2007 (UTC)
replies: text: A simple approval process, simply requiring an admin or existing BAG member to say yes, no big process. That would be ideal. It means people with bot knowledge can get in, but people who know nothing about it will likely not get approved. Matt/TheFearow (Talk) (Contribs) (Bot) 01:46, 23 July 2007 (UTC)
replies: text: That sounds like a great idea. If issues do come about, and a user is becoming disruptive whilst on "the list", then we hold a discussion, and consensus will determine what happens.  Daniel 02:03, 23 July 2007 (UTC)

text: I would really like to hear some input from current Group members about the merits of this proposal. Cheers, Daniel 11:11, 25 July 2007 (UTC)
replies: text: This would be fine. We'd need to keep the list, and there should be some oversight, at least that you must run a bot and have programming experience, but if we do that I don't see a problem. --ST47Talk·Desk 14:33, 25 July 2007 (UTC)
replies: text: Why would they need programming experience? Often we as programmers see things in one way, and the insight of non-programmers is incredibly useful. They already comment on BRFA's - having them able to do it officially as BAG and/or approve trials/etc would be a benefit. Matt/TheFearow (Talk) (Contribs) (Bot) 03:51, 26 July 2007 (UTC)
replies: text: Programmers know if an automated task is feasible or not (e.g., when it's clearly impossible for a non-human entity to account for all of the human factors it may encounter), when there's potential for an automated task to overstep its bounds (e.g., if regular expressions could be too greedy in some situations, or when there's a logic error in a conditional loop), among other things.  They are the most qualified to comment on automated tasks because they are very familiar with the method of automation.  I think that what you want non-programmers to do (e.g., commenting on whether a task would benefit the project or not, if there may be interference with other concurrently-running bot tasks, or if another WikiProject may need to comment first, etc.), they already can do by engaging in discussion of BRFAs as has always been promoted.  But the final decision on whether a piece of code making edits at superhuman speeds should be unleashed on Wikipedia should be that of those who understand the piece of code.  — Madman bum and angel (talk – desk) 05:45, 26 July 2007 (UTC)
replies: text: Indeed, we still need a list of some sorts, and you need some experience with bots on Wikipedia. Not exactly programming in eight different e-languages, but a solid grounding of bot policy and use on Wikipedia. Plus the generic urge for people to take it slow at the start, etc. Again, more comments appreciated. Daniel 06:31, 26 July 2007 (UTC)
replies: text: Well in that case, why not just let any admin be a member of BAG? One would expect all admins to either know of bot policy or know how to look it up. --kingboyk 13:31, 27 July 2007 (UTC)
replies: text: That's the idea of the proposal... Daniel 13:52, 27 July 2007 (UTC)
replies: text: Let's give it a trial run then. --kingboyk 14:08, 27 July 2007 (UTC)

text: Does there?  I think the analogy to CHU and RFCU clerking is an excellent one, and that's what I, for one, would really like to see.  Sure, you can add yourself; just keep in mind that it's an extra responsibility, usually a dull one, and it's not a position of prestige.  If you seem inactive, you can be removed; if another BAG member continually has to correct you on procedural or technical details, you're not being useful.  If you're disrupting the procedure or apparently not well versed in policy, you can be asked to remove yourself and come back some other time.  — Madman bum and angel (talk – desk) 17:41, 26 July 2007 (UTC)
replies: text: Indeed. Pending no further word against this proposal (and the support for it), I'll reword and deprotect (leave at semi-protection) the BAG page so that this system can be adopted (I'll include cautions about starting off slowly, not approving your own bots, understanding of the bot policy etc.). If you object, please speak up within the next 48 hours so that we can discuss and modify as appropriate. Cheers, Daniel 04:13, 27 July 2007 (UTC)
replies: text: Well hold on, are you proposing that anybody can add themselves to the group or are you proposing extending BAG membership to all admins? They're quite different. Already anybody can comment on bot applications; there has to be somebody with some authority to close the debates. Also, remember, this is actually a bureacrat task that is delegated to BAG; delegating it to all admins is fine, but to everybody? no. I couldn't support that. We may as well just close down bot approvals altogether; at least then there would be no "bureacracy". --kingboyk 14:22, 27 July 2007 (UTC)
replies: text: Extending to bot operators with programming experience and BRFA experience, who may add themselves at will to the list, however they can be removed if they don't have experience with bots or if they need to be corrected constantly. --ST47Talk·Desk 14:30, 27 July 2007 (UTC)
replies: text: Alright. Let's see how it goes. I'll suggest to User:Reedy Boy that he sign up (admin, bot op, AWB dev); if other folks can suggest to some suitable candidates that they sign up too it will give us a more useful test. --kingboyk 15:00, 27 July 2007 (UTC)
replies: text: Very nice choice.  :) — Madman bum and angel (talk – desk) 15:07, 27 July 2007 (UTC)

text: Not bad, but I have a question. What happens if somebody is removed involuntarily? What recourse do they have? --kingboyk 14:48, 27 July 2007 (UTC)
replies: text: I expect it's much like CHU and RFCU clerking, after which this proposal has been modeled.  You don't really have a recourse except to take a break, review bot policy, then return if you'd like.  Re-adding your own name immediately would not be useful and would probably be seen as disruptive.  It's expected that you'll comply with the more experienced members of the Group, and it not, dispute resolution may be in order.  For the record, I've not seen such a dispute occur over clerking.  — Madman bum and angel (talk – desk) 14:59, 27 July 2007 (UTC)
replies: text: Righto. I'm happy with that; let the trial commence! --kingboyk 15:08, 27 July 2007 (UTC)
thread_title: Second proposal

message: I'm slightly concerned about what could happen with this.  Certainly, parallels can be drawn to the clerking procedure, but the community has given the BAG more power than clerks have - that is, the power to approve or reject bot approvals.  As it was, nothing (absolutely nothing) stopped a user from commenting on BRFAs for a period of time at their leisure, much like people can comment on AfDs at their leisure.  It then came down to the BAG member to approve/reject/order a trial on a bot, using the comments made as a guide.  However, there is no doubt that managing (or commenting on) BRFAs is, frankly, mind numbingly boring.  Hence someone will comment for a while, and realise that if they were to get onto the BAG, they'd have to do a hell of a lot more of this - ultimately, they decide that they don't want to, and they stop.
That is where the problem lies - a lack of participation.  This isn't caused by some sort of perceived bureaucracy - we have far less of that than the ArbComm does, retaining its fairly closed body of clerks (with no nomination system open to become a member) and keeping the willing contributor out.  If you look at the text removed in this diff (provided to me by Daniel on IRC in a totally unrelated matter!), you will see a comment which effectively says that some parts of Wikipedia, for various reasons, can't be as open as others.  These reasons including there being set procedures to follow and/or a requirement for some sort of expertise.  By making BAG a relative "free for all", we remove any and all standards that we can reasonably expect the community to hold us to.
I'm all for increased participation in the BAG, but fear that this format can only cause problems with incorrectly approved bots, ultimately leading to further calls for the dissolution of the BAG (and for the record, threats of MFD can be safely ignored, as it seems, from the deletion attempts on the AMA, that groups cannot be nominated for deletion).
So, I've said that BAG has more powers than clerks.  I don't think that anyone could argue on this point, or on the point that an incorrectly approved bot can do a massive deal of harm.  Contrary to apparent belief, approving bots isn't as simple as looking at the approval, thinking "that looks good", and making the edits to approve.  No - a member of the BAG has to check the background of the user (ie, we don't want to give a user who doesn't meet the minimum edit threshold for using AWB to be given the ability to run an AWB bot); we need to check that the proposal is clearly supported by the community via relevant Wikiprojects; we need to have an excellent knowledge of Wikipedia policy and of the "unwritten rules", so that we can avoid upsetting people by approving a well meaning, but unwelcome bot.  Finally, we need to have the technical skills to pick apart a request.  If someone comes to BRFA asking for approval for an anti-vandalism bot using AWB, the alarm bells have to start ringing.  This sort of task cannot be done with AWB, so it become clear that the requesting user either hasn't done his research, or is up to no good (both are valid - we've had a couple fo requests from Molag Bal socks).  Having an open group, people will use BAG as a stepping stone to adminstratorship, and then leave when they get the shiny new buttons.  We don't want that.
OK - I've complained enough now!  So what is a workable solution?  Well, first off, there needs to be some oversight of prospective members, whether this be a vote or a simple empowerment of someone ('crats? consensus of the BAG?) to remove someone forcibly.  As it is, I feel that there is nothing wrong with our current voting system, as long as it is publicised.  I say this on every request I see - "please leave messages on the appropriate noticeboards", followed by a long line of alphabet soup indicating the appropriate noticeboards.  I also suggest a notice at the top of WP:BRFA.  A (perhaps valid) complaint about BAG is that it's cabalish.  We need to give the community every opportunity to vote for someone, and that means leaving nominations open for their full course.  We don't differentiate between BAG and non-BAG opinion either, which makes us significantly more open that the MedCom.  People just need to remember to advertise the fact that a vote is ongoing.
Community trust does need to be proven - not, as has been suggested above, a lack of it.  BAG is the, effectively, the ultimate authority on bot approval matters on Wikipedia, having had this role devolved to them by the 'crats.  There should be just three absolute requisites for membership of the BAG - community trust, technical expertise and experience around BRFA.  The first needs to be proven by a voting period of sorts, and the second and third need confirming by a vote.  All three are really quite easy to attain - it is by no means difficult to get onto the BAG, as the current nomination is showing.  
So, congratulations if you've read all of that (and if not, please do so - it took me some time to write, so please show me the courtesy :))!  That's my position on BAG membership - as for the approvals themselves, I do have another opinion (that a voting section, as seen on other wikis, would be good), but that can be brought up when the discussion swings back that way.  Thanks, Martinp23 15:57, 28 July 2007 (UTC)
replies: text: Hmmm.  Well, I'm going to mull over your argument for a little bit longer, as I do see many valid points in it.  But let me just comment for the time being that in regards to your workable solution, it's already been established that consensus of the BAG or a bureaucrat can forcibly remove a member, either because he is disrupting the process or because he is not qualified.  This sets us apart from CHU and RFCU clerks; we do have a specialized body, and we're taking that into account in this proposal.  I've been under no impression that bot approval is easy, and I assumed that many of the tasks you specified above were executed by the BRFA.  Perhaps, though, we should  make it clear to new members what exactly they're signing on to do?  Iron out that procedure a bit?  Just a couple thoughts.  :) — Madman bum and angel (talk – desk) 17:16, 28 July 2007 (UTC)
replies: text: We don't actually have any way to remove users.  Betacommand was only removed after a load of argument on this page, and there is no procedure set up - that was all a very informal affair, and relied heavily on the ArbComm ruling.  I think that it would be better, in any case, to avoid the situation in which we may need to remove a user in the first place.  Comments will always come in that any sort of voting process is broken (*points to RfA*), generally after a number of (high profile?) failures.  Then, there'll be a load of successful nominations and we'll think "hey - all that argument about changes was pointless!".  It's never-ending cycle ;) Martinp23 18:24, 28 July 2007 (UTC)
replies: text: Betacommand was removed prior to the ArbCom decision. --kingboyk 12:17, 29 July 2007 (UTC)

text: Oh.  I thought you were commenting on the reform proposal, which does indeed provide that users may be removed.  Perhaps you should see the notice at the top of WP:BAG, which ST47 posted, and represents the implementation of the proposal in a nutshell, as far as I can see. — Madman bum and angel (talk – desk) 18:49, 28 July 2007 (UTC)
replies: text: According to the BAG page, "Users who are not qualified or who consistently need to be corrected may be removed at any time by consensus of existing members or any bureaucrat". Does that address your concern? Basically, either the BAG discuss a person here and if the consensus is to remove, that user is removed. If a bureaucrat removes them, that's fine, we gave them the keys because we trust them. Daniel 00:15, 29 July 2007 (UTC)
replies: text: There needs to be some oversight prior to joining.  The community has vested its faith in us to handle bot requests properly - the least we can do is make sure that competent people are doing the job. Martinp23 02:20, 29 July 2007 (UTC)
thread_title:  Section break 

message: I've had a look through WP:BAG and WP:BRFA now, having returned from my holiday.  What I saw does not amuse me.  Of the several editors who have joined under the open scheme, only a tiny proportion (<1/2, iirc) have any significant edits to BRFAs.  I was tempted to take a pair of hedge-trimmers to the list, but then remembered about this proposal.
For those who have been active members of BAG through this trial period, I can't see why you won't be able to get on under this system, especially as you have "work experience" under your belt to point at and be proud of.  For others: this shouldn't pose any significant barrier to you joining, and will in fact enrich your experience (!) by letting you know whether you'd enjoy working on BAG, and giving you a chance to get into a routine of making sustained contributions to BRFAs.  A problem I've noted while looking at WP:BAG is that people have signed up thinking "I might comment, one day" - we don't want that, and giving them a week of time being "watched" prior to joining will make these people think twice.  
Please raise any objections/ideas regarding this proposition - I propose bringing it in to force fairly soon (tomorrow?) if no one has major problems. Martinp23 22:53, 26 August 2007 (UTC)
replies: text: I don't see any major problems.  This seems to have encouraged some of our editors who would be good BAGgers to contribute to BRFAs, which in turn gains them easy acceptance to the BAG.  — madman bum and angel 06:07, 27 August 2007 (UTC)
thread_title:  Further discussion 

message: Hi! Just an advisiory, I've changed the configuration of my interwiki bot to use the account User:STBot rather than User:STBotD. Both accounts are flagged, and I've made a note on the original request and userpages. This change is due to my use of STBot on other wikis and the upcoming SUL change. --ST47Talk·Desk 15:51, 16 August 2007 (UTC)
thread_title:  Change in bot name 

message: Hey there, to assist in BAG tasks, I have created a user script.
To install it, simply add the line:
importScript("User:TheFearow/baghelper.js");
to the bottom of your monobook.js file. Then, perform a hard reload. It adds the following tabs on BRFA pages:
* BAG Trial (prompts for the extra template params, and replies with a bottrial tag)
* BAG Speedy (replies with a botspeedy tag)
* BAG Approve (replies with a botapproved tag)
* BAG Denied (replies with a botdenied tag)
* BAG Archive (archives the request, prompts for result which is either Speedy, Approved, Denied, Withdrawn, Expired, etc)
Speedy, approve, and deny do not reload, as you are supposed to archive right after. On both archive and trial, the page is reloaded after completion. Progess is shown in the contentSub, right below the text "From Wikipedia, the free encyclopedia", which is right below the title. Lastly, please do not just copy across the content, as I may be updating etc the script with bug patches/more features. Enjoy! Matt/TheFearow (Talk) (Contribs) (Bot) 01:45, 20 August 2007 (UTC)
replies: text: I have added an Expired and a Withdrawn template to it. I am considering adding one that adds the  and a custom message. Does anyone like the idea? Matt/TheFearow (Talk) (Contribs) (Bot) 21:46, 21 August 2007 (UTC)
replies: text: Looks like a pretty good idea. Cbrown1023 talk 01:43, 22 August 2007 (UTC)
thread_title:  User Script 

message: I've unblocked a bot as requested on WP:BOWN, this appears to be an issue that is going to get way past BAG, please see the discussion there.  Thanks, — xaosflux Talk 00:50, 24 August 2007 (UTC)
thread_title:  Unblocked Bot 

message: I don't like that this template has an editrate parameter.  According to the bot policy:
I take this to mean that even already flagged bots should still run tasks that have been approved for trial only at two edits per minute, so that the operator and the BAG can monitor its operation, and so if there are any problems spotted by a sysop, the bot can be terminated/blocked and the edits reverted.  Now, I know that this edit rate restriction isn't always observed in practice.  But I don't think we should encourage higher edit rates as a matter of "template" routine.  Thoughts? — madman bum and angel 15:16, 28 August 2007 (UTC)
replies: text: Yes, you're exactly right.  The idea is that, during a trial, the botop manually approves and checks each edit, and is on hand to stop the bot immediately should problems arise.  The 2 epm should be a restriction noted for all unflagged bots, by virtue of them not having a flag - I think the line is blurred somewhat for existing botops, but they should still be encouraged to use a low edit rate, and be reminded that they're expected to check all the edits. Martinp23 16:14, 28 August 2007 (UTC)
replies: text: Parameter removed. ~ Wikihermit 22:27, 28 August 2007 (UTC)
thread_title:  {{tl|BotTrial}}