642:
304:, BAG members have the discretion to allow the proposed bot to undergo trial to judge its technical soundness. Trials can also be used to help determine consensus if relevant communities have been notified, but failed to engage in dialogue after a reasonable amount of time has elapsed. Bot trials exist so the community has a chance to review a proposed bot's behaviour, suggest improvements, voice opposition, point out issues, discuss the scope of its task, and to
556:
163:
623:
669:
594:
575:
179:
819:. This is a place where BAG can provide early feedback on whether or not something something should be done, how it can be done, or who could possibly do it. Pinging bot operators who did similar tasks before for their feedback is a good idea. Being involved here can save many coding hours, a lot of frustration, and reduce the number of bot requests that go unaddressed.
635:. Those usually happen when the operator agrees that the task is bad, needs time to flesh out the idea, or find themselves unable to fulfill the task for one reason or another. The operator may re-open the request later, especially if the BRFA is withdrawn because of time commitment. Tasks that go back to the drawing board should typically be filed as new BRFAs.
289:. The more contentious a task, the higher the burden of demonstrating consensus. Non-controversial and technically straightforward tasks may be approved after short trials, while more contentious and technically complex tasks may require formal and well-advertised RFCs accompanied by long trial periods. Typical places to hold such discussions are at the
324:
official rule, but more of a recognition that whoever approves a bot for trial is usually more familiar with the background of the task, and has implicitly agreed to review the bot's edit and follow up on any issues raised during the trial. If a BAG member is unable to finish the review, or is unsure on how to proceed, they should leave a note at
27:
243:
323:
Typically, a BAG member will oversee a BRFA from trial to closure, and invite (or mandate) involvement from the community. Other BAG members will often participate and comment during the BRFA to give their opinions on various matters, but defer to the trial-granter for closure. This is not an
963:
will often facilitate bot-like editing, or deal with tedious tasks. They can often be alternatives to bots that don't required full BRFAs. BAG Members should be familiar with what is out there, if only so people don't spend time coding bots for tasks that don't require them.
331:
To ensure the impartial reviews of BRFAs, BAG members should not oversee the process for their own bots, or in other BRFAs where impartiality would be compromised. Such involved BAG members can still participate and comment on the task, however.
1020:
870:
These pages sometimes have issues related to BAG's mandate, or of interest to the bot community. If you notice something bot-related in need of attention from the BAG and/or bot operators, please post a notice at
1025:
340:
This is a general overview of the broad categories of trials that are typically granted by BAG members. These do not not constitute 'official types', and when exactly a 'short' trial becomes a 'long' trial is
740:, with a list of current and former members. Few discussions take place there, but you should watch the page in case BAG's role changes. The talk page serves as a general discussion board for BAG matters.
906:. Several bot issues can be reported there. The usual requests are to block malfunctioning or rogue bots. In many ways, BAG's job is to prevent thing from going there in the first place (see the quote in
265:(and people interested in the inner workings of the BAG)! This is a small guide for common BAG-related tasks and duties, and how to best perform them. It also includes a few other useful resources.
795:, a list of all active BRFAs. BAG members have the mandate of reviewing BRFAs and determine both the technical soundness of the proposed bot, and ensure that the requested task has consensus.
380:
subtasks during the trial. BAG members may require the trial to have a specific number of edits for each substask, or require a trial with enough edits that each substask is demonstrated.
564:
If the task is completely non-controversial, such as extensions to tasks that have already been approved in the past, by an experienced coder in good standing, then the task can be
805:
A summary of all active BRFAs, updated several times a day. It is transcluded at the top of the BRFA page if you would rather not receive watchlist notices every time it updates.
938:. A summary of Knowledge (XXG)'s most contentious disputes. Occasionally involves bots. When things get there, BAG ought to take a deep look at how exactly that happened.
768:. All BAG members should know this page like the back of their hand. Many discussions and requests for clarification affecting several bots take place on the talk page.
108:
317:
376:
Additional conditions on trials can always be specified. In particular, a BRFA with multiple subtasks should demonstrate technical soundness and consensus for
999:
202:; rather, its purpose is to explain certain aspects of Knowledge (XXG)'s norms, customs, technicalities, or practices. It may reflect differing levels of
606:. The operator can re-open the request at a later time. Typical waiting time is 2 to 4 weeks. BAG should usually contact the operator (usually using
148:
277:
into account. Precedent can be used to inform judgment, but should never be used as a hammer. Each BRFA requires BAG members to determine both the
1050:
103:
693:
way, and the bot operator notified. You may also feel a notice is warranted on the talk page of a bot with high community engagement, such as
650:
If the task is technically unsound, consensus is unclear (or clearly against the task), or some major concerns remain, the task should be
199:
1035:
610:
662:
way. If the idea has potential, the operator should be invited to flesh out the idea with the community and re-submit the task later.
842:
297:, but other locations may be suitable as well depending on the nature of the bot task. When in doubt, ask for more community input.
141:
195:
136:
65:
17:
473:
trial is similar to a long trial, except with mandated pauses between editing sprees. For instance a bot could be approved for
187:
81:
1030:
537:
49:
457:
and a large number of edits need to be reviewed before the bot can be considered sound. They can also be granted to
481:. The main use of a ramp-up trial is to give time for bystanders to participate in the discussion in the case of a
1055:
153:
367:
98:
907:
313:
800:
308:. Once technical soundness and consensus are satisfied, bot tasks can be approved. If a new bot requires a
279:
58:
998:, a weekly newsletter covering "recent software changes likely to impact Wikimedians". You can subscribe
834:
285:
207:
203:
88:
131:
976:
872:
852:
325:
217:
969:
943:
824:
309:
305:
301:
273:
BAG members are expected to use sound judgement and take the full situation and background of every
530:
126:
810:
759:
717:
These pages are directly related to BAG's mandate, and every active BAG member should watch them.
501:
An extended trial is an additional trial that follows a previous trial. These are usually done to
1014:
516:
Once a BRFA has run its course, BAG members should close it in one of the following manners. See
118:
983:
880:
686:
655:
583:
If the task is technically sound, has consensus, and no major concerns remain, the task can be
694:
357:
883:, members are expected to give advice on bot-related matters and to help mediate situations.
787:
773:
745:
690:
659:
294:
274:
42:
782:. Many discussions and requests for clarification affecting specific bots take place there.
520:
929:
915:
897:
876:
856:
731:
678:
262:
252:
622:
342:
290:
698:
345:. In practice, BAG members simply state the specific length and conditions of a trial (
602:
If the bot operator has become unresponsive or inactive, the BRFA should be marked as
1044:
851:
on Libera Chat. BAG members are voiced. It serves as a less formal alternative to
505:, and can be of any duration. A bot may be subject to multiple extended trials.
490:
990:
437:
tasks, to prove that the bot is both technically sound and works as intended.
1021:
Knowledge (XXG):Bots/Requests for approval/Instructions for bot operators
631:
If the bot operator withdraws the request, the BRFA should be marked as
1026:
Knowledge (XXG):Bots/Requests for approval/Instructions for BAG members
470:
924:. Several technical issues are discussed there, many related to bots.
26:
503:
confirm issues flagged in a previous trials have been corrected
300:
If consensus has been demonstrated, is likely to form, or can
237:
173:
32:
654:. The reason for denying approval should be made clear, in a
493:
in tasks that affect a very large number of pages (10,000+).
461:
once they see the bot editing an article on their watchlist.
283:
of the proposed bot, and ensure that the requested task has
25:
754:
on
Knowledge (XXG). Serves mostly as an overview page.
685:. The reason for revocation should be made clear, in a
251:
This page documents the common tasks and duties of the
225:
421:Most BRFA will have a typical trial length between
318:
Knowledge (XXG):Bots/Requests for approval/Approved
485:that could prove to be controversial, but also as
1017:, a collection of common templates used in BRFAs
459:allow for more bystanders to give their feedback
453:. These are typically granted when the task is
316:will apply the flag after the BRFA is added to
255:, as well as useful resources to BAG members.
8:
445:Long trials typically are anywhere between
833:. Sent infrequently. You can subscribe at
409:in good standing. This is also known as a
904:Administrator's Noticeboard for Incidents
885:
719:
542:
397:This should only be done for completely
382:
200:Knowledge (XXG)'s policies or guidelines
681:, approval of a task may be marked as
1036:Knowledge (XXG):Administrators' guide
403:tasks that have already been approved
7:
18:Knowledge (XXG):Bot Approvals Group
616:) to see if the operator replies.
24:
1051:Knowledge (XXG) information pages
936:Arbitration Committee Proceedings
922:Village Pump, Technical Division
667:
640:
621:
592:
573:
554:
241:
177:
171:Knowledge (XXG) information page
161:
879:. While BAG duties differ from
483:presumed or tentative consensus
349:), rather than the trial type (
1:
1031:User:SQL/How to close a BRFA
538:User:SQL/How to close a BRFA
399:non-controversial extensions
347:Approved for trial, 50 edits
793:(Bot) Requests for Approval
540:for the technical details.
435:technically straightforward
1072:
815:A place for users to make
736:Describes the role of the
611:Operator assistance needed
479:2500 edits (250 edits/day)
351:Approved for a short trial
215:
947:
835:Knowledge (XXG):Bots/Spam
545:
429:. This is to be used for
343:best left to philosophers
475:500 edits (50 edits/day)
249:This page in a nutshell:
750:Describes the role of
627:Withdrawn by operator.
302:reasonably be presumed
30:
679:consensus has changed
104:Requests for Approval
29:
1056:Knowledge (XXG) bots
881:Administrator duties
328:so others can help.
196:encyclopedic article
738:Bot Approvals Group
405:in the past, by an
280:technical soundness
66:Bot Approvals Group
1015:Template:BAG Tools
764:Knowledge (XXG)'s
677:In the case where
560:Speedily Approved.
455:technically tricky
447:100 and 1000 edits
31:
1006:
1005:
863:
862:
843:#wikipedia-en-bag
705:
704:
695:User:Citation bot
568:without a trial.
566:speedily approved
509:
508:
431:non-controversial
407:experienced coder
259:
258:
236:
235:
169:
168:
1063:
886:
780:Bots Noticeboard
720:
671:
670:
644:
643:
625:
615:
609:
598:Request Expired.
596:
595:
577:
576:
558:
557:
543:
535:
529:
525:
519:
423:10 and 100 edits
383:
372:
368:BotExtendedTrial
366:
362:
356:
293:, or a relevant
245:
244:
238:
228:
188:information page
181:
180:
174:
165:
164:
137:Activity monitor
123:
117:
33:
1071:
1070:
1066:
1065:
1064:
1062:
1061:
1060:
1041:
1040:
1011:
868:
849:BAG IRC Channel
831:Bots Newsletter
715:
710:
668:
641:
613:
607:
593:
574:
555:
533:
527:
523:
517:
514:
411:speedy approval
370:
364:
360:
354:
338:
271:
242:
232:
231:
224:
220:
212:
211:
178:
172:
162:
158:
121:
115:
94:
22:
21:
20:
12:
11:
5:
1069:
1067:
1059:
1058:
1053:
1043:
1042:
1039:
1038:
1033:
1028:
1023:
1018:
1010:
1007:
1004:
1003:
993:
991:meta:Tech/News
987:
986:
980:
979:
973:
972:
966:
965:
946:
940:
939:
932:
926:
925:
918:
912:
911:
908:WP:BOTAPPROVAL
900:
894:
893:
890:
867:
864:
861:
860:
845:
839:
838:
827:
821:
820:
813:
807:
806:
803:
797:
796:
790:
784:
783:
776:
770:
769:
762:
756:
755:
748:
742:
741:
734:
728:
727:
724:
714:
711:
709:
708:Pages to watch
706:
703:
702:
699:User:AAlertBot
675:
664:
663:
648:
637:
636:
629:
618:
617:
600:
589:
588:
581:
570:
569:
562:
551:
550:
547:
513:
510:
507:
506:
499:
495:
494:
467:
463:
462:
443:
439:
438:
419:
415:
414:
395:
391:
390:
387:
337:
334:
270:
269:Guide to BRFAs
267:
257:
256:
246:
234:
233:
230:
229:
221:
216:
213:
193:
192:
184:
182:
170:
167:
166:
159:
157:
156:
151:
146:
145:
144:
139:
129:
127:Creating a Bot
124:
113:
112:
111:
101:
95:
93:
92:
85:
78:
77:
76:
62:
55:
54:
53:
38:
36:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
1068:
1057:
1054:
1052:
1049:
1048:
1046:
1037:
1034:
1032:
1029:
1027:
1024:
1022:
1019:
1016:
1013:
1012:
1008:
1001:
997:
994:
992:
989:
988:
985:
982:
981:
978:
975:
974:
971:
968:
967:
962:
958:
954:
950:
945:
942:
941:
937:
933:
931:
928:
927:
923:
919:
917:
914:
913:
909:
905:
901:
899:
896:
895:
891:
888:
887:
884:
882:
878:
874:
865:
858:
854:
850:
847:The official
846:
844:
841:
840:
836:
832:
828:
826:
823:
822:
818:
814:
812:
809:
808:
804:
802:
801:WP:BAG/Status
799:
798:
794:
791:
789:
786:
785:
781:
777:
775:
772:
771:
767:
763:
761:
758:
757:
753:
749:
747:
744:
743:
739:
735:
733:
730:
729:
725:
722:
721:
718:
712:
707:
700:
696:
692:
688:
684:
680:
676:
674:
666:
665:
661:
657:
653:
649:
647:
639:
638:
634:
630:
628:
624:
620:
619:
612:
605:
601:
599:
591:
590:
586:
582:
580:
572:
571:
567:
563:
561:
553:
552:
548:
544:
541:
539:
532:
522:
511:
504:
500:
497:
496:
492:
488:
484:
480:
476:
472:
468:
465:
464:
460:
456:
452:
448:
444:
441:
440:
436:
432:
428:
424:
420:
417:
416:
412:
408:
404:
400:
396:
393:
392:
388:
385:
384:
381:
379:
374:
369:
359:
352:
348:
344:
335:
333:
329:
327:
321:
319:
315:
311:
307:
306:break silence
303:
298:
296:
292:
288:
287:
282:
281:
276:
268:
266:
264:
254:
250:
247:
240:
239:
227:
223:
222:
219:
214:
209:
205:
201:
198:, nor one of
197:
194:It is not an
191:
189:
183:
176:
175:
160:
155:
152:
150:
147:
143:
142:Status report
140:
138:
135:
134:
133:
130:
128:
125:
120:
114:
110:
107:
106:
105:
102:
100:
97:
96:
91:
90:
86:
84:
83:
79:
75:
74:
70:
69:
68:
67:
63:
61:
60:
56:
52:
51:
47:
46:
45:
44:
40:
39:
37:
35:
34:
28:
19:
995:
960:
957:User Scripts
956:
952:
948:
935:
921:
903:
892:Description
869:
848:
830:
817:Bot Requests
816:
792:
779:
765:
751:
737:
726:Description
716:
691:constructive
682:
672:
660:constructive
651:
645:
632:
626:
603:
597:
584:
578:
565:
559:
549:When to use
515:
502:
491:corner cases
487:extra safety
486:
482:
478:
474:
458:
454:
451:7 to 30 days
450:
446:
434:
430:
426:
422:
410:
406:
402:
398:
389:When to use
377:
375:
350:
346:
339:
330:
322:
299:
291:Village Pump
284:
278:
272:
260:
248:
185:
132:List of bots
99:Bot Requests
87:
80:
72:
71:
64:
57:
48:
41:
977:WP:USCRIPTS
866:Bot-related
713:Bot-focused
427:3 to 7 days
373:templates.
353:) with the
295:WikiProject
263:BAG Members
186:This is an
82:Noticeboard
1045:Categories
970:WP:SCRIPTS
944:WP:GADGETS
825:WP:BOTNEWS
766:Bot Policy
531:Bot Bottom
314:bureaucrat
89:Newsletter
59:Bot policy
50:Dictionary
996:Tech News
811:WP:BOTREQ
760:WP:BOTPOL
633:withdrawn
579:Approved.
498:Extended
394:No trial
286:consensus
204:consensus
119:BAG Tools
109:Adminbots
1009:See also
984:WP:TOOLS
673:Revoked.
585:approved
512:Closures
489:against
466:Ramp up
358:BotTrial
310:bot flag
261:Welcome
218:Shortcut
43:Overview
959:, and
953:Scripts
949:Gadgets
875:and/or
788:WP:BRFA
774:WP:BOTN
746:WP:BOTS
683:revoked
646:Denied.
604:expired
546:Result
521:Bot Top
471:ramp up
226:WP:BAGG
208:vetting
149:History
930:WP:A/C
916:WP:VPT
898:WP:ANI
877:WP:BON
873:WT:BAG
857:WP:BON
853:WT:BAG
732:WP:BAG
652:denied
418:Short
386:Types
336:Trials
326:WT:BAG
961:Tools
889:Page
723:Page
687:civil
656:civil
442:Long
154:Types
73:Guide
16:<
1000:here
934:The
920:The
902:The
829:The
778:The
752:bots
689:and
658:and
536:and
433:and
312:, a
275:BRFA
206:and
910:).
855:or
697:or
477:or
449:or
425:or
401:to
378:all
253:BAG
1047::
1002:.
955:,
951:,
859:.
837:.
701:.
614:}}
608:{{
587:.
534:}}
528:{{
524:}}
518:{{
469:A
413:.
371:}}
365:{{
361:}}
355:{{
320:.
122:}}
116:{{
526:/
363:/
210:.
190:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
