878:
better, but current
English Knowledge culture means that delivering them by default is unlikely to get consensus, and getting a newcomer to signup for a newsletter may be hard. That being said, perhaps we could have a new editors newsletter that gets delivered monthly to those who do signup; it could have a brief tip of the month and pointers to editing ideas. That is something I might be interested in co-ordinating. On the encouraging participation front, I think it would be helpful to have one or more facilitators maintaining a page for each event, to be a hub for those participating, and perhaps maintaining an aggregated tally (I hesitate to have an explicit leaderboard, but there are pros and cons in favour of one).
713:
to
Knowledge. I think something to be more concerned about from that angle is how there tends to be a backlog of thousands of drafts and new editors with potential aren't nessecarily getting quick or personalized feedback. Like many areas, we have the problem of a few volunteers trying to do what they can to make sure that these processes get by. When we're just focusing on getting by, it makes it a lot harder to thrive and go that extra mile, because it's easy for people who are involved in these processes to become burnt out. If we had better editor retention, this would be less of an issue because the overall workload would be more sustainable... so I think this does becomes somewhat of a vicious cycle.
949:
newbies, are also unaware "that
Knowledge's content (the article) is determined by a consensus of everyone editing its pages..." I tell anyone interested that many times the talk pages are more interesting than the article they discuss. Reading the talk pages provides a window into the construction, the etiquette of communicating toward a goal, and through the ebbs and flows of discussion and editing, an ever-changing article is put forth. It's the classroom, the hidden secret that needs to be "sold" to the public and to newbies. It's taken for granted that They Know. But maybe they don't.
816:" idea, with a specific emphasis on welcoming newcomers to try these new things? I can see something like that being worth brainstorming as it can give people a sense of direction and guide people to areas where they can make a measurable difference to said backlogs. I remember when I was brand new, I was super excited to do things but it felt like everything was going into a void. It's part of the reason I like some of the new features that are being designed nowadays that show things like "your impact". But newbie me did come across the
504:
486:
560:
365:
455:
396:
437:
335:
780:, and encourage new editors to practice working on one aspect of editing Knowledge. This month we might want to work on citing articles, the next month working on typo finding, etc. By doing so, we would merge all editor retention efforts to a single program, and new editor will have comrades to talk to and feel validated by experienced editors. What do you think about this?
882:
of it being retained in the article, and every page has a corresponding talk page, which you should use to collaborate with other editors. (For those who don't understand
Knowledge's mission, the one key point would be that Knowledge's content is determined by a consensus of everyone editing its pages, which may not correspond to what you think should be in Knowledge.)
604:
976:
is no mention that the editors are unpaid volunteers. When I first read it, it gave me the impression that editors were in a room somewhere negotiating terms on what should go and what should stay. We all know how important the talk pages are but as this article shows they seem to be our secret.....
881:
For better or worse, editing an encyclopedia beyond typo fixing is a time-consuming activity. If I could get two concise points across to newcomers who already understand
Knowledge's mission, they would be the following: adding references to sources for any content you add will improve the likelihood
442:
One of our most obvious objectives in editor retention is to forward the idea of equality, regardless of race, gender, ethnicity, religion or creed. No one who discriminates may advertise here or be in any way a part of WER. Discrimination is completely against our entire mission, and will neither be
877:
I think it's worthwhile trying to try to get people to work on specific tasks. Things to think about, though, is how to get people to know about the initiative, and how to attract them to participate. Banner blindness makes it tricky for projects to get attention. Talk page notices would likely work
712:
To get a bit more on track though, given that new editors typically edit in draftspace until they're autoconfirmed and these articles rarely get moved to mainspace by experienced AfC reviewers if they're completely unsourced... I'm not sure this will actually raise the bar that much for contributing
975:
This
Aljazeera article is a good example] of what I mean. It is a very good descriptive recount of what happens. But there is no explanation that the discussions about the article happen on a page that is, in a way, separate and detached from the article. There is no mention of a "talk page". There
708:
problem when it comes to what people see when they actually click edit. This isn't really something the average wikipedian can control but I do remember seeing an interesting pilot project from someone involved with the WMF that would encourage people to cite sources when they added content. It had
665:
and I afraid that this might have a chilling effect to new editors who are looking to join
Knowledge, because this would set the standard for contributing Knowledge even higher than it is now. How can we make sure that we would stop biting newcomers? Improved mentoring program for new editors? Ban
849:
Oh, something else! I created a "newbie central" section on my talk page after my experience teaching newcomers at a
Knowledge Day event. It was a bit different trying to explain these things in person to people, but something that ended up being a focus was different stub templates that might be
873:
I think most editors are quite familiar with banner blindness and how people don't like to read instructions. I think having more volunteer mentors as part of the growth team features initiative would be a good way to help more new editors to ramp up. But... the feedback I've seen is that there
948:
mentions, "...and every page has a corresponding talk page". Now we all know that every article has a talk page but my experience is that the general public (aka our readers) are unaware that they exist. Another thing I have found in defending WikiPedia in RL is that they, the public and maybe
419:
In July 2012, some editors started a page called WikiProject Editor
Retention with the idea of creating a place to brainstorm ideas about helping newcomers and fostering a friendlier atmosphere. Today the most vibrant parts of that project's discussion page have gripes about "bullying done by
709:
prompts that would exist while someone was actually editing. I remember seeing it and thinking it was a gamechanger, it was honestly really nice and something we should have had ages ago. I hope it's still in-the-works and that I can get to see it in action someday. :)
599:
831:
As for banner blindness, I think it is worth considering if the editor made templates and whatnot can be simplified and still get the crucial pieces of information that people need to know across, even if it's not quite what I was thinking about last night.
589:
Back on July 1, 2012, Dennis Brown said: "I'm seeing a lot of discussion in a lot of places regarding editor retention, but not a coordinated effort. This is that coordinated effort, a way for us to actually do something beside speak out in random venues."
605:
Knowledge talk:WikiProject Editor
Retention/Archive 1#Core reasons for good editor dissatisfaction related to content: Unmet need for recognition, Frustration with seeing good work ruined, Exasperation at having to continuously defend completed
874:
aren't many useful questions being asked of mentors, and little follow up. So at present it's not going to be a magic bullet to increase retention dramatically, though I see it as a needed base requirement to support other initiatives.
549:
703:
Ooh, I've become courtesy ping worthy when it comes to brainstorming. :) You have no idea how excited this makes me. I'll probably have grander thoughts sometime later but the first thing that comes to mind is that we have a serious
754:. That banner is so long that I just feel sorry for any new editors who have to face with this banner... Maybe we should make a checklist of requirements that an article have to achieve before it will not be deleted under AfD?
635:
610:
625:
630:
515:, a collaborative effort to improve the coverage of efforts to improve editor retention on Knowledge. If you would like to participate, please visit the project page, where you can join
615:
640:
650:
420:
administrators," debates over whether "Knowledge has become a bloody madhouse," and disputes featuring accusations such as "You registered an account today just to have a go at me?"
645:
620:
577:
96:
326:
675:
374:
666:
generic/templated warnings asking people to cite sources? I don't know. Feel free to write about your wildest proposals for retaining new editors here, I'm all ears.
31:
322:
318:
314:
310:
306:
302:
298:
294:
290:
286:
282:
278:
274:
270:
266:
262:
258:
254:
250:
246:
242:
238:
234:
230:
226:
222:
218:
798:. People don't edit Knowledge because it is a significant time investment. The more convenient we make for new editors to join in to our efforts, the better.
214:
210:
206:
202:
198:
194:
190:
186:
182:
807:
789:
698:
662:
600:
Knowledge talk:WikiProject Editor Retention/Archive 1#The decline is caused, at least in part, by increasing rejection of good-faith newcomer contributions
734:
and read everything on the banners, when in reality nobody cares about them. I think one of the ways we can improve is to simplify these banners, such as
656:
1009:
844:
763:
725:
49:
973:
1014:
891:
40:
945:
883:
862:
131:
994:
927:
910:
795:
967:
772:
Ok, I have an idea. What if we create an operation for teaching newcomers to cite articles, as part of the mentorship program at
511:
491:
81:
22:
898:
I think the pilot project you're referencing, Clovermoss, is Reference Check, which is being developed as part of the larger
137:
334:
567:
636:
Knowledge talk:WikiProject Editor Retention/Archive 29#SPA Welcome #2--Expanding your Knowledge experience (SMcCavandish)
748:
550:
Previous conversations about newbies, all in one place, so we can harvest ideas for solutions and not re-hash them
773:
414:
77:
776:? Maybe we could establish a program under WikiProject Editor Retention, in a similar minimalistic style like
738:
126:
915:
Edit check does indeed seem to be what I was thinking of. Thanks for the links, Sdkb, it's appreciated. :)
803:
785:
759:
694:
671:
466:
381:
117:
828:
which is a similar concept of "this is stuff you can do", but I wouldn't say it's that very well known.
817:
611:
Knowledge talk:WikiProject Editor Retention/Archive 1#Getting across to newbies quickly and clearly ...
177:
939:
902:
project. I share the view that that has by far the best potential to help with this issue. Cheers,
821:
404:
349:
162:
799:
781:
755:
690:
667:
594:
586:
This is a library of sorts. Open 24/7. No library card is required and no fines will be levied.
825:
626:
Knowledge talk:WikiProject Editor Retention/Archive 29#A suggestion for welcoming new editors
472:
155:
924:
859:
841:
722:
8:
731:
631:
Knowledge talk:WikiProject Editor Retention/Archive 29#My experience as a new wiki editor
107:
850:
within that editor's field of interest. I'm a bit curious on what you think about that.
147:
122:
730:
This this this! Editors on wikipedia loves to assume that new editors would have done
985:
958:
813:
103:
887:
705:
916:
851:
833:
777:
769:
714:
686:
616:
Knowledge talk:WikiProject Editor Retention/Archive 28#What is editor retention?
503:
485:
641:
Knowledge talk:WikiProject Editor Retention/Archive 30#The elephant in the room
899:
345:
1003:
651:
Knowledge talk:WikiProject Editor Retention/Archive 30#Newcomers and contests
977:
950:
646:
Knowledge talk:WikiProject Editor Retention/Archive 30#Loss of core editors
621:
Knowledge talk:WikiProject Editor Retention/Archive 29#A note from some guy
559:
364:
350:
904:
682:
347:
796:
What is the main reason more people don't start editing Knowledge?
395:
576:
351:
72:
1001:
84:and anything related to its purposes and tasks.
657:Involve new editors to cite unsourced articles
465:does not require a rating on Knowledge's
575:
1010:Knowledge pages referenced by the press
566:This section is pinned and will not be
1002:
525:Knowledge:WikiProject Editor Retention
1015:WikiProject Editor Retention articles
528:Template:WikiProject Editor Retention
820:and find people looking for help at
812:It sounds like you're suggesting a "
794:I think this echo the sentiments at
581:An un-opened gift from User:Penyulap
553:
454:
452:
448:
431:
390:
359:
16:
663:depreciating new unsourced articles
471:It is of interest to the following
13:
14:
1026:
661:I've just made a new proposal to
509:This page is within the scope of
413:Tom Simonite (October 22, 2013).
405:mentioned by a media organization
558:
502:
484:
453:
435:
394:
363:
333:
97:Click here to start a new topic.
774:Knowledge:Growth Team features
1:
519:and see a list of open tasks.
94:Put new text under old text.
512:WikiProject Editor Retention
371:WikiProject Editor Retention
82:WikiProject Editor Retention
7:
102:New to Knowledge? Welcome!
10:
1031:
928:17:15, 17 March 2024 (UTC)
911:16:49, 17 March 2024 (UTC)
892:17:13, 17 March 2024 (UTC)
863:17:22, 17 March 2024 (UTC)
845:17:13, 17 March 2024 (UTC)
818:Knowledge:Community portal
808:07:58, 17 March 2024 (UTC)
790:07:55, 17 March 2024 (UTC)
764:07:46, 17 March 2024 (UTC)
726:07:39, 17 March 2024 (UTC)
699:07:17, 17 March 2024 (UTC)
676:07:17, 17 March 2024 (UTC)
415:"The Decline of Knowledge"
403:This WikiProject has been
145:
995:03:52, 11 July 2024 (UTC)
968:03:19, 11 July 2024 (UTC)
531:Editor Retention articles
497:
479:
417:. MIT Technology Review.
132:Be welcoming to newcomers
822:Knowledge:Typo Team/moss
749:AfC submission/declined
595:Knowledge:First contact
443:endorsed nor tolerated.
583:
568:automatically archived
127:avoid personal attacks
940:Selling the Talk page
826:Knowledge:Task center
579:
327:Auto-archiving period
824:. There is also the
814:backlog of the month
739:AfC submission/draft
376:a WikiProject Report
800:CactiStaccingCrane
782:CactiStaccingCrane
756:CactiStaccingCrane
691:CactiStaccingCrane
668:CactiStaccingCrane
584:
467:content assessment
138:dispute resolution
99:
33:Editor of the Week
992:
965:
574:
573:
547:
546:
543:
542:
539:
538:
447:
446:
430:
429:
389:
388:
385:on 22 April 2013.
358:
357:
118:Assume good faith
95:
68:
67:
1022:
984:
957:
922:
919:
909:
907:
857:
854:
839:
836:
753:
747:
743:
737:
720:
717:
706:banner blindness
562:
554:
533:
532:
529:
526:
523:
522:Editor Retention
506:
499:
498:
492:Editor Retention
488:
481:
480:
458:
457:
456:
449:
439:
438:
432:
422:
398:
391:
373:was featured in
367:
360:
352:
338:
337:
328:
165:
158:
73:
61:
52:
43:
34:
25:
17:
1030:
1029:
1025:
1024:
1023:
1021:
1020:
1019:
1000:
999:
942:
920:
917:
905:
903:
855:
852:
837:
834:
751:
745:
741:
735:
718:
715:
681:Courtesy ping:
659:
582:
563:
552:
530:
527:
524:
521:
520:
436:
426:
425:
412:
408:
354:
353:
348:
325:
171:
170:
169:
168:
161:
154:
150:
143:
113:
80:for discussing
69:
59:
50:
41:
32:
23:
12:
11:
5:
1028:
1018:
1017:
1012:
998:
997:
989:
981:
962:
954:
941:
938:
937:
936:
935:
934:
933:
932:
931:
930:
896:
895:
894:
879:
875:
871:
870:
869:
868:
867:
866:
865:
829:
710:
658:
655:
654:
653:
648:
643:
638:
633:
628:
623:
618:
613:
608:
602:
597:
580:
572:
571:
564:
557:
551:
548:
545:
544:
541:
540:
537:
536:
534:
517:the discussion
507:
495:
494:
489:
477:
476:
470:
459:
445:
444:
440:
428:
427:
424:
423:
409:
402:
401:
399:
387:
386:
368:
356:
355:
346:
344:
343:
340:
339:
173:
172:
167:
166:
159:
151:
146:
144:
142:
141:
134:
129:
120:
114:
112:
111:
100:
91:
90:
87:
86:
85:
66:
65:
63:
56:
54:
47:
45:
38:
36:
29:
27:
20:
15:
9:
6:
4:
3:
2:
1027:
1016:
1013:
1011:
1008:
1007:
1005:
996:
991:
990:
987:
983:
982:
979:
974:
972:
971:
970:
969:
964:
963:
960:
956:
955:
952:
947:
929:
926:
923:
914:
913:
912:
908:
901:
900:mw:Edit check
897:
893:
889:
885:
880:
876:
872:
864:
861:
858:
848:
847:
846:
843:
840:
830:
827:
823:
819:
815:
811:
810:
809:
805:
801:
797:
793:
792:
791:
787:
783:
779:
775:
771:
767:
766:
765:
761:
757:
750:
740:
733:
729:
728:
727:
724:
721:
711:
707:
702:
701:
700:
696:
692:
688:
684:
680:
679:
678:
677:
673:
669:
664:
652:
649:
647:
644:
642:
639:
637:
634:
632:
629:
627:
624:
622:
619:
617:
614:
612:
609:
607:
603:
601:
598:
596:
593:
592:
591:
587:
578:
569:
565:
561:
556:
555:
535:
518:
514:
513:
508:
505:
501:
500:
496:
493:
490:
487:
483:
482:
478:
474:
468:
464:
460:
451:
450:
441:
434:
433:
421:
416:
411:
410:
406:
400:
397:
393:
392:
384:
383:
378:
377:
372:
369:
366:
362:
361:
342:
341:
336:
332:
324:
320:
316:
312:
308:
304:
300:
296:
292:
288:
284:
280:
276:
272:
268:
264:
260:
256:
252:
248:
244:
240:
236:
232:
228:
224:
220:
216:
212:
208:
204:
200:
196:
192:
188:
184:
181:
179:
175:
174:
164:
160:
157:
153:
152:
149:
139:
135:
133:
130:
128:
124:
121:
119:
116:
115:
109:
105:
104:Learn to edit
101:
98:
93:
92:
89:
88:
83:
79:
75:
74:
71:
64:
62:
57:
55:
53:
48:
46:
44:
39:
37:
35:
30:
28:
26:
21:
19:
18:
986:
980:Buster Seven
978:
959:
953:Buster Seven
951:
943:
732:WP:Tutorials
660:
588:
585:
516:
510:
473:WikiProjects
463:project page
462:
418:
380:
375:
370:
330:
176:
163:WT:RETENTION
76:This is the
70:
58:
946:User:Isaacl
1004:Categories
918:Clovermoss
853:Clovermoss
835:Clovermoss
770:Clovermoss
716:Clovermoss
687:Clovermoss
148:Shortcuts
140:if needed
123:Be polite
78:talk page
60:Talk page
51:Templates
24:Main page
778:WP:FEB24
382:Signpost
178:Archives
108:get help
944:Above,
379:in the
331:20 days
42:Members
993:(UTC)
966:(UTC)
925:(talk)
884:isaacl
860:(talk)
842:(talk)
723:(talk)
469:scale.
156:WT:WER
461:This
136:Seek
988:Talk
961:Talk
906:Sdkb
888:talk
804:talk
786:talk
760:talk
744:and
695:talk
683:Sdkb
672:talk
606:work
125:and
1006::
921:🍀
890:)
856:🍀
838:🍀
806:)
788:)
762:)
752:}}
746:{{
742:}}
736:{{
719:🍀
697:)
689:.
685:,
674:)
329::
323:36
321:,
319:35
317:,
315:34
313:,
311:33
309:,
307:32
305:,
303:31
301:,
299:30
297:,
295:29
293:,
291:28
289:,
287:27
285:,
283:26
281:,
279:25
277:,
275:24
273:,
271:23
269:,
267:22
265:,
263:21
261:,
259:20
257:,
255:19
253:,
251:18
249:,
247:17
245:,
243:16
241:,
239:15
237:,
235:14
233:,
231:13
229:,
227:12
225:,
223:11
221:,
219:10
217:,
213:,
209:,
205:,
201:,
197:,
193:,
189:,
185:,
106:;
886:(
802:(
784:(
768:@
758:(
693:(
670:(
570:.
475::
407::
215:9
211:8
207:7
203:6
199:5
195:4
191:3
187:2
183:1
180::
110:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.