The Signpost

News and notes

Two new Wikimedia fellows to boost strategies for tackling major issues

Contribute  —  
Share this
By Tony1

The Wikimedia foundation has just announced new community fellowships aimed at tackling two very different challenges faced by the movement. Both fall within the 2011–12 priorities of increasing participation and editor retention across the projects.

Small-wiki editor engagement

Tanvir Rahman, whose fellowship will look at the technical and social aspects of growing small wikis
An example of Bengali script: the word Wikipedia.
Tanvir Rahman is a steward and active editor of the Bengali Wikipedia, which has about 23,000 articles and 50 active editors—12 of whom make more than 100 edits a month. The project will concentrate on that site to experiment with "on-wiki strategies to encourage and grow the editing community on small language versions of Wikipedia", says Siko Bouterse, the foundation's head of community fellowships.

"Small", though, only refers to the size of the site: ironically, by some counts Bengali ranks sixth among the world's languages in terms of the number of native speakers, with nearly 300 million. We asked Tanvir why more Bengali-speakers aren't editing the site. He said, "Most Bengali-speakers get the English Wikipedia when they Google. A lot of them don't know about the Bengali Wikipedia, and still fewer that they can actually contribute to the site."

"Part of the problem is that Bengali is written in a non-roman script, and to edit you need software that supports this script. Many people don't have it, even though there are now increasingly satisfactory open-source tools, such as Avro Keyboard to which we have a link on our main page."

The regions where Bengali is spoken (the darker shade of red is Bangladesh)
Participants at the recent Bengali Wikipedia Conference held at the Independent University, Chittagong
Wikimedia's increasing global reach is encountering an old phenomenon in new and different ways: languages often don't map onto nation-states. The Bengali Wikipedia is a profound example of this: 160 million speakers live in Bangladesh, where Bengali is the only official language, and about 80 million live in West Bengal, a contiguous state on the eastern edge of India; tens of millions more live in adjacent Indian states to the north. So the national border lies athwart this huge group of people who share long and rich literary and cultural traditions.

But there have been tensions, some of them even recent; for example, Tanvir told us that over the past few years, the Indian government has been blocking the transmission of Bangladeshi television into West Bengal, reportedly citing fears of "anti-Indian" propaganda and coded messages to separatists (the Signpost cannot reliably confirm the details or whether the blocking persists).

Despite these hiccups, Tanvir says, there are obviously strong links between the groups. We asked him whether the Bengali Wikipedia has the potential to bring the two groups together in terms of free information and intellectual pursuit. He says that both Wikimedia India and Wikimedia Bangladesh have been active in supporting the Bengali Wikipedia (Tanvir played a key role in establishing the Bangladesh chapter, which has already begun outreach in the country). He points out that although India has some 400 languages, Bengali is its second most spoken native language, after Hindi. Bengali matters to both countries, and articles on the Wikipedia concern the whole language region.

Furthermore, Tanvir says, West Bengalis are welcome to collaborate with the Bangladesh chapter—anything, he says, that will develop the editing community. "There are possibilities for joint ventures with Wikimedia India on workshops, and we would be glad to help, although so far this has not occurred." On the Bengali Wikipedia, there are "very few" editors from West Bengal, although "one of the four active administrators is from West Bengal".

The project will comprise a number of overlapping phases. Initially, information and feedback will be collected regarding editing patterns and the basic needs of the community, including technical and social issues that might have a bearing on editor engagement. These findings will be analysed and pilot projects designed on welcoming and training new editors, and on the creation of an outreach program. The pilot programs will then be run, and outcomes reviewed, measured, and reported, leading to implementation in the longer term.

Tanvir says the project will open opportunities for transferring to other small wikis what we learn about attracting and retaining editors on one. "Communities may live in very different sociocultural circumstances, but there are likely to be common factors in all small wikis that enable us to formulate more robust strategies."

Dispute resolution

Another dimension of the editor retention narrative is dispute resolution, highlighted by last week's release of data suggesting that a surprising proportion of Wikipedians find the social milieu problematic, with 23% of respondents rating their fellow editors "arrogant", 13% "unfriendly", 7% "rude", 5% "dumb", and fewer than half "collaborative", among their top two descriptors (question 17). Steven Zhang, according to Bouterse, has "a passion for resolving on-wiki disputes and helping others to do the same". In June last year he was instrumental in setting up the dispute resolution noticeboard (DRN) on the English Wikipedia, and his fellowship will use this as the starting point for developing new tools and strategies to improve mediation.

We asked Steven how he would score the noticeboard out of 10; he says 6–7 might be a fair assessment at the moment. Previously "there were many entry points for dispute resolution, as though they'd grown without any planning at all. Unless you were a seasoned editor, you wouldn't know which one to go to. My whole purpose was to draw the system into a 'single capsule' for low-end disputes, and if a particular dispute needs to go somewhere else, to direct it there subsequently."

Steven Zhang, new community fellow on dispute resolution
The DRN has already made one of the low-end entry points somewhat redundant (the mediation cabal), but Steven is measured in his view of the task ahead: "Bad dispute resolution procedures", he says, "have a very negative effect on editor retention. However, there's no magic fix. The only thing that will maximise our success rate will be more people working in dispute resolution who've got the right knowledge. One of the advantages of the DRN is that it doesn't have to be as formal as the alternatives. People can just drop in and give advice without all of the strings attached to other forms of mediation. This format has been quite successful in attracting more editors into the field. Starting with just two people, we've now grown to more than 10."

What skills are necessary to work in dispute resolution, then? How do you get one religious or political group talking productively to their opposite number? "First, mediators need to know policy, because often disputants will quote policy, and you need to know your way around it yourself. But just as important, you have to look at a complex situation and clearly extract what the differences of approach are, separating the content issues from personal agendas. In the end, if they can't look at the situation objectively there may be nothing you can do, and it probably needs to go to another forum."

How much psychological insight is necessary? "You sometimes need to work out what the mind-sets of the parties are, and you can only do that by going into their edit histories. A lot of patience is required to succeed. Being aware of a number of typical scenarios might help both mediators and disputing parties to see their way through to resolution. For example, there's the ping-pong match, where participants don't listen to each other, the boomerang, where just bouncing back policy explanation does the trick, and the my source is better than yours dispute that can be solved by carefully working out how to present the different points of view in the article text. Then there's the compromise, where the final result is an amalgamation of opinions from parties, and the tough nut, disputes that would benefit from more formal mediation. You need to know when page protection may break the back of the dispute, and how to manage verbose editors, where tighter structure and intervention might work. Occasionally, a dispute has many issues and can be divided into components for better results.

Could admins play a greater role generally? "The problem for admins is that when a dispute is based on deep emotions—like some of the religious disputes I've mediated—they're reluctant to get involved. I think the admin and mediator hats are quite different. Being an enforcer and a mediator at the same time is a very hard thing to do. But having said that, experienced admins who have a detailed knowledge of policy and how to apply it can do a lot of good in resolving disputes."

"While on the issue of admins," says Steven, "I'll take this opportunity to say that I see a lot of RfAs where applicants are given a hard time for having less content creation experience than people think they should have; but my view is that dispute-resolution experience is a reasonable and valuable alternative to a lot of content editing."

As part of his fellowship, Steven will analyse the results of a survey of approximately 1,100 Wikipedians to determine the relationship between demographics and experiences of dispute resolution, and will collate opinions on how the process can be improved and who might be interested in participating as mediators. As part of the Wikimedia Fellow panel at Wikimania, he will outline the history of dispute resolution on the English Wikipedia, the results of his survey, and how they might feed into new strategies. In a related workshop at the unconference, he'll present developed case studies (anonymised) to compare how the audience believes the case should be resolved and how the case actually played out. He'll go on to create an online version so these test cases can be used by editors across foundation projects to improve their dispute resolution processes.

Brief notes

+ Add a comment

Discuss this story

These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.
  • Made a few small tweaks, but very well written. Thanks again :-) Steven Zhang Talk 02:22, 22 May 2012 (UTC)[reply]
  • Is it possible for someone clever to get rid of the massive gap in the middle of the article? After "our main page.", there's about 12 blank lines on my screen, presumably caused by the images. --Dweller (talk) 10:23, 22 May 2012 (UTC)[reply]
Dweller, I've asked at the Village pump for expert technical opinion. Tony (talk) 14:28, 22 May 2012 (UTC)[reply]
  • Please see User:Timeshifter/More articles and less editors. I have stopped nearly all my editing of Wikipedia article pages since early January. Yesterday was my first serious editing of a Wikipedia article in a long time. I still edit on the Commons, Wikia, Bugzilla, technical discussions, Village Pumps, talk pages, etc.. It is good that there is a dispute resolution noticeboard. Wikipedia:Dispute resolution noticeboard. I see that there is a Wikipedia:WikiProject Dispute Resolution too. That is a good idea too. The bottom line is that there are less active editors and more articles. I doubt that the number of active editors will increase. If the numbers do turn around, I doubt it will be by much. So that means content dispute resolution will have to become more efficient. It is way too time-consuming now. I agree that we need more people at lower levels of content dispute resolution. The bigger problem is the lack of accountable, efficient dispute resolution between average editors and admins. Admins are mainly only accountable to other admins, and even then only barely accountable. Objective observers of Wikipedia administration see it as another fanboy groupthink club where the vast majority of admins are male. Editors too. Wikipedia:Teahouse is an effort to counter that. Wikipedia mirrors society in its increasing control at the top by unaccountable leaders. Wikipedia refuses to truly deal with it, or to acknowledge the depth of the problem. Content dispute resolution oftentimes ends up with admin intervention. Since there is no definitive content resolution it oftentimes ends up in deadlock, or with admin arbitrariness. Editors leave due to both problems. --Timeshifter (talk) 13:19, 22 May 2012 (UTC)[reply]
    Dispute resolution does need to be more time-efficient, I agree. I have a few ideas that I am thinking over and might start chatting about it with a few people, and see if it's a viable option. Keep your eyes and ears open. No comment on admins - my perspective from what I've observed is that they do not participate in dispute resolution enough to have an impact on its outcome, but we of course are all entitled to our own opinion. Of course, my work will be focused on extracting the opinions of the community from the survey over my own, and putting something together to make dispute resolution more efficient, and to encourage more to get involved. That's my goal. Regards, Steven Zhang Talk 13:45, 22 May 2012 (UTC)[reply]
I suggest asking more survey questions concerning disputes with admins, and content disputes where admins get involved. That way it is not just my opinion or yours. The article says: "23% of respondents rating their fellow editors 'arrogant', 13% 'unfriendly'." There is also a certain percentage of admins that editors consider arrogant or unfriendly. That is got to effect content disputes too. Especially when admins step in as an enforcer instead of as a mediator. Admins frequently have to step in. WP:3RR, page protection, incivility warnings and blocks, and WP:Edit warring (a completely vague policy). Just thinking about some of my experiences with admins in the last year makes me question why I would want to do anything but the rare article edit until content dispute resolution is far more efficient. The quality of admin interactions has definitely gotten worse since I started editing Wikipedia in 2005. I sincerely hope your efforts and others succeed because then far fewer admin interactions would be needed. Due to its vagueness and arbitrariness WP:Edit warring is almost diabolically efficient in driving away active editors. It is inevitable that active editors will arrive at content disputes one after another especially as they edit more and more controversial topics. After a few arbitrary clueless rulings (oh, it happens often) by admins wielding WP:Edit warring even the most thick-skinned active editors just throw in the towel. Why bother? Admin power corrupts, WP:Edit warring corrupts absolutely. It is the perfect tool for rude admins who enjoy the fanboy groupthink cheers of their fellow clique of admins. The groupthink reminds me of the fanboy groupthink of spam fighters who arbitrarily remove external links. Wikipedia has become like gang warfare. The best editing lately is done by WikiProjects who can overcome rude admins. I just checked to see if you were an admin, Steven Zhang, and found out that you were not. I found this though: User:Steven Zhang/Disclosure. I think it qualifies you perfectly to help start the Admin Misconduct Noticeboard I proposed. Combined with the Dispute resolution noticeboard, the two noticeboards would greatly enhance editor retention. By the way, I am a bureaucrat on Wikia with over 35,000 edits there, and thoroughly understand wiki groupthink. --Timeshifter (talk) 06:51, 24 May 2012 (UTC)[reply]
I do not see how my past should affect my input on the project one way or another. I think we have two different ways for tackling the same problem here, but I also wonder if this is the proper venue to discuss such matters. My user talk page would likely be a better location for this discussion. Regards, Steven Zhang Talk 15:21, 24 May 2012 (UTC)[reply]
I apologize if I said anything offensive. I did not mean to. On the contrary, I think your background is a big plus. I can use your talk page too if you desire. But discussion here is more important in my opinion, because unless more and more people become knowledgeable about the existence of the problem, and see the difficulties in arriving at solutions, then progress may not occur. --Timeshifter (talk) 18:34, 24 May 2012 (UTC)[reply]
I'm not offended, I just don't think my past is really relevant in this situation. I am also curious as to how you have come to the conclusions that you describe above, and think that sort of discussion is one to have via my talk page. Regards, Steven Zhang Talk 01:31, 25 May 2012 (UTC)[reply]
  • Comment. I suggest removing the "In this issue" right sidebar in the discussion section here. Or make it a right-floating table instead of a sidebar. That way the comments are not squished into a narrow column. That is a problem when there are multiple replies with more and more indentation. --Timeshifter (talk) 06:54, 24 May 2012 (UTC)[reply]
    This is more appropriate at Wikipedia talk:Wikipedia Signpost as it's not related to the article. I consider the right margin important in visually differentiating the comments from the article. Comments can be viewed full-width on the talk page as normal. — Pretzels Hii! 18:53, 25 May 2012 (UTC)[reply]





       

The Signpost · written by many · served by Sinepost V0.9 · 🄯 CC-BY-SA 4.0