598:
480:
been nominated" and then an "image has been deleted" prompt, just for uniformity. The image being deleted notification IMO is useful, because it prompts authors to find new images for the page. The main reason for notifying on deletion is that we had a problem where a very very widely used image was deleted w/o notification, which could have been interesting :) If needs be I can limit the "deletion" notification only for images with over 75 uses. Thanks for the feedback. --
664:
411:
48:
456:
Notification is useful if is announced when a file is tagged/nominated, not when already deleted. After an image is deleted nobody can see it, so is hard to provide any useful feedback. As stated in the notification, there are bots which remove deleted images from articles, so is pointless to notify
479:
I will reduce the size of the image, that was on my todo list today FWIW. Regarding the rest - nominations are "coming" (speedy nominations are working, normal deletion discussions might take a bit longer while I work on a solid way to track them). The intent is that each page will get a "image has
389:
At the moment I can extend the time limits to whatever is deemed necessary. I am still working on the code to sweep for FfD's. From my testing I suggest running sweeps for deletions and CSD nominations every 15 minutes. And when FfD's get going to run that in a new thread once a day (that should be
298:
and if this looks good to the bot people from a bot standpoint I'd get behind it. Fact of the matter is that
Commons is never going to reach out to us and tell us that they're deleting something we use. We have to go to them then and take the information, and this bot seems like a step in the right
608:
the full 7 days, but I am going ot be busy the rest of this week so wanted to post this while I had time. Over the week I ran into a few bugs, which are now fixed (a wierd crash bug was fixed this morning) and the code has been pretty stable and accurate for the last couple of days. I'm no longer
540:
Regarding multiple images in a notification.... I want to try and do this, unfortunately it is not all that easy with the way I have currently structured the code. There are a few pages that end up with a rash of notifications - but mostly it is one notice per page. Once I have things stable and
359:
I have been told that in many cases CSDs, as well as all admin functions, are slower at
Commons than at Knowledge. As low as our admin numbers are, Commons has it even rougher. 15 minutes should be more than enough time, even 30. I've been told that CSDs can last for two or three days at Commons
506:
Thanks, is much better, but if there would be a way to consolidate multiple notifications into one, (i.e. have only one notification with a list of images) would be even nicer. Regarding deletion notification, in the Wiel Arets case I would have noticed anyway about
609:
posting deletion notifications, only nominations. The early problems with posting a notification multiple times to the same page has now been fixed :) Response seems to be good, no one has complained :) r.e. Jarry's comments above, if it is preferable to avoid
617:
then that is fine. One of the reasons I chose AN was because it is possible that some of these issues might need admins to fix. Sven has suggested that he is working on a new board/location for image problems - so long term the bot can post there instead.
285:
UPDATED 27/04/2011: The bot can now do the above for images nominated for speedy deletion (i.e. logging nominations, addign a note to article talk pages). Currently working on a good way to track normal deletion.
511:
and I don't think is worth the trouble to leave those messages on the talk page. Certainly, a threshold set for such notifications -as you suggested- I would see as an improvement. --
384:
460:
The notification message is way too large and opulent, creating an unpleasant visual clutter on the article talk page. A shorter message with a small icon would do the same job.
396:
583:
191:
424:
590:
677:
653:
638:
547:
501:
435:
565:
535:
520:
486:
251:
The bot monitors commons file deletions and checks for the image use on this wiki. Where image usage on WP is found the initial implementation will do the following:
68:
644:
211:
No idea... but in the bot functions I propose having an "upper limit" of the talk pages the bot will place a notice before going to a central location instead.
708:
185:
This bot will replace the original
CommonsTicker bot (which has been out of action for a while) to notify WP users of file deletions that might affect them
553:
323:
624:
473:
349:
339:
The coding people will need to pass judgment on that aspect of the bot. If it performs its 50 edit trial run well then I say approve it. cheers --
586:
There is no way spamming AN and VPM every time is going to be sustainable. Try just VPM for now, I should think. But looking good otherwise :) -
195:
267:
492:
73:
449:
88:
332:
For FfDs have the bot run once a day. The discussions tend to last more time (7 days I think) so one big sweep a day would be sufficient.
83:
508:
118:
390:
fine IMO). The crucial thing, to my mind, is catching the big deletions and notifying those who can fix things at this end. --
335:
For CSDs I recommend the bot to run every hour, 30 minutes or 15 minutes depending on how speedy commons speedy deletion is.
103:
21:
93:
415:
Approved for trial (7 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
452:. While I agree that is useful to notify editors on Knowledge about deletion discussions on Commons, I see some issues:
443:
526:
98:
58:
289:
113:
139:
108:
78:
260:
256:
59:
630:
I'm ready to approve, but would you mind renaming the bot to
CommonsNotificationBot for consistency?
266:
Add a talk page note to the article talk pages (for each article the image was used on) (template:
375:
314:
328:
I can find no issue with the concept of this bot. For the bots timing this is my suggestion.
344:
194:, no further discussion but I can get input from VP if needed (update: opened a discussion
162:
8:
690:
40:
176:
541:
working nicely I will look at re-engineering the bot so it can support that feature. --
361:
300:
133:
561:
516:
469:
259:
with a list of files used on WP that have been deleted on commons (example output:
340:
587:
17:
702:
614:
220:
671:
649:
632:
620:
610:
543:
531:
497:
482:
431:
418:
392:
275:
129:
557:
512:
465:
171:
493:
Talk:Ludovic_Hubler#File:CARICATURE5.jpg_Nominated_for_speedy_Deletion
47:
167:
Python (pywikibot and some custom code for imageusage API calls)
683:
The above discussion is preserved as an archive of the debate.
689:
To request review of this BRFA, please start a new section at
39:
To request review of this BRFA, please start a new section at
149:
213:
300-500 edits per day (200-400 to article talk pages)
192:
Issue (of commons ticker being down) was noted on AN/I
177:
http://hg.errant.me.uk/wikibots/src/tip/commonsbot.py
282:
All of the above limits can be tweaked as required.
529:, I'll try to get it working like that tomorrow. --
189:Links to relevant discussions (where appropriate):
552:Yep, I guess is complicated as so far I only saw
429:Thanks, will start the trial tomorrow morning. --
700:
33:The following discussion is an archived debate.
525:Yep, solid argument, you have me convinced :)
268:User:CommonsNotification/imagedeletion_article
556:. Thanks again for your friendly response. --
709:Approved Knowledge bot requests for approval
457:editors that they should do it manually.
14:
701:
491:Slightly less opulent notification:
208:Estimated number of pages affected:
27:
28:
720:
45:The result of the discussion was
662:
596:
409:
46:
273:If the number of articles : -->
148:12:25, Tuesday April 26, 2011 (
13:
1:
261:User:CommonsNotification/log
7:
274:50 it will instead post to
257:Knowledge:Commons Deletions
10:
725:
385:01:49, 30 April 2011 (UTC)
350:02:21, 29 April 2011 (UTC)
324:23:39, 27 April 2011 (UTC)
643:No, don't mind at all :)
686:Please do not modify it.
678:10:09, 16 May 2011 (UTC)
654:08:33, 16 May 2011 (UTC)
639:02:16, 16 May 2011 (UTC)
625:12:02, 11 May 2011 (UTC)
36:Please do not modify it.
591:16:29, 9 May 2011 (UTC)
566:13:29, 6 May 2011 (UTC)
548:12:17, 6 May 2011 (UTC)
536:12:13, 6 May 2011 (UTC)
521:10:58, 6 May 2011 (UTC)
502:10:20, 6 May 2011 (UTC)
487:10:10, 6 May 2011 (UTC)
474:22:11, 5 May 2011 (UTC)
436:16:19, 4 May 2011 (UTC)
425:01:47, 4 May 2011 (UTC)
397:09:23, 3 May 2011 (UTC)
158:Automatic unsupervised
237:Already has a bot flag
60:CommonsNotificationBot
232:not sure it is needed
22:Requests for approval
645:request filed @ CHUS
163:Programming language
156:Automatic or Manual:
450:these notifications
360:before being seen.
278:with a notification
221:Exclusion compliant
215:updated 06/05/2011
183:Function overview:
613:and just go with
382:
321:
249:Function details:
716:
688:
674:
666:
665:
635:
600:
599:
554:one bot doing it
421:
413:
412:
381:
376:
373:
347:
320:
315:
312:
233:
216:
50:
38:
724:
723:
719:
718:
717:
715:
714:
713:
699:
698:
697:
684:
672:
663:
633:
602:Trial complete.
597:
527:On my todo list
448:I just noticed
446:
419:
410:
377:
370:
366:
362:
345:
316:
309:
305:
301:
292:
231:
214:
202:Edit period(s):
179:(still in dev)
124:
63:
34:
26:
25:
24:
12:
11:
5:
722:
712:
711:
696:
695:
680:
659:
658:
657:
656:
594:
593:
579:
578:
577:
576:
575:
574:
573:
572:
571:
570:
569:
568:
462:
461:
458:
445:
444:Trial feedback
442:
441:
440:
439:
438:
406:
405:
404:
403:
402:
401:
400:
399:
368:
364:
337:
336:
333:
307:
303:
291:
288:
280:
279:
271:
264:
123:
122:
116:
111:
106:
101:
96:
91:
86:
81:
76:
74:Approved BRFAs
71:
64:
62:
57:
56:
55:
29:
18:Knowledge:Bots
15:
9:
6:
4:
3:
2:
721:
710:
707:
706:
704:
694:
692:
687:
681:
679:
676:
675:
669:
661:
660:
655:
652:
651:
646:
642:
641:
640:
637:
636:
629:
628:
627:
626:
623:
622:
616:
612:
607:
603:
592:
589:
585:
581:
580:
567:
563:
559:
555:
551:
550:
549:
546:
545:
539:
538:
537:
534:
533:
528:
524:
523:
522:
518:
514:
510:
505:
504:
503:
500:
499:
494:
490:
489:
488:
485:
484:
478:
477:
476:
475:
471:
467:
459:
455:
454:
453:
451:
437:
434:
433:
428:
427:
426:
423:
422:
416:
408:
407:
398:
395:
394:
388:
387:
386:
383:
380:
374:
372:
358:
357:
356:
355:
354:
353:
352:
351:
348:
342:
334:
331:
330:
329:
326:
325:
322:
319:
313:
311:
297:
287:
283:
277:
272:
269:
265:
262:
258:
254:
253:
252:
250:
246:
244:
241:
238:
234:
229:
226:
223:
222:
217:
212:
209:
205:
203:
199:
197:
193:
190:
186:
184:
180:
178:
175:
173:
168:
166:
164:
159:
157:
153:
151:
147:
143:
141:
138:
135:
131:
128:
120:
117:
115:
112:
110:
107:
105:
102:
100:
97:
95:
92:
90:
87:
85:
82:
80:
77:
75:
72:
70:
66:
65:
61:
53:
49:
44:
42:
37:
31:
30:
23:
19:
685:
682:
670:
667:
648:
631:
619:
605:
601:
595:
542:
530:
509:15 min later
496:
481:
463:
447:
430:
417:
414:
391:
378:
363:
338:
327:
317:
302:
295:
293:
284:
281:
248:
247:
242:
239:
236:
235:
227:
224:
219:
218:
210:
207:
206:
201:
200:
188:
187:
182:
181:
170:
169:
161:
160:
155:
154:
145:
144:
136:
126:
125:
51:
35:
32:
299:direction.
204:Continuous
198:for input)
172:Source code
146:Time filed:
584:New Meixco
341:Guerillero
290:Discussion
174:available:
114:rights log
104:page moves
668:Approved.
588:Jarry1250
296:something
127:Operator:
109:block log
703:Category
294:We need
140:contribs
84:contribs
52:Approved
20: |
691:WT:BRFA
673:MBisanz
634:MBisanz
420:MBisanz
371:anguard
346:My Talk
310:anguard
255:Update
130:ErrantX
41:WT:BRFA
650:Errant
621:Errant
615:WP:VPM
558:Elekhh
544:Errant
532:Errant
513:Elekhh
498:Errant
483:Errant
466:Elekhh
432:Errant
393:Errant
611:WP:AN
606:quite
495::) --
276:WP:AN
240:(Y/N)
225:(Y/N)
89:count
16:<
604:Not
562:talk
517:talk
470:talk
379:Wha?
367:ven
318:Wha?
306:ven
196:here
165:(s):
134:talk
119:flag
99:logs
79:talk
69:BRFA
582:Re
245:No
230:No
150:UTC
94:SUL
705::
647:--
618:--
564:)
519:)
472:)
464:--
343:|
152:)
142:)
693:.
560:(
515:(
468:(
369:M
365:S
308:M
304:S
270:)
263:)
243::
228::
137:·
132:(
121:)
67:(
54:.
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
