Jump to content

Wikipedia:Wikipedia Signpost/Single/2012-04-30

From Wikipedia, the free encyclopedia
The Signpost
Single-page Edition
WP:POST/1
30 April 2012

 

2012-04-30

Does Wikipedia Pay? The Consultant: Pete Forsyth

Does Wikipedia Pay? is an ongoing Signpost series seeking to illuminate paid editing and paid advocacy, for-profit Wikipedia consultants, editing public relations professionals, Conflict of Interest guidelines in practice, and the Wikipedians who work on these issues—by speaking openly with the people involved.
Last week we interviewed Silver Seren about his involvement with WikiProject Cooperation. For the second round of the series, The Signpost talked with Wikipedia editor, administrator, and former Wikimedia Foundation (WMF) employee Pete Forsyth, owner of the Wikipedia consulting firm Wiki Strategies. The way Forsyth describes it, consulting is altogether different than paid editing, notably for the lack of editing articles directly. Instead, he offers guidance to clients and instructs them about how to engage the community. Does he avoid the common traps of conflict of interest editing? Is this a model that could or should be extended? Can one actually make a living doing it? Much to consider in this week's interview ...
For a transcript of the unedited conversation, see below.

Related articles
Does Wikipedia pay?

How paid editors squeeze you dry
31 January 2024

"Wikipedia and the assault on history"
4 December 2023

The "largest con in corporate history"?
20 February 2023

Truth or consequences? A tough month for truth
31 August 2022

The oligarchs' socks
27 March 2022

Fuzzy-headed government editing
30 January 2022

Denial: climate change, mass killings and pornography
29 November 2021

Paid promotional paragraphs in German parliamentary pages
26 September 2021

Enough time left to vote! IP ban
29 August 2021

Paid editing by a former head of state's business enterprise
25 April 2021

A "billionaire battle" on Wikipedia: Sex, lies, and video
28 February 2021

Concealment, data journalism, a non-pig farmer, and some Bluetick Hounds
28 December 2020

How billionaires rewrite Wikipedia
29 November 2020

Ban on IPs on ptwiki, paid editing for Tatarstan, IP masking
1 November 2020

Paid editing with political connections
27 September 2020

WIPO, Seigenthaler incident 15 years later
27 September 2020

Wikipedia for promotional purposes?
30 August 2020

Dog days gone bad
2 August 2020

Fox News, a flight of RfAs, and banning policy
2 August 2020

Some strange people edit Wikipedia for money
2 August 2020

Trying to find COI or paid editors? Just read the news
28 June 2020

Automatic detection of covert paid editing; Wiki Workshop 2020
31 May 2020

2019 Picture of the Year, 200 French paid editing accounts blocked, 10 years of Guild Copyediting
31 May 2020

English Wikipedia community's conclusions on talk pages
30 April 2019

Women's history month
31 March 2019

Court-ordered article redaction, paid editing, and rock stars
1 December 2018

Kalanick's nipples; Episode #138 of Drama on the Hill
23 June 2017

Massive paid editing network unearthed on the English Wikipedia
2 September 2015

Orangemoody sockpuppet case sparks widespread coverage
2 September 2015

Paid editing; traffic drop; Nicki Minaj
12 August 2015

Community voices on paid editing
12 August 2015

On paid editing and advocacy: when the Bright Line fails to shine, and what we can do about it
15 July 2015

Turkish Wikipedia censorship; "Can Wikipedia survive?"; PR editing
24 June 2015

A quick way of becoming an admin
17 June 2015

Meet a paid editor
4 March 2015

Is Wikipedia for sale?
4 February 2015

Shifting values in the paid content debate; cross-language bot detection
30 July 2014

With paid advocacy in its sights, the Wikimedia Foundation amends their terms of use
18 June 2014

Does Wikipedia Pay? The Moderator: William Beutler
11 June 2014

PR agencies commit to ethical interactions with Wikipedia
11 June 2014

Should Wikimedia modify its terms of use to require disclosure?
26 February 2014

Foundation takes aim at undisclosed paid editing; Greek Wikipedia editor faces down legal challenge
19 February 2014

Special report: Contesting contests
29 January 2014

WMF employee forced out over "paid advocacy editing"
8 January 2014

Foundation to Wiki-PR: cease and desist; Arbitration Committee elections starting
20 November 2013

More discussion of paid advocacy, upcoming arbitrator elections, research hackathon, and more
23 October 2013

Vice on Wiki-PR's paid advocacy; Featured list elections begin
16 October 2013

Ada Lovelace Day, paid advocacy on Wikipedia, sidebar update, and more
16 October 2013

Wiki-PR's extensive network of clandestine paid advocacy exposed
9 October 2013

Q&A on Public Relations and Wikipedia
25 September 2013

PR firm accused of editing Wikipedia for government clients; can Wikipedia predict the stock market?
13 May 2013

Court ruling complicates the paid-editing debate
12 November 2012

Does Wikipedia Pay? The Founder: Jimmy Wales
1 October 2012

Does Wikipedia pay? The skeptic: Orange Mike
23 July 2012

Does Wikipedia Pay? The Communicator: Phil Gomes
7 May 2012

Does Wikipedia Pay? The Consultant: Pete Forsyth
30 April 2012

Showdown as featured article writer openly solicits commercial opportunities
30 April 2012

Does Wikipedia Pay? The Facilitator: Silver seren
16 April 2012

Wikimedia announcements, Wikipedia advertising, and more!
26 April 2010

License update, Google Translate, GLAM conference, Paid editing
15 June 2009

Report of diploma mill offering pay for edits
12 March 2007

AstroTurf PR firm discovered astroturfing
5 February 2007

Account used to create paid corporate entries shut down
9 October 2006

Editing for hire leads to intervention
14 August 2006

Proposal to pay editors for contributions
24 April 2006

German Wikipedia introduces incentive scheme
18 July 2005


More articles

How paid editors squeeze you dry
31 January 2024

"Wikipedia and the assault on history"
4 December 2023

The "largest con in corporate history"?
20 February 2023

Truth or consequences? A tough month for truth
31 August 2022

The oligarchs' socks
27 March 2022

Fuzzy-headed government editing
30 January 2022

Denial: climate change, mass killings and pornography
29 November 2021

Paid promotional paragraphs in German parliamentary pages
26 September 2021

Enough time left to vote! IP ban
29 August 2021

Paid editing by a former head of state's business enterprise
25 April 2021

A "billionaire battle" on Wikipedia: Sex, lies, and video
28 February 2021

Concealment, data journalism, a non-pig farmer, and some Bluetick Hounds
28 December 2020

How billionaires rewrite Wikipedia
29 November 2020

Ban on IPs on ptwiki, paid editing for Tatarstan, IP masking
1 November 2020

Paid editing with political connections
27 September 2020

WIPO, Seigenthaler incident 15 years later
27 September 2020

Wikipedia for promotional purposes?
30 August 2020

Dog days gone bad
2 August 2020

Fox News, a flight of RfAs, and banning policy
2 August 2020

Some strange people edit Wikipedia for money
2 August 2020

Trying to find COI or paid editors? Just read the news
28 June 2020

Automatic detection of covert paid editing; Wiki Workshop 2020
31 May 2020

2019 Picture of the Year, 200 French paid editing accounts blocked, 10 years of Guild Copyediting
31 May 2020

English Wikipedia community's conclusions on talk pages
30 April 2019

Women's history month
31 March 2019

Court-ordered article redaction, paid editing, and rock stars
1 December 2018

Kalanick's nipples; Episode #138 of Drama on the Hill
23 June 2017

Massive paid editing network unearthed on the English Wikipedia
2 September 2015

Orangemoody sockpuppet case sparks widespread coverage
2 September 2015

Paid editing; traffic drop; Nicki Minaj
12 August 2015

Community voices on paid editing
12 August 2015

On paid editing and advocacy: when the Bright Line fails to shine, and what we can do about it
15 July 2015

Turkish Wikipedia censorship; "Can Wikipedia survive?"; PR editing
24 June 2015

A quick way of becoming an admin
17 June 2015

Meet a paid editor
4 March 2015

Is Wikipedia for sale?
4 February 2015

Shifting values in the paid content debate; cross-language bot detection
30 July 2014

With paid advocacy in its sights, the Wikimedia Foundation amends their terms of use
18 June 2014

Does Wikipedia Pay? The Moderator: William Beutler
11 June 2014

PR agencies commit to ethical interactions with Wikipedia
11 June 2014

Should Wikimedia modify its terms of use to require disclosure?
26 February 2014

Foundation takes aim at undisclosed paid editing; Greek Wikipedia editor faces down legal challenge
19 February 2014

Special report: Contesting contests
29 January 2014

WMF employee forced out over "paid advocacy editing"
8 January 2014

Foundation to Wiki-PR: cease and desist; Arbitration Committee elections starting
20 November 2013

More discussion of paid advocacy, upcoming arbitrator elections, research hackathon, and more
23 October 2013

Vice on Wiki-PR's paid advocacy; Featured list elections begin
16 October 2013

Ada Lovelace Day, paid advocacy on Wikipedia, sidebar update, and more
16 October 2013

Wiki-PR's extensive network of clandestine paid advocacy exposed
9 October 2013

Q&A on Public Relations and Wikipedia
25 September 2013

PR firm accused of editing Wikipedia for government clients; can Wikipedia predict the stock market?
13 May 2013

Court ruling complicates the paid-editing debate
12 November 2012

Does Wikipedia Pay? The Founder: Jimmy Wales
1 October 2012

Does Wikipedia pay? The skeptic: Orange Mike
23 July 2012

Does Wikipedia Pay? The Communicator: Phil Gomes
7 May 2012

Does Wikipedia Pay? The Consultant: Pete Forsyth
30 April 2012

Showdown as featured article writer openly solicits commercial opportunities
30 April 2012

Does Wikipedia Pay? The Facilitator: Silver seren
16 April 2012

Wikimedia announcements, Wikipedia advertising, and more!
26 April 2010

License update, Google Translate, GLAM conference, Paid editing
15 June 2009

Report of diploma mill offering pay for edits
12 March 2007

AstroTurf PR firm discovered astroturfing
5 February 2007

Account used to create paid corporate entries shut down
9 October 2006

Editing for hire leads to intervention
14 August 2006

Proposal to pay editors for contributions
24 April 2006

German Wikipedia introduces incentive scheme
18 July 2005

Introduction

Pete Forsyth
Tell me about your background as a Wikipedian. When did you get started? What were your first edits and first impressions? What got you hooked?

I was first exposed to the Internet at college in 1992, and soon I was drawn to the collaborative and public benefit vision of the free software movement. I later built a wiki with colleagues at a local non-profit. Learning about wikis as part of a thriving real-world community was a formative experience. When I came to Wikipedia I found myself developing working relationships, and ultimately friendships, which greatly enriched my experience. My first project was to start the article Oregon's statewide elections, 2006. I was learning myself, and wanted to share my new knowledge with others.

When others began to improve on my work, I was hooked; it was exhilarating to see unambiguous signs that other people valued what I was doing, and wanted to carry it further.

How did you grow in the Wikipedia community to become an administrator and then work with the WMF?

I quickly found others working on Oregon-related content, including people I knew from local blogs. A few things that stoked my interest: attending open space–based conferences like BarCamp and RecentChangesCamp, and working with peers to reach out to the Oregon Historical Society [1] and the state legislature [2]. I shared my enthusiasm for Wikipedia with others in my personal and professional life, earning a reputation as a Wikipedia expert.

I began to meet Wikimedia Foundation staff in about 2008, and was flattered to learn that they followed the WikiProject Oregon blog we'd launched. They were interested in our outreach efforts. The foundation later hired me to help design a university program, which became known as the Wikipedia Public Policy Initiative. Through that work, students and professors around the world have begun to learn about Wikipedia, and I met some of the smartest and most dedicated people I know.

Wiki Strategies

When did you start Wiki Strategies? What was your motivation for doing so?

I'd been an Internet and communications consultant for several years, so it was probably inevitable that my Wikipedia interests and my professional interests would converge. I launched Wiki Strategies in 2009 (initially as a partnership with User:Esprqii, though we have amicably parted ways since). We both observed that as Wikipedia grew into a robust and widely known institution, new people and organizations were getting interested. We saw an opportunity with organizations that tried to engage with Wikipedia, but didn't get complete or useful answers through typical on-site interaction. Wikipedia's production model can be very unfamiliar, and a dedicated consultant can offer value through a customized introduction to the site.

How does Wiki Strategies deal with conflicts of interest?

Above all, we only work with clients who agree to disclose any conflict of interest, and approach any related editing in a collaborative, respectful way. We work with clients who agree to do things like stating their affiliation on their user page, and leaving notes on the article talk page and in "Wikipedia:" space when appropriate. Our clients appreciate the practical guidance about how to engage in ways that are ethical and consistent with Wikpedia's values and culture. They're happy to learn how to genuinely improve a highly regarded public resource. On a more pragmatic level, our model eliminates the risk that they will be "outed", because of the high degree of upfront disclosure. From a client's perspective, this translates to stability; there is less likelihood of something unexpected happening with an article months or years in the future, when an effort to openly build consensus has guided their work from the start.

What is the difference between being a paid editor and a "consultant"? What types of services do people pay your for?

As a consultant, my clients are explicitly interested in my expertise in Wikipedia, how it operates, and how to engage with it in effective and ethical ways. I would think "paid editor" encompasses areas where a company has already determined what they want to do, and are paying somebody to carry out a task. Not necessarily good or bad; but in a case like that, I would hope they have a thoughtful Wikipedian working on outlining the project upfront.

Do you ever edit articles that you are paid for directly?

I have never made an edit to an article on behalf of a client. (There's a slight chance I've fixed a typo, or similar, without thinking.) However, I routinely advise clients (and others, in my volunteer efforts) in how to edit articles in an open and respectful way. Typically, clients are "on the clock" while making those edits, and they clearly disclose what they are doing. Here is an example of a client's work. The history and talk page may give a better idea of how Wiki Strategies helps clients with articles about themselves.

If you don't edit articles directly, but you do edit the text of client drafts, can you be sure that your clients are not editing directly? If they were, does that mean you're paid editing by proxy? Do you provide guidance as to what clients should do next once you're done working with them?

I go to great lengths to set clear expectations with my clients prior to starting any paid work. I work closely with them through their first edits; if they were to stray significantly from what we agree on, that would just be weird – it would be a significant betrayal of a trust-based relationship we've both invested in. I suppose I'd end the project, and scratch my head about why they had hired me to begin with. When I look back at past clients' articles, I've never seen anything that raises any flags for me. In the few cases where they're still engaged, they're doing good work and being open about their identity.

What has surprised you about working with clients? What's the most common misunderstanding they hold about Wikipedia?

As a consultant, I have learned to ask a lot of questions and listen carefully when getting to know a prospective client. On Wikipedia, such discussions often get skipped over while we deal with massive quantities of information. I think as Wikipedians, it's tempting to focus on the worst-case scenario (inserting non-neutral material) rather than considering the broad range of reasons people and organizations might want to engage.
Nearly every organization I talk to expresses a strong appreciation for Wikipedia's commitment to neutral and factual information. They recognize that it's a fundamentally different model from other media, but generally don't understand fully how it's different. As the Internet has become more complex and interactive, I think it becomes more difficult for most people to distinguish even among the most popular sites they visit every day. I'm sometimes surprised by the specifics; for instance, I've heard this sort of thing many times: "Years ago, I just clicked an edit button and fixed a typo. But I'm sure that's been locked down now – you can't just edit any page without [insert hazy theory], right?" I'm actually more surprised by Wikipedians' assumptions about why an organization might be interested in Wikipedia.

Have you ever turned down a client?

Yes. I get inquiries from people and organizations who are marginally notable from time to time. I typically advise them that resources spent on making the case for notability are not a good investment, and are better spent on other kinds of earned media.

How much do you earn from your consulting? Is it your primary job? Enough for spending money? Quit your day job? Retire early?

All my income relates to Wikipedia; it's my day job. I am comfortable with my income, but I won't be rich any time soon.

At heart are you a regular Wikipedian who's paid for working on Wikipedia on the side, or a consultant who occasionally does editing unrelated to your company?

A Wikipedian, without hesitation. Yes, I believe it's important to maintain a strong connection to the volunteer-driven nature of the project, and I'm not sure there's a better way to do that than through volunteer work.

You've managed to do what many experienced Wikipedia editors would dream of, which is to make money around Wikipedia. Do you think your path is a feasible one for other editors?

As demand for services relating to Wikipedia grows, it's imperative that we point the way toward practical steps companies can take that are built on the site's core values and policies.
Absolutely. It's not only possible, but vitally important to the future of Wikipedia that engaged, experienced, and mission-driven Wikipedians develop consulting skills. It's not an easy path, and it's not for everyone; I've worked hard to get this far. But the demand for expert advice in how to engage with the biggest, most widely read body of work in human history is not going to subside. I will say, I don't have a lot of confidence in models where the consultant's focus is entirely around direct conflicts of interest. I try to work with clients who have an interest in improving a general topic area, building goodwill as a good "digital citizen," and/or learning something about online community engagement through an exploration of Wikipedia. I believe staying active in these areas, both in my paid work and as a volunteer contributor, is essential.

You're getting paid to do what many do for free. Is that fair? Can the community survive with a split between those who are volunteers and those who are employees?

I disagree, in two respects: (1) I continue to volunteer heavily, and I don't think I could be a very effective consultant if I didn't; and (2) my paid work is very unlike my volunteer work. At the core, it's about gaining an understanding of my client's strategic objectives (either as an organization, or on a specific project) and exploring where it does or doesn't align with the strategic objectives of Wikipedia/Wikimedia. I don't believe this is work that takes place routinely in the volunteer community. There are some excellent examples where it has, but I doubt very much if the Wikipedians who have done this sort of work as volunteers imagine themselves doing so in a volunteer capacity for any length of time.

No, I don't believe the community could survive a split of this kind. I believe it's essential that paid consultants act as, and be accepted as, members of the community. This means actively serving the site's mission to connect all humanity with the sum of all knowledge. Our community has always been diverse, with writers, software developers, photographers, Foundation staff, etc.; the fact that paid consultants have a different approach than volunteer editors shouldn't exclude them from the community. But effort on the part of consultants and of other Wikimedians is needed for the relationship to work well.

What is Wiki Strategies working on now and next?

My major projects are not ones where a conflict of interest is central. Our current focus is on broader projects. For instance, supporting volunteer improvement of a broad topic area, earning a reputation as a good digital citizen, or learning about online collaboration and publishing through engagement with the Wikipedia community. I believe such projects have a lot more potential, both to advance the Wikipedia mission and to have a positive impact for my clients. Currently, my two main projects involve helping organizations contribute to broad topic areas on Wikipedia (such as Consumer Reports [3] and the Open Education Collaborative Documentation Project [4]). These projects are exciting to me because I see great potential to build bridges between different groups that share core values, but approach their day-to-day work in very different ways. I have some side work advising on articles that involve more direct conflicts of interest (along the lines of the Pixetell example above), but it's not my central focus.

Companies and other organizations have rich and complex relationships with knowledge generation and dissemination. Some have vast archives of research that may be hidden from public view, only because they see no easy way to share them. Some have business models that would simply work better if the public had better access to factual information. Some may have good reason to worry about casual or inaccurate Wikipedia editing on the part of their employees, and want to learn what they can do. Encouraging and helping organizations to openly and respectfully explore how Wikipedia may relate to their efforts has become my central focus, so I no longer do many projects that focus on one, or a few, articles about a company itself. To read more about current projects, check out the Wiki Strategies blog.

Are you hiring?

No, but we are beginning to explore what kinds of tasks can be spread among sub-contractors. I would like to be in a position to hire Wikipedians in the next year.

Conflict of interest policy and practices

What do you think of Jimbo's strong stance against direct editing of articles by COI editors?

A strict prohibition on article editing for editors in a conflict of interest would go against healthy, everyday Wikipedia practice, and would have devastating consequences. Conflicts of interest are common, and only some of them involve money. They can be managed through ethical behavior and sound judgment. Striking the right balance can be a challenge, but new and experienced Wikipedians challenge themselves to value neutrality above their own opinions every day, often with excellent results. Numerous organizations have, and will increasingly develop, an interest in contributing to Wikipedia. If we were to prohibit them from ever editing articles, there would be two major results. In cases where directly editing an article is common, accepted practice (for instance, non-controversial edits), (1) we would throw away any ability to influence how they edit articles, and (2) we would create a situation where such edits could not be disclosed, for fear of being punished. We would effectively be promoting secrecy over disclosure and accountability.

In little over a decade, we've developed a new model of peer production, knowledge management, and publication. We have built the largest, most widely read body of work in human history. Along with these accomplishments comes responsibility: we have to help the people and organizations of the world understand how to make sense of Wikipedia, and how it relates to their work. We are "the encyclopedia anyone can edit." Establishing and adopting practices about how to do so is the way to stay true to that vision; excluding entire classes of people is not. To simply tell organizations "no, you can't participate" is not a practical or reasonable approach, doesn't align with day-to-day, normal practice on Wikipedia, and wouldn't align with our mission. At the core, it would be an abdication of our goal and responsibility to improve the way knowledge moves through society.

We are "the encyclopedia anyone can edit." Establishing and adopting practices about how to do so is the way to stay true to that vision; excluding entire classes of people is not.

Do you see a need for the community to keep out paid/PR/COI editors?

Wikipedia is founded on inclusion, not exclusion. While any serious Wikipedian should be concerned about the influence of special interests (monied or otherwise), excluding broad categories of contributors, whether from the entire project or from editing article content, is the wrong way to go. That kind of exclusion would go against everyday, healthy Wikipedia interaction, in which reasonable contributors engaging in respectful ways are treated well. It would also take us in a new direction, in which there are giant asterisks next to our core policies of Be Bold and Assume Good Faith.

It's reasonable to expect people with conflicts of interest to clearly disclose them, and to respect emerging consensus even if they don't like it; but it's not reasonable to treat them as second-class Wikipedians. What's more, every one of us has various conflicts of interest. Ideally, we develop skills that help us minimize the impact of those conflicts on a project devoted to neutral information. People in a professional role are no less capable of developing those skills than anyone else, but it would certainly be helpful if other organizations' policies toward Wikipedia were to develop in ways that fully support Wikipedia's mission. That aspiration is at the core of my consulting work.

How can the constructive paid editors be accommodated while still dealing with the unethical ones?

I am continually impressed with the efforts of Wikipedians to deal with counterproductive editing. But there is always room for improvement. I believe organizations that value Wikipedia for what it is can be important allies in that process. Their actions can be used to guide future efforts by other organizations; and their reports about positive experiences based in ethical practices can reach audiences difficult for Wikipedians to access directly. Above all, I believe it is of critical importance to develop strong and clear consensus that openness about one's affiliations is a key component of ethical engagement with Wikipedia. By "consensus," I don't mean mere agreement just among Wikipedians, but also among the general public, companies, non-profits, government entities, and thought leaders in general.

The world is learning to love and value Wikipedia. At the moment, the absence of clear and actionable guidelines about how to engage constructively leaves everything up to individual interpretation. Without those guidelines, much of that interpretation will be self-interested. Consider this: given a genuine choice, what organization would want to be perceived as an adversary of Wikipedia? By offering useful guidelines for organizations on how to engage in ethical and productive ways, we have a tremendous opportunity to influence organizational behavior. Strange as it may seem, ethical guidelines need not be formal or enforced to be useful and effective. My clients ask me all the time: "what's the right way to do it?" Through all the work we have done as Wikipedians, we have established our own authority and influence. We have more power to advance our mission through straightforward communication than we tend to realize.

There's a long list of scandals dating back to MyWikiBiz through WikiScanner and BellPottinger, in which COI editors have been exposed, blocked, embarrassed. If you were Gregory Kohs in 2006, would Jimbo have blocked you? Why do you think you are still in good standing with the encyclopedia?

The Bell Pottinger story provides a plain-as-day example of the risks inherent in a simplistic, short-sighted, and unethical approach to engaging with Wikipedia.([5][6]) As such it is valuable to us as a movement, and to businesses considering whether and how to engage with Wikpedia. By failing to think through the best way to engage with Wikipedia, Bell Pottinger let its clients down and exposed them to backlash. They created a situation where principled Wikipedians had no choice but to publicly criticize the firm and its practices, and reverse the damage. As for myself, I like to think I'm in good standing with the encyclopedia because I continue to advance its mission on a daily basis, in an open and collaborative way – both in my paid work and in a volunteer capacity.

Do you think WP:COI needs to be updated, promoted to policy, or demoted to essay status? Should policy prohibit direct editing by paid editors?

It's good as is. I especially appreciate the bolded sentence in the lead paragraph: "Where advancing outside interests is more important to an editor than advancing the aims of Wikipedia, that editor stands in a conflict of interest." The page is very useful in establishing relationships with my clients. It provides a clear picture of how conflicts of interest can be problematic for Wikipedia, without outright denying the possibility that a person with a COI might be able to make a valuable contribution.

Should COI disclosures be required for paid editors?

Creating a requirement, given the project's strong dedication to individual privacy and anonymity, strikes me as impractical in the extreme. I do think it's important to establish a strong consensus, extending far beyond Wikipedia's inner circles, that openness and transparency are critical to ethical and effective engagement with Wikipedia, especially when there is a clear conflict of interest. Clearly articulating the benefits of disclosure, and advancing it as common practice in numerous small ways, will ease tensions between Wikipedia and other entities. (I'm not advocating a fundamental change – there are tons of great anonymous editors – but I do think we would be better off if it were more the exception than the rule, moreso where conflicts of interest exist.)

Should editors be able to advertise their services *on* Wikipedia?

Advertisements are disallowed by policy. We've gotten really good at dealing with this in article space (e.g., "Company X makes product Y" is generally OK, but a graphic listing specific prices, slogans, etc. is not). If we weren't distracted by the "paid editor" component of this issue, I think we'd all agree the concept translates directly to user space. Mentioning a service in passing is one thing; boldly advertising it, with a rate, at the top of a user page -- that's something else entirely. That's advertising, and advertising is prohibited.

What do you think of recent efforts to improve relations between the PR industry/paid editors, and Wikipedia. I'm thinking of CREWE and WikiProject Cooperation in particular.

Improving relationships is always a worthy goal. But the interest public relations firms have in Wikipedia doesn't usually align strongly with Wikipedia's mission. I'd be somewhat surprised if a clear and positive path forward emerges from the PR industry; but I've been surprised by many things in my time as a Wikipedian, so I wouldn't rule it out completely! In my own business pursuits, however, I see better opportunities with other kinds of businesses and organizations.

The big picture

This model for continual improvement emerged from the discussions around the five year strategic plan for the Wikimedia movement.

What is your plan for the next five years with Wikipedia? What do you think its biggest challenges are, and how do you see the community addressing them?

As a participant in the Wikimedia strategic planning process, I take a great deal of pride in the five-year plan that emerged [7]. The dedication and creative energy of the community has always been essential to advancing the project. I'd like to see a Wikipedia where the community of contributors better reflects the diversity of the broader world, in all aspects; currently, the low representation of women and the global south in our contributor base strike me as major shortcomings. In building community around wikis, I've found that helping people understand the potential of the medium, and the values that have brought it to its present state, are vital ingredients. That's why I focus my efforts in these areas.

What's your favorite quote or piece of advice about Wikipedia?

In the occasional cynical moment, Valfontis' Law resonates pretty strongly! ("The amount of time and effort spent explaining policy and procedure to any user is inversely proportional to the likelihood that user will become a productive editor.") But overall, I'd have to go with the nutshell version of the Be Bold policy: "If you see something that can be improved, improve it!"

Full transcript of interview
The following discussion has been closed. Please do not modify it.


Introduction

Tell me about your background as a Wikipedian. When did you get started? What were your first edits and first impressions? What got you hooked?

I was first exposed to the Internet at college in 1992, and was captivated by the opportunities for global interaction and collaboration. The free software movement captured my attention in the late 1990s, mostly via Slashdot. I later built a wiki with fellow volunteers and staff at Free Geek (a Portland, Oregon-based charity rooted in free culture and building community). Learning about wikis as part of a thriving real-world community was a formative experience. When I came to Wikipedia, I wanted to find others who shared my interests. Developing good working relationships -- and ultimately friendships -- through the site greatly enriched the experience. My first project was to start the article Oregon's statewide elections, 2006. I was learning myself, and wanted to share the information I found so others could benefit. When others began to improve on my work, I was hooked; it was exhilarating to see unambiguous signs that other people valued what I was doing, and wanted to carry it further.

When others began to improve on my work, I was hooked; it was exhilarating to see unambiguous signs that other people valued what I was doing, and wanted to carry it further.

How did you grow in the Wikipedia community to become an administrator and then work with the WMF?

I quickly found others working on Oregon-related content. There was even a little overlap with people I knew from local blogs. A few things that stoked my interest: connecting with people in person, attending open space-based conferences like BarCamp and RecentChangesCamp, working with Wikipedians to reach out to organizations like the Oregon Historical Society [8] and the state legislature [9]. I was working as a consultant, so it was probably inevitable that my Wikipedia interests and my professional interests would converge. I took every opportunity to share my enthusiasm for Wikipedia with others in my personal and professional life, and earned a reputation as a Wikipedia expert. I wouldn't count attaining admin privileges as a major milestone. I think my efforts as a writer, editor, and in outreach are much more significant. I rarely introduce myself as a "Wikipedia administrator;" I think it conveys a misleading notion of hierarchy.

Wiki Strategies

When did you start Wiki Strategies? What was your motivation for doing so?

I launched Wiki Strategies in 2009 (initially as a partnership with User:Esprqii, though we have amicably parted ways since). I'd been working as an Internet and communications consultant for several years; we both observed that as Wikipedia grew into a robust and widely known institution, new people and organizations were getting interested. We saw an opportunity primarily with organizations that tried to engage with Wikipedia, but did not get complete or useful answers through typical on-site interaction. Wikipedia's production model is very unfamiliar to many people, and a dedicated consultant can offer value through a customized introduction to the site.

Now, I see more opportunity to advance Wikipedia's mission through deeper engagement with organizations, not merely working with marketing departments to improve their "own" articles. Companies and other organizations have rich and complex relationships with knowledge generation and dissemination. Companies often have a strong interest in improving public access to accurate, neutral, factual information, especially when the focus is not limited to their "own" articles. Encouraging and helping organizations to explore how Wikipedia may relate to their efforts has become my central focus. In the long run, it will be in everyone's interest if a relationship between Wikipedia and other branches of the company exists before any serious effort to work on content is begun.

How does Wiki Strategies deal with conflicts of interest?

Above all, we only work with clients who agree to disclose any conflict of interest, and approach any related editing in a collaborative, respectful way. We work with clients who agree to do things like stating their affiliation on their user page, and leaving notes on the article talk page and in "Wikipedia:" space when appropriate. We do not edit Wikipedia on their behalf. Our clients appreciate the practical guidance about how to engage in ways that are ethical and consistent with Wikpedia's values and culture. They are happy to learn how to genuinely improve a highly regarded public resource. On a more pragmatic level, our model eliminates the risk that they will be "outed," because of the high degree of upfront disclosure. From a client's perspective, this translates to stability; there is less likelihood of something unexpected happening with an article months or years in the future, when an effort to openly build consensus has guided their work from the start.

What is the difference between being a paid editor and a 'consultant'? What types of services do people pay your for?

I would say the central difference is this: as a consultant, my clients are explicitly interested in my expertise in Wikipedia, how it operates, and how to engage with it in effective and ethical ways. I would think "paid editor" encompasses areas where a company has already determined what they want to do, and are paying somebody to carry out a task. Not necessarily good or bad; but in a case like that, I would hope they have a thoughtful Wikipedian good working on outlining the project up front.

Do you ever edit articles that you are paid for directly?

I have never made an edit to an article on behalf of a client. (There's a slight chance I've fixed a typo, or similar, without thinking.) However, I routinely advise clients (and others, in my volunteer efforts) in how to edit articles in an open and respectful way. Typically, clients are "on the clock" while making those edits, and they clearly disclose what they are doing. Here is an example of a client's work. The history and talk page may give a better idea of how Wiki Strategies helps clients with articles about themselves.

'"If you don't edit articles directly, but you do edit the text of client drafts, which are later posted to Wikipedia, can you be sure that these clients are following COI best practices by disclosing their COI and seeking other editors to review the text--that your clients are not editing directly? If they were editing directly, does that mean you're paid editing by proxy?" Once, you're 'off the clock', do you provide guidance as to what clients should do next, or what not to do, like edit directly?

I go to great lengths to set clear expectations with my clients prior to starting any paid work. I work with those who are interested in my expertise and looking for guidance. I work closely with them through their first edits; if they were to stray significantly from what we agree upon, that would just be weird -- it would be a significant betrayal of a trust-based relationship we have both invested in. I suppose I would end the project, and scratch my head about why they had hired me to begin with. When I look back at past clients' articles, I have never seen anything that raises any flags for me. In the few cases where they're still engaged, they are doing good work, and being open about their identity.

I can think of one instance in which an associate of my client interfered with an edit. It wasn't anything of major consequence. But the integrity of our process, and of working within Wikipedia policy, was as important to my client as it was to me; as soon as I pointed it out, she took steps to have it undone.

What has surprised you about working with clients? What is the most common misunderstanding they hold about Wikipedia?

Nearly every organization I talk to expresses a strong appreciation for Wikipedia's commitment to neutral and factual information. They recognize that it's a fundamentally different model from other media, but generally don't understand fully how it's different. I am sometimes surprised by the specifics; for instance, I've heard this sort of thing many times: "Years ago, I just clicked an edit button and fixed a typo. But I'm sure that's been locked down now, you can't just edit any page without [insert hazy theory], right?" As the Internet has become more complex and interactive, I think it becomes more difficult for most people to distinguish even among the most popular sites they visit every day. As for misunderstandings, I'm actually more surprised by Wikipedians' assumptions about why an organization might be interested in Wikipedia. As a consultant, I have learned to ask a lot of questions and listen carefully when getting to know a prospective client. On Wikipedia, such discussions often get skipped over while we deal with massive quantities of information. I think as Wikipedians, it's tempting to focus on the worst-case scenario (inserting non-neutral material) rather than considering the broad range of reasons people and organizations might want to engage.

As a consultant, I have learned to ask a lot of questions and listen carefully when getting to know a prospective client. On Wikipedia, such discussions often get skipped over while we deal with massive quantities of information. I think as Wikipedians, it's tempting to focus on the worst-case scenario (inserting non-neutral material) rather than considering the broad range of reasons people and organizations might want to engage.

Have you ever turned down a client?

Yes. I get inquiries from people and organizations who are marginally notable from time to time. I typically advise them that resources spent on making the case for notability are not a good investment, and are better spent on other kinds of earned media.

Have you ever spoken with Jimmy Wales about your paid consulting?

Yes, but not in any great depth.

Have you ever been accused of having a COI? If so, how did you deal with it?

I was once attacked with a multi-page screed by an anonymous Wikipedia editor, who dug up every bit of information he could find about me and made multiple accusations about my motives. I didn't like it at all! It took some effort, but I resisted the urge to read it closely, or to respond in detail. I was deeply appreciative of the responses that came from other Wikipedians, who were all, I think, strangers to me. It was gratifying to know that such attacks were regarded as an attack on the site, in addition to being an attack on me as an individual. In the long run, it did a lot to strengthen my hope for the Wikipedia project as a whole.

How much do you earn from your consulting? Is it your primary job? Enough for spending money? Quit your day job? Retire early?

All my income relates to Wikipedia; it is my day job. I am comfortable with my income, but I won't be rich any time soon. However, my major projects are not ones where a conflict of interest is of central significance. Currently, my two main projects involve helping organizations contribute to broad topic areas on Wikipedia [such as Consumer Reports [10] and the Open Education Collaborative Documentation Project [[11]]. I have some side work advising on articles that involve more direct conflicts of interest (along the lines of the Pixetell example above) but it's not my central focus.

At heart are you a regular Wikipedian who gets paid for working on Wikipedia on the side, or a consultant who occasionally does editing unrelated to your company? A Wikipedian, without hesitation. Yes, I believe it's important to maintain a strong connection to the volunteer-driven nature of the project, and I'm not sure there's a better way to do that than through volunteer work. My expertise in how Wikipedia works is the single most important thing I can offer my clients; and because Wikipedia is tremendously complex and continually evolving, I find it absolutely essential to stay engaged in a variety of ways. Plus, I love my work with WikiProject Oregon and various Wikimedia projects -- it's personally fulfilling in important ways. I have learned and grown more through my involvement with Wikipedia than through any other life experience.

You've managed to do what many experienced Wikipedia editors would dream of, which is to make money around Wikipedia. Do you think your path is a feasible one for other editors?

Absolutely. It's not only possible, but vitally important to the future of Wikipedia that engaged, experienced, and mission-driven Wikipedians develop consulting skills. As demand for services relating to Wikipedia grows, it's imperative that we point the way toward practical steps companies can take that are built on the site's core values and policies. It's not an easy path, and it's not for everyone; I've worked hard to get this far. But the demand for expert advice in how to engage with the biggest, most widely read body of work in human history is not going to subside. I will say, I don't have a lot of confidence in models where the consultant's focus is entirely around direct conflicts of interest. I try to work with clients who have an interest in improving a general topic area, building goodwill as a good "digital citizen," and/or learning something about online community engagement through an exploration of Wikipedia. I believe staying active in these areas, both in my paid work and as a volunteer contributor, is essential to maintaining and continuing to build the expertise I offer to my clients.

It's not only possible, but vitally important to the future of Wikipedia that engaged, experienced, and mission-driven Wikipedians develop consulting skills. As demand for services relating to Wikipedia grows, it's imperative that we point the way toward practical steps companies can take that are built on the site's core values and policies.

You're getting paid to do what many do for free. Do you think that's unfair? Can the community survive with a split between those who are volunteers and those who are employees?

I disagree, in two respects: (1) I continue to volunteer heavily, and I don't think I could be a very effective consultant if I didn't; and (2) the paid work I do is very unlike my volunteer work. At the core, it's about gaining an understanding of my client's strategic objectives (either as an organization, or on a specific project) and exploring where it does or doesn't align with the strategic objectives of Wikipedia/Wikimedia. I don't believe this is work that takes place routinely in the volunteer community. There are some excellent examples where it has, but I doubt very much if the Wikipedians who have done this sort of work as volunteers imagine themselves doing so in a volunteer capacity for any length of time. No, I do not believe the community could survive a split of this kind. I believe it is essential that paid consultants act as, and be accepted as, members of the community. This means actively serving the site's mission to connect all humanity with the sum of all knowledge. Our community has always been diverse, with writers, software developers, photographers, Foundation staff, etc.; the fact that paid consultants have a different approach than volunteer editors shouldn't exclude them from the community. But effort on the part of consultants and of other Wikimedians is needed for the relationship to work well.

Are you hiring?

No, but we are beginning to explore what kinds of tasks can be spread among sub-contractors. I would like to be in a position to hire Wikipedians in the next year.

Conflict of interest policy and practices

What do you think of Jimbo's strong stance against direct editing of articles by COI editors?

A strict prohibition on article editing for editors in a conflict of interest would go against healthy, everyday Wikipedia practice, and would have devastating consequences. Conflicts of interest are common, and only some of them involve money. They can be managed through ethical behavior and sound judgment. Striking the right balance can be a challenge, but new and experienced Wikipedians challenge themselves to value neutrality above their own opinions every day, often with excellent results. Numerous organizations have, and will increasingly develop, an interest in contributing to Wikipedia. If we were to prohibit them from ever editing articles, there would be two major results. In cases where directly editing an article is common, accepted practice (for instance, non-controversial edits), (1) we would throw away any ability to influence how they edit articles, and (2) we would create a situation where such edits could not be disclosed, for fear of being punished. We would effectively be promoting secrecy over disclosure and accountability. In little over a decade, we have developed a new model of peer production, knowledge management, and publication. We have built the largest, most widely read body of work in human history. Along with these accomplishments comes responsibility: we have to help the people and organizations of the world understand how to make sense of Wikipedia, and how it relates to their work. We are "the encyclopedia anyone can edit." Establishing and adopting practices about how to do so is the way to stay true to that vision; excluding entire classes of people is not. To simply tell organizations "no, you can't participate" is not a practical or reasonable approach, doesn't align with day-to-day, normal practice on Wikipedia, and wouldn't align with our mission. At the core, it would be an abdication of our goal and responsibility to improve the way knowledge moves through society.

We are "the encyclopedia anyone can edit." Establishing and adopting practices about how to do so is the way to stay true to that vision; excluding entire classes of people is not.

Do you see a need for the community to keep out paid/PR/COI editors?

Wikipedia is a project founded on inclusion, not exclusion. While any serious Wikipedian should be concerned about the influence of special interests (monied or otherwise), excluding broad categories of contributors, whether from the entire project or from editing article content, is the wrong way to go. That kind of exclusion would go against everyday, healthy Wikipedia interaction, in which reasonable contributors engaging in respectful ways are treated well. It would also take us in a new direction, in which there are giant asterisks next to our core policies of Be Bold and Assume Good Faith. It's reasonable to expect people with conflicts of interest to clearly disclose them, and to respect emerging consensus even if they don't like it; but it's not reasonable to treat them as second-class Wikipedians. What's more, every one of us has various conflicts of interest. Ideally, we develop skills that help us minimize the impact of those conflicts on a project devoted to neutral information. People in a professional role are no less capable of developing those skills than anyone else; but it would certainly be helpful if other organizations' policies toward Wikipedia were to develop in ways that fully support Wikipedia's mission. That aspiration is at the core of my consulting work. Wikipedia is a place for everyone to share knowledge. If we lose sight of that, Wikipedia is in trouble.

How can the constructive paid editors be accommodated while still dealing with the unethical ones?

I am continually impressed with the efforts of Wikipedians to deal with counterproductive editing. But there is always room for improvement. I believe organizations that value Wikipedia for what it is can be important allies in that process. Their actions can be used to guide future efforts by other organizations; and their reports about positive experiences based in ethical practices can reach audiences difficult for Wikipedians to access directly. Above all, I believe it is of critical importance to develop strong and clear consensus that openness about one's affiliations is a key component of ethical engagement with Wikipedia. By "consensus," I don't mean mere agreement just among Wikipedians, but also among the general public, companies, non-profits, government entities, and thought leaders in general. The world is learning to love and value Wikipedia. At the moment, the absence of clear and actionable guidelines about how to engage constructively leaves everything up to individual interpretation. Without those guidelines, much of that interpretation will be self-interested. Wikipedia is an enormous and well loved global brand, strongly associated with values like inclusion and universal knowledge. Consider this: given a genuine choice, what organization would want to be perceived as an adversary of Wikipedia? By offering useful guidelines for organizations on how to engage in ethical and productive ways, we have a tremendous opportunity to influence organizational behavior. Strange as it may seem, ethical guidelines need not be formal or enforced in order to be useful and effective. My clients ask me all the time: "what's the right way to do it?" Through all the work we have done as Wikipedians, we have established our own authority and influence. We have more power to advance our mission through straightforward communication than we tend to realize.

There is a long list of scandals dating back to MyWikiBiz through WikiScanner and BellPottinger, in which COI editors have been exposed, blocked, embarrassed. If you were Gregory Kohs in 2006, would Jimbo have blocked you? Why do you think you are still in good standing with the encyclopedia?

The Bell Pottinger story provides a plain-as-day example of the risks inherent in a simplistic, short-sighted, and unethical approach to engaging with Wikipedia.([12][13]) As such it is valuable to us as a movement, and to businesses considering whether and how to engage with Wikpedia. By failing to think through the best way to engage with Wikipedia, Bell Pottinger let its clients down and exposed them to backlash. They created a situation where principled Wikipedians had no choice but to publicly criticize the firm and its practices, and reverse the damage. As for myself, I like to think I'm in good standing with the encyclopedia because I continue to advance its mission on a daily basis, in an open and collaborative way -- both in my paid work and in a volunteer capacity.

What do you think of recent efforts to improve relations between the PR industry/paid editors, and Wikipedia. I'm thinking of CREWE and WikiProject Cooperation in particular.

Improving relationships is always a worthy goal. But the interest public relations firms have interest in Wikipedia doesn't usually align strongly with Wikipedia's mission. I would be somewhat surprised if a clear and positive path forward emerges from the PR industry; but I've been surprised by many things in my time as a Wikipedian, so I wouldn't rule it out completely! In my own business pursuits, however, I see better opportunities with other kinds of businesses and organizations.

What do you think is a bigger problem, paid editing, or upaid advocacy? Do you think it's unfair that paid editors have a target painted on them while unpaid advocates can civilly push their point of view without consequence?

I think genuine adherence to Wikipedia's mission and policies is important, whether or not there is money changing hands. Many, or perhaps most, edits to Wikipedia involve some level of conflict of interest; we tend to work on articles where we hold some kind of opinion. Striking a balance between our own opinions and our commitment to a neutral point of view is a continual personal challenge for any serious Wikipedian. I believe an open exploration of how to best strike that balance, whether as an individual or as someone with an organizational affiliation, is in the best interest of the encyclopedia.

Do you think WP:COI needs to be updated, promoted to policy, or demoted to essay status? Should policy prohibit direct editing by paid editors?

I think the conflict of interest guideline is good as is. I especially appreciate the bolded sentence in the lead paragraph: "Where advancing outside interests is more important to an editor than advancing the aims of Wikipedia, that editor stands in a conflict of interest." The page is very useful in establishing relationships with my clients. It provides a clear picture of how conflicts of interest can be problematic for Wikipedia, without outright denying the possibility that a person with a COI might be able to make a valuable contribution.

Do you think COI disclosures should be required for paid editors?

Creating a requirement, given the project's strong dedication to individual privacy and anonymity, strikes me as impractical in the extreme. I do think it's important to establish a strong consensus, extending far beyond Wikipedia's inner circles, that openness and transparency are critical to ethical and effective engagement with Wikipedia, especially when there is a clear conflict of interest. Clearly articulating the benefits of disclosure, and advancing it as common practice in numerous small ways, will ease tensions between Wikipedia and other entities. (I'm not advocating a fundamental change -- there are tons of great anonymous editors -- but I do think we would be better off if it were more the exception than the rule, moreso where conflicts of interest exist.)

Should editors be able to advertise their services *on* Wikipedia?

Advertisements are disallowed by policy. We've gotten really good at dealing with this in article space (e.g., "Company X makes product Y" is generally OK, but a graphic listing specific prices, slogans, etc. is not). If we weren't distracted by the "paid editor" component of this issue, I think we'd all agree the concept translates directly to user space. Mentioning a service in passing is one thing; boldly advertising it, with a rate, at the top of a user page -- that's something else entirely. That's advertising, and advertising is prohibited.

The big picture

What is your plan for the next 5 years with Wikipedia? What do you think it's biggest challenges are, and how do you see the community addressing them?

This model for continual improvement emerged from the discussions around the five year strategic plan for the Wikimedia movmement.

As a participant in the Wikimedia strategic planning process, I take a great deal of pride in the five year plan that emerged.[14] The dedication and creative energy of the community has always been essential to advancing the project. I would like to see a Wikipedia where the community of contributors better reflects the diversity of the broader world, in all aspects; currently, the low representation of women and the global south in our contributor base strike me as major shortcomings. In building community around wikis, I have found that helping people understand the potential of the medium, and the values that have brought it to its present state, are vital ingredients. That's why I focus my efforts in these areas.

For the following list of problems--no visual editor, few women, poor editor retention, pending changes, lack of civility, BLP issues, vandalism, lack of global south editors--how would you rank them in order of urgency and importance, and where would paid/coi editing fit on that list?

I would put civility at the top of that list, but with the caveat that one person's "uncivil comment" might be another's "strong defense of the project's core values." There are seldom bright lines when it comes to what is or is not civil, but even so, it's really important that we remain committed to dealing with one another in civil and respectful ways. I believe the diversity of our editing base along many vectors (gender, economic status, organizational affiliations) will improve if we can make progress in the overall civility of our interactions. Improving the editing interface is very important, but we have gotten this far without it, so I wouldn't regard it as totally essential. And it may be possible to substantially improve the editing interface (for example, by suppressing templates except in an "advanced" mode) without needing a full-on "visual editor." I'm confident that good things will continue to come from the developer community, which I think is showing signs of becoming more effective in recent months and years. I believe organizations (both for-profit and non-profit) have a great deal of knowledge to offer a project seeking the "sum of all knowledge." Unlocking that potential in ways that serve the project's values and policies -- rather than undermining them -- is an interesting project to me, and one that I think will become increasingly important as organizational interest in Wikipedia grows.

What article or project are you most proud of in both your unpaid work and your paid work? What article or project was most controversial or unsuccessful, both in your unpaid work and your paid work? What did you learn from it?

In my work as a volunteer, I am very proud of having guided the process of bringing the Columbia River article to Featured Article status, though there is a great deal of credit due to the article's many other contributors. I also take a lot of pride in the work I've done in places like Meta wiki to categorize and improve the historical coverage of the Wikimedia movement. And leading events like edit-a-thons and GLAMcamp DC has been very rewarding as well. In my paid work, I researched and planned much of the Wikipedia Public Policy Initiative for the Wikimedia Foundation, and it's been very gratifying to see the results (a growing network of Wikipedia Ambassadors, establishment of an ongoing Wikipedia Education Program, etc.) My current main projects involve helping experts in health care [15] and in the open education movement [16] find the best ways to engage with Wikipedia. These projects are exciting to me because I see great potential to build bridges between different groups that share core values, but approach their day-to-day work in very different ways.

What's your favorite quote or piece of advice about Wikipedia?

In the occasional cynical moment, Valfontis' Law resonates pretty strongly! But overall, I'd have to go with the nutshell version of the Be Bold policy: "If you see something that can be improved, improve it!"



Reader comments

2012-04-30

Showdown as featured article writer openly solicits commercial opportunities

By adding this short note at the top of his user page, User:Cla68 has ignited strong and at times emotive reactions that have engulfed the discussion on paid editing over the past week, and introduced a debate on what editors may say on their user page about their professional activities. Cla68, a Wikipedian for more than six years, has 29 sole-nominated and four co-nominated FAs to his name, and a long-standing involvement in military history articles. Cla68’s user page was soon the scene of an edit-war by other editors, who alternately removed and reinstated the statement until the page was temporarily protected two days later.

The debate over the status of paid editing in the project has been simmering for more than two months in a trenchantly debated RfC that now comprises more than 90,000 words. The RfC is a new episode of a discussion that first peaked in 2009. Discussion has become more active since the release of hotly disputed external research findings covered in last week's Signpost. Cla68 has stated that Wikipedia's soapbox policy "does not prohibit announcing your services or availability to improve Wikipedia."

There really are ethical communications professionals who understand that I will crucify their clients in the media if they do not do the right thing. And there are those who do NOT get it, and banning them is the fastest and easiest thing to do."

Cla's action has prompted extensive discussion on Jimmy Wales’s talk page ("It makes me sick to my stomach"). Jimmy summarised his attitude of how the phenomenon of paid editing could be addressed in this statement: "The truth is that paid advocacy is significantly deterrable through a thoughtful set of policies that forbids direct article editing and encourages appropriate interaction with the community. It's really quite simple: follow a bright-line rule – no paid advocacy in article space – come to the discussion page."

Opinions on Jimmy's page were as mixed as elsewhere, and ranged from the measured to the uncivil. One editor said that Cla68 makes himself "sound like a whore". Some doubted that Cla68's action was anything more than provocative or sarcastic. Arguing from logic, one participant wrote, "How likely would you be to work for free in an environment where many people are getting paid for the same work?" On the other hand, another said, "a complete banning of paid editing would just lead to media complaints of hypocrisy that paid editors are banned, but those editors with extreme COI issues (often high ranking Wikipedia members as well) are allowed to roam free." In one editor's view, "It is far too late to pretend that Cla68 is responsible for the current ruckus. His provocation was only possible thanks to years of studied inattention." Others were concerned with the analogy with BLPs who edit their own articles, or with a different bright line: "Jimbo is clearly distinguishing between paid editors and paid advocates. The latter should be banned the former not. I agree with that."

In news that may have implications for the current debates, The Signpost has been informed that a university has approached Cla68 and is negotiating a contract with him to write a set of articles about their researchers; this has now been confirmed with the university itself. The details of whether or how many of these articles will be nominated as featured article candidates are still to be determined between the parties.

Two ANI threads

"Looks like a pretty effective troll to me. Par for the course for this particular editor."

The conflagration has now spread across at least five other pages on the English Wikipedia, each showing how divided the community is on the issue. An ANI thread was launched that did not appear to distinguish between the issues of paid editing and user-page advertising. Within hours it contained a huge variety of community opinions. One editor said: "if you force him to remove it, you've removed an important disclosure that does more good than harm. It's called, shooting yourself in the foot. I'd rather know who is paid to edit." Another participant commented: "I also stumbled across an editor yesterday whose User page described his work in photography for Wikipedia, with links to contact him at his business. (Looked like nice work, too.) Unless the WMF says otherwise, I'm not seeing much reason to take up arms on this one. Advertising one's Wikipedia-related work on their Userpage has apparently been accepted by the community, through disinterest if nothing else."

This ANI thread was closed as a "no admin action", a closure that was almost immediately disputed. Another ANI thread was opened, this time with the explicit theme of "asking the community to affirmatively address specifically whether there is consensus to disregard policy and allow an advertisement on this user page." This thread was closed with the summary, "Regardless of your feeling on paid COI, there's a RfC and a MfD where this can be properly discussed, and this is getting very silly here, let's stop it."

MfD and edit-war

"The post on Jimbo's talk page was especially helpful in getting the word out. Jimbo's talk page is likely the most watched user talk page in Wikipedia."

The "MfD" referred to is a request to delete Cla's user page. Among the comments was a query as to how Jimmy Wales's mention on his user page of his for-profit Wikia company—which includes contact details—is acceptable if other users are forbidden from providing information about their wikipedia-related commercial activities. At the start of Tuesday UTC, the MfD has attracted 18 calls for Cla68's user page to be deleted, a further 14 for the "advertisement" alone to be removed (that is, 32 combined), and 38 calls for the page and "advertisement" to be kept.

On Monday 29 April UTC, the MfD page was subjected to a rapid-fire edit-war in which an attempt to speedy-close it was reverted, reinstated, reverted, and reinstated, all within nine minutes. The MfD has now been closed, with the summary, "Keep per WP:FORUMSHOP. This has been taken to ANI twice and closed due to no consensus. Brought up at Jimbo's talk page. And an RfC. ... easy call."

RfC at the user-page guideline

The request for comment was launched at the guideline on user pages. The proposal is to add a bullet to the current guideline that restricts what may appear on user pages (see below; our italicisation).

Promotional and advocacy material and links
  • Advertising or promotion of an individual, business, organization, group, or viewpoint unrelated to Wikipedia (such as commercial sites or referral links).
  • Advertising or promotion of a product, service, or any other for-profit, money-making venture, regardless of its relationship to Wikipedia.
  • Extensive self-promotional material, especially when not directly relevant to Wikipedia.

The argument is that "the wording of the first bullet point is ambiguous. It can be interpreted in a way that conflicts with WP:NOTADVERTISING, implying that it's ok to advertise products and services, as long as they are related to Wikipedia. ... It is not the intent of this proposal to decide whether paid editing (or otherwise making money from Wikipedia-related activities) is acceptable, nor is it the intent of this proposal to limit an editor's ability to disclose that they are a paid editor."

At the time of writing, there are 13 supports, one provisional support, and nine opposes. The comments have included queries concerning whether Pete Forsyth (who is interviewed in the current edition of The Signpost), would need to remove from his user page the link and reference to his consulting business, Wiki Strategies, in which he advises on "opportunities to engage with the Wikipedia community in accordance with its policies and culture."

Other pages

Opinion was mixed as well at the off-wiki Facebook site CREWE (Corporate Representatives for Ethical Wikipedia Engagement). Among the reactions were: “I'm quite sure that there's far more people on the 'meh, who cares' side and the 'how you edit matters, not why' side than the banning side.”; “This was a pretty obvious attempt to provoke a reaction rather than a serious attempt to drum up business as a paid editor by 'advertising services' on CLA's 'User Page.' "; and “Even I'll say that using a userpage to advertise services is kind of shady.”

There is currently a related proposal at the Village Pump that new articles on commercial businesses must have at least one independent reliable source, as for BLPs.

In brief

Visualization of the answers to the question: What is your gender? The darkest colour represents ... men.
  • Terms of Use update: A link to the new version of the foundation's Terms of Use (Signpost coverage) has appeared on a banner since April 25. Points regarding the TOU can be raised on Meta until May 25, when the old version will be replaced by the new one.
  • Gender gap persists: The WMF published survey results from a sample of 6503 on the state of gender equality and the dominance of the English Wikipedia among WMF projects on April 27 in its blog. Nine out of 10 editors are male; but the news is that the proportion of females among new editors has risen year by year: 8% in 2008, 9% in 2009, 10% in 2010, and 14% last year. There were generally no significant variations across the major language Wikipedias, although as outliers, 15% of US editors and only 6% of Russian editors are women. While only 30 percent primarily edit the English Wikipedia, 63% contribute to it. Almost half of English Wikipedia editors report other language Wikipedias as their primary project, and a remarkable 86% of all Wikipedia editors read the English Wikipedia. The blog contains a link to more information and has provision for comments by users.
  • Wikipedian in residence at Harvard: Details of a Stanton Foundation–funded Wikipedian in residence fellowship at the Belfer Center for Science and International Affairs have been published.
  • Wikimania scholarships: A statement on this year's Wikimania scholarships, providing insights into the results, has been published in the WMF's blog on April 25.
    From the April 23 Wikipedia Academy Oslo 2012
  • Editor Growth and Contribution Program: The concept and a FAQ of the WMF's new Editor Growth and Contribution Program (Signpost coverage) has been published on Meta.
  • US Wikipedia Education Program figures: Survey results from 132 students participating in the (northern) Fall 2011 program who returned the survey were published in the WMF's blog on April 23.
  • Wikipedia Academy in Norway: The annual event in Oslo took place on April 23 and Haakon, Crown Prince of Norway and Jimmy Wales took part in it to celebrate the new Wikipedia Zero-partnership between Telenor and the WMF (Signpost coverage).
  • New administrators: The Signpost welcomes a new administrator, Dennis Brown. He is a long-time editor who, in the words of conominator Pedro, is "a well rounded courteous and dependable editor who learns from rare mistakes." Dennis intends to apply his new tools at CSD and in anti-vandalism work.
    Ilokano population distribution; the Ilokano language, an Austronesian language related to such languages as Indonesian, Malay, Fijian, and Maori, ranks third in the Philippines in terms of the number of native speakers. The Ilokano Wikipedia reached a milestone this week.

  • Milestones: The following Wikipedia projects reached milestones this week:

2012-04-30

Barnstars work; Wiktionary assessed; cleanup tags counted; finding expert admins; discussion peaks; Wikipedia citations in academic publications; and more

A monthly overview of recent academic research about Wikipedia and other Wikimedia projects, edited jointly with the Wikimedia Research Committee and republished as the Wikimedia Research Newsletter.
The relative number of edits by Wikipedians who had randomly received barnstars (red) and by the control group whose members hadn't (blue).

Recognition may sustain user participation

To gain insight in what makes Wikipedia tick, two researchers from the Sociology Department at Stony Brook University conducted an experiment with barnstars.[1] They were surprised by what they found.

Professor Arnout van de Rijt and graduate student Michael Restivo wanted to test the hypothesis according to which receiving recognition for one's work in an informal peer-based environment such as Wikipedia has a positive effect on productivity. To test their hypothesis, they determined the top 1% most productive English Wikipedia users among the currently active editors who had yet to receive their first barnstar. From that group they took a random sample of 200 users. Then they randomly split the sample into an experimental group and a control group, each consisting of 100 users. They awarded a barnstar to each user in the experimental group; the users in the control group were not given a barnstar. The researchers found their hypothesis confirmed: the productivity of the users in the experimental group was significantly higher than that of the control group. What really took the researchers by surprise was how long-lasting the effect was. They followed the two groups for 90 days, observing that the increase in contribution level for the group of barnstar recipients persisted, almost unabated, for the full observation period.

One major factor the experiment did not take into account was whether it mattered who delivered barnstars and whether they were anonymous, registered, or known members of the Wikipedia community. During the experiment, it was noted on the Administrator's noticeboard/Incidents page that a seemingly random IP editor was "handing out barnstars", which led to some suspicion from Wikipedians. The thread was closed after User:Mike Restivo confirmed he accidentally logged out when delivering the barnstars. He did not, however, declare his status as a researcher, and the group's paper does not disclose that the behavior was considered unusual enough to warrant such a discussion thread.

Can Wiktionary rival traditional lexicons?

Wiktionary received an extensive assessment[2] as a potential rival to expert-built lexicons.

A chapter titled "Wiktionary: a new rival for expert-built lexicons?"[2] in a collection on electronic lexicography to appear with Oxford University Press contains a description and critical assessment of Wikipedia's second oldest sister project (which will celebrate its 10th anniversary in December this year) – subtitled "Exploring the possibilities of collaborative lexicography", which it calls a "fundamentally new paradigm for compiling lexicons".

The article describes in detail the technical and community features of Wiktionary. Though it is not immediately clear, the article's focus is on several language editions and not just English (as often happens in research about Wikipedia and its sister projects). The article gives a comprehensive account of the coverage of the world's languages by the various Wiktionary language editions. There is a critical analysis of Wiktionary's content, first with what appears to be a thorough statistical comparison with other dictionaries and wordnets, including an examination of the overlaps in the lexemes covered, which the authors found to be surprisingly small.

Number of native terms (p.17) Wiktionary wordnets Roget's Thesaurus OpenThesaurus
English language 352,865 148,730 (WordNet) 59,391
German language 83,399 85,211 (GermaNet) 58,208
Russian language 133,435 130,062 (Russian WordNet)

The article notes an important characteristic of open wiki projects: they allow "updating of the lexicons immediately, without being restricted to certain release cycles as is the case for expert-built lexicons" (p. 18). Though this characteristic is obvious to experienced Wikimedians, it is frequently overlooked. The discussion of the organization of polysemy and homonymy is comprehensive, although limited to the English Wiktionary. Other language editions may do it differently. The article notes that "it is a serious problem to distinguish well-crafted entries from those that need substantial revision by the community", which is good constructive criticism. The paragraphs about "sense ordering" make some vague claims (e.g. "Although there is no specific guideline for the sense ordering in Wiktionary, we observed that the first entry is often the most frequently used one") which could be interesting and useful from a community perspective, but offers little actionable evidence and should be investigated further. The paper's conclusions identify some of the features that enable Wiktionary to rival expert-built lexicons: "We believe that its unique structure and collaboratively constructed contents are particularly useful for a wide range of dictionary users", listing eight such groups – among them "Laypeople who want to quickly look up the definition of an unknown term or search for a forum to ask a question on a certain usage or meaning."

On a critical note, the last paragraph says "we believe that collaborative lexicography will not replace traditional lexicographic theories, but will provide a different viewpoint that can improve and contribute to the lexicography of the future. Thus, Wiktionary is a rival to expert-built lexicons – no more, no less", which sounds a bit contradictory. The authors also note that "Lepore (2006: 87) raised a criticism about the large-scale import of lexicon entries from copyright-expired dictionaries such as Webster's New International Dictionary". It would be nice if the authors would write at least a short explanation of the problem that Lepore described. But the actual article[3] mentions Wiktionary only very briefly. For the most part, the article is a good academic-grade presentation of Wiktionary: it is very general and does not dive too much into details; it makes a few vague statements, but they present a good starting point for further research.

Wikipedia as an academic publisher?

Can Wikipedia integrate with open-access scholarly publishing?

Xiao and Askin (2012) looked at whether academic papers could be published on Wikipedia.[4] The paper compares the publishing process on Wikipedia to that of an open-access journal, concluding that Wikipedia's model of publishing research seems superior, particularly in terms of publicity, cost and timeliness.

The biggest challenges for academic contributions to Wikipedia, they found, revolve around the level of acceptance of Wikipedia in academia, poor integration with academic databases, and technical and conceptual differences between an academic article and an encyclopedic one. However, the paper suffers from several problems. It correctly observes that the closest a Wikipedia article comes to a "final", fully peer-reviewed status is after having passed the featured article candidate process, but makes no mention of intermediary steps in Wikipedia's assessment project, such as B-class, Good Article and A-class reviews; nor is the assessment project itself mentioned. Despite its focus on the featured-article process, no previous academic work on featured articles is cited (although quite a few have been published). Crucially, the paper disregards the most relevant of Wikipedia's policies, no original research. Thus, the study fails to consider whether Wikipedia would want to publish academic articles without their undergoing changes to bring them closer to encyclopedic style – a topic that already has become an issue numerous times on the site, in particular regarding difficulties encountered by some educational projects. In the end, the paper, while a well-intentioned piece, seems to illustrate that university researchers can have a quite different understanding of what Wikipedia is than those more closely connected with the project.

In other news, however, a scientific journal appears to have found a viable way to publish peer-reviewed articles on Wikipedia: The open access journal PLoS Computational Biology has announced[5] that it is starting to publish "Topic Pages" - peer-reviewed texts about specific topics, which are published both in the journal and as a new article on Wikipedia. It is hoped that the Wikipedia versions will be updated and improved by the Wikipedia community. The first example is about circular permutation in proteins.

Wikipedia citations in American law reviews

Volume 1 of the Harvard Law Review (1887–1888).

The article "A Jester's Promenade: Citations to Wikipedia in Law Reviews , 2002–2008" concerns the issue of citations of Wikipedia in US law reviews and the appropriateness of this practice.[6] The article seems to be well researched, and its author, law reference/research librarian Daniel J. Baker, demonstrates familiarity with the mechanics of Wikipedia (such as the permanent links). For the period 2002–08, Baker identified 1540 law-review articles that contain at least one citation of Wikipedia – most in law reviews dealing with general and "popular" subject matter, with a significant proportion originating from authors with academic credentials.

The article notes that 2006 marked the peak of that trend, attributing it (thereby demonstrating some familiarity with Wikipedia's history) to a delayed reaction to the Seigenthaler incident and the Essjay Controversy. (Since the article's data analysis ends in 2008, the question of whether this trend has rebounded in recent years is left unanswered.)

The author is highly critical of Wikipedia's reliability, arguing that a source that "anyone can edit" – and where much of the information is not verified – should not be used in works that may influence legal decisions. Thus Baker calls for stricter rules in legal publishing, in particular that Wikipedia should not be cited. In a more surprising argument, the paper suggests that if information exists on Wikipedia, it should be treated as common knowledge, and thus does not require referencing (a recommendation that follows a 2009 one – Brett Deforest Maxfield, "Ethics, politics and securities law: how unethical people are using politics to undermine the integrity of our courts and financial markets", 35 OHIO N.U. L. REV. 243, 293 (2009)). This argument does, however, raise the question of whether no citation at all is truly better than a citation to Wikipedia; if such a recommendation were followed, it could lead to a proliferation of uncited claims in law review journals that would be assumed (without any verification) to rely on "common knowledge" as represented in the "do not cite" Wikipedia.

One in four of articles tagged as flawed, most often for verifiability issues

A paper titled "A Breakdown of Quality Flaws in Wikipedia"[7] examines cleanup tags on the English Wikipedia (using a January 2011 dump), finding that 27.53% of articles are tagged with at least one of altogether 388 different cleanup templates. In a 2011 conference poster [8] (a version of which was summarized in an earlier edition of this newsletter), the authors analyzed – together with a third collaborator – a 2010 dump of the English Wikipedia for a smaller set of tags, arriving at a much lower ratio: "8.52% [of articles] have been tagged to contain at least one of the 70 flaws". Using a classification of Wikipedia articles into 24 overlapping topic areas (derived from Category:Main topic classifications), the highest ratio of tagged articles were found in the "Computers" (48.51%), "Belief" (46.33%) and "Business" (39.99%) topics; the lowest were in "Geography" (19.83%), "Agriculture" (22.57%) and "Nature" (23.93%). Of the 388 tags on the more complete list, "307 refer to an article as a whole and 81 to a particular text fragment". As another original contribution of the paper, the authors offer an organization of the existing cleanup tags into "12 general flaw types" – the most frequent being "Verifiability" (19.46% of articles have been tagged with one of the corresponding templates), "Wiki tech" (e.g. the "orphan", "wikify" or "uncategorized" templates; 5.47% of articles) and "General cleanup" (2.01%).

Time evolution of Wikipedia discussions

Kaltenbrunner and Laniado look at the time evolution of Wikipedia discussions, and how it correlates to editing activity, based on 9.4 million comments from the March 12, 2010 dump.[9] Peaks in commenting and peaks in editing often co-occur (for sufficiently large peaks of 20 comments, 63% of the time) within two days. They show the articles with the longest comment peaks and most edit peaks, and the 20 slowest and 20 fastest discussions.

The authors note that a single, heavy editor can be responsible for edit peaks but not comment peaks; peaks in the discussion activity seem to indicate more widespread interest by multiple people. They find that "the fastest growing discussions are more likely to have long lasting edit peaks" and that some editing peaks are associated with event anniversaries. They use the Barack Obama article as a case study, showing peaks in comments and editing due to news events as well as to internal Wikipedia events (such as an editor poll or article protection). Current events are often edited and discussed in nearly real-time in contrast to articles about historical or scientific facts.

They use the h-index to assess the complexity of a discussion, and they chart the growth rate of the discussions. For instance, they find that the discussion pages of the three most recent US Presidents show a constant growth in complexity but that the rate of growth varies: Bill Clinton's talk page took 332 days to increase h-index by one, while George W. Bush's took only 71 days.

They envision more sophisticated algorithms showing the relative growth in edits and discussions. Their ideas for future work are intriguing – for instance, the question of how to determine article maturity and the level of consensus, based on the network dynamics. (AcaWiki summary)

APWeb2012 papers on admin networks, mitigating language bias and finding "minority information"

Several of the accepted papers of this month's Asia-Pacific Web Conference APWeb2012 concerned Wikipedia:

  • Prototype tool searches for expert admins: In the article "Exploration and Visualization of Administrator Network in Wikipedia",[10] four Chinese authors examine the collaboration graph of administrators on the English Wikipedia (where two of them are connected by an edge if they have edited the same article during the sampled time span from January 2010 to January 2011), and "define six features to reflect the characteristics of administrator’s work from different respects including diversity of the admin user interests, the influence & importance across the network, and longevity & activity in terms of contribution." The authors observe that the recognition of an admin's work by other users in the form of barnstars seems to agree with the overall rank they calculate from these quantities: "By analyzing the profiles of the top ranked fifty admin users as a test case, it has been observed that the number of barn stars received by them also follows the similar trend as we overall ranked the admin users."To extract topics from an admin's history and define diversity, Latent Dirichlet allocation (LDA) is used. The authors describe a prototype software called "Administrator Exploration Prototype System", which displays these various quantitative measures for an admin and allows ranking them. In particular, it "will automatically find the expert authors based on the editing history of each admin user". An example screenshot shows a list of results for a "Search for "Expert Admin User" for the keywords "Music, Songs, Singers", topped by Michig, Mike Selinker and Bearcat. Analyzing the whole network, the authors find a "decreasing trend of the clustering coefficient [which] can also be seen as a symptom of the growing centralization of the network." Overall, they observe that "the administrator network is a healthy small world community having a small average distances and a strong centralization of the network around some hubs/stars is observed. This shows a considerable nucleus of very active administrators who seems to be omnipresent."
  • Not what the majority of readers search for under "football": A goalball game
    Detecting "minority information" on Wikipedia: A paper[11] by two Japanese researchers proposes "a method of searching for minority information that is less-acknowledged and has less popularity in Wikipedia" for a given keyword. "For example, if the user inputs ‘football’ as a majority information keyword, then the system seeks articles having a sentence of “....looks like football....” or similar content of articles about soccer in Wikipedia. It extracts as candidates for minority sports those articles which have few edits and few editors. Then, it performs sports filtering and extracts minority articles from the candidates. In this case, the results are ‘Bandy’, ‘Goalball’, and ‘Cuju’." The authors constructed a prototype system and tested it.
  • Completing Wikipedia articles with information from other language versions: In an article titled "Extracting Difference Information from Multilingual Wikipedia"[12], four Japanese researchers describe a "method for extracting information which exists in one language version [of Wikipedia], but which does not exist in another language version. Our method specifically examines the link graph of Wikipedia and structure of an article of Wikipedia. Then we extract comparison target articles of Wikipedia using our proposed degree of relevance." As motivating example, they note that the English Wikipedia's coverage of the game cricket is much fuller than the Japanese Wikipedia's, but spread over separate articles beyond just the main one at cricket. The goal is a system where a (Japanese) user can enter a keyword and will receive the "Japanese article with sections of English articles that do not appear in the Japanese article".

Briefly

  • The proportion of "good faith" and "golden" editors among new contributors over time has remained constant.[13]
    Unchanged quality of new user contributions over time. GroupLens PhD candidate Aaron Halfaker (who also collaborates with the Wikimedia Foundation as a contractor research analyst) shared some preliminary results on the quality of new user contributions,[13] part of a larger study currently submitted for publication. The results, based on an analysis of revert rates in the English Wikipedia combined with blind assessment of a new editor contribution history, indicate that new editors have produced the same level of quality in their first contributions since 2006. Despite the fact that "the majority of new editors are not out to obviously harm the encyclopedia (~80 percent), and many of them are leaving valuable contributions to the project in their first editing session (~40 percent)", today's user experience for a first-time editor is much more hostile than it used to be, as "the rate of rejection of all good-faith new editors’ first contributions has been rising steadily, and, accordingly, retention rates have fallen. These results challenge the hypothesis that today’s newbies produce much lower quality contributions than in earlier years.
  • Modeling Wikipedia's community formation processes. An important factor behind the success of Wikipedia is its own internal culture. Like any social group, a community of peer production has its own rules, norms, and customs. Unlike traditional social groups -- a recently-defended doctoral dissertation in computer science argues -- the process of formation of these traits involves, and often determines, how contents are being produced. The dissertation, defended by former Summer of Research fellow and Wikimedia Foundation contractor analyst Giovanni Luca Ciampaglia,[14] uses computer simulation to study how the community of Wikipedia may have formed its specific cultural traits and distinctive sociological features. Starting from the distribution of user account lifespan in five of the largest Wikipedia communities (English, German, Italian, French, and Portuguese) this work shows how the statistical patterns of the data can be reproduced by a simple model of cultural formation based on principles taken from self-categorization theory and social judgment theory.
    Distribution of AFT ratings for articles in different project quality assessment categories.[15]

    The research finds that an important factor to determine whether a community will be able to sustain itself and thrive is the degree of openness of individual users towards differing points of view, which may be critical in the early stages of user participation, when a newcomer first enters in contact with the body of social norms that the community has devised. The thesis concludes that simulation techniques, when supplemented with empirical methods and quantitative calibration, may become an important tool for conducting sociological studies.
  • Matching reader feedback via the Article Feedback Tool to editor peer review: An upcoming presentation at Wikimania 2012[15] compares data gathered from the Article Feedback Tool (AFT) version 4 on the English Wikipedia over summer 2011 to ratings assigned by various peer review processes, e.g. good and featured articles. As might be expected, articles at any point in the peer review process tend to be rated more highly by reviewers, but this distinction is highly sensitive to the article length. Once length is accounted for (using a variety of methods), the differences between demoted or not promoted articles and unrated articles disappears. The research also offers a broad snapshot of the AFT dataset as well as some suggestions for future AFT design. Future revisions of the draft as well as the presentation will approach the dynamic relationship between peer reviewed status and reader feedback, exploiting entry and exit into various categories for identification.
  • Referencing of Wikipedia in academic works is continuing unabated: An article in the "Research Trends" newsletter published by the bibliographical database Scopus, titled "The influence of free encyclopedias on science"[16] charts the number of papers in Scopus that are either about Wikipedia or cite it. Considering that Wikipedia was only founded in 2001 (i.e. that these numbers have necessarily started from zero right before the observed timespan), the author's astonishment at the compound annual growth rates for both kinds of papers from 2002 to 2011 (which she calls "staggering" and "unbelievable", respectively) is somewhat surprising, but the article also gives the growth rates for the five years from 2007 to 2011 (ca. 19% per year for Wikipedia as a subject, ca. 31% per year for Wikipedia as a reference). Interestingly, Scholarpedia is showing itself to be the second most popular online encyclopedia to be cited, if lagging significantly behind Wikipedia (5%).
  • Using Wikipedia to drive traffic to library collections: In an article titled "Wikipedia Lover, Not a Hater: Harnessing Wikipedia to Increase the Discoverability of Library Resources"[17] in the Journal of Web Librarianship, two librarians from the University of Houston Libraries and a former intern report how they had successfully used Wikipedia to drive traffic to the collection of the institution's digital services department (UHDS), proceeding from merely inserting links into articles to uploading images from the collection to Commons (which still contain such link on the file description pages): "Originally, UHDS intended to contribute exclusively to the External Links section of existing Wikipedia articles. [However, over time] UHDS staff found it was much more effective to match digital items with Wikipedia articles and to share those items in Wikimedia Commons (WMC) rather than (or in addition to) the External Links section of the articles." While few statistics are given, the authors emphasize the effectiveness of their actions, observed already for the very first attempts: "Within hours of posting external links to existing Wikipedia articles, the digital library received hits to those collections at a surprisingly high rate." As an example of an article enriched with such images, the entry 1915 Galveston hurricane is named. Among the successful additions to external links section is the article about former US president George H. W. Bush, where the student intern linked a photograph showing Bush shaking hands with former University of Houston chancellor Philip G. Hoffman (as already noted in the Signpost's April 2011 coverage after the authors had presented their project at the annual meeting of the Association of College and Research Libraries: "Experts and GLAMs – contributing content or 'just' links to Wikipedia?"). Much of the paper describes basic technicalities of Wikipedia: The uploading of image, the use of contributions lists, talk pages and watchlists. While Wikipedia's external links guidelines are not cited in the paper, it notes that "contributing effectively to Wikipedia and WMC entailed a steep learning curve in order to align contributions with the granular and well-enforced Wikipedia guidelines for use", and among them notices policies against advertising. As one unresolved problem for such institutional usage of Wikipedia and Commons, the paper describes the prohibition "to share an editor username with other editors, and [that] organizational usernames are considered a violation of Wikipedia guidelines forbidding the promotion of organizations. When the pilot project transitioned into a permanent departmental program, UHDS staff struggled to devise a way that others on staff could continue to monitor previous edits and uploads and create new ones", e.g. due to the lack of shared watchlists.
  • Weekly and daily activity patterns discern Wikipedia from commercial sites: Two Finnish researchers analyzed[18] the distribution of timestamps in the recent changes RSS feed from four different language versions (Arabic, Finnish, Korean, and Swedish - Arabic having been chosen because its speakers are spread over "a very wide range of timezones", in contrast to the other three), and RSS new feeds from BBC World News "and the leading Finnish daily newspaper Helsingin Sanomat". As the main difference between the activity on those two sites (which the authors describe as "commercial news sites") and on the Wikipedias, it was found that Wikipedia edits "distribute fairly equally over all days in all cases. The drop of activity on weekends that occurred with the commercial news services is not visible in the Wikipedias, quite the opposite, with Sundays typically seeing the highest average level of activity. Only the Arabic version has a slightly lower activity rate in Sundays, however, we should remember the fact that in Arabic countries the weekend falls on Friday-Saturday or in some countries on Thursday-Friday". The diurnal patterns are found to be "more spread out" on Wikipedia, where "the activity levels follow natural diurnal rhythms. Interestingly, a great number of changes are made during working hours, which leads us to 2 different, but not mutually exclusive, conjectures about the people who edit Wikipedia. Either, the editors are people with “free” time during the day, e.g., students, or people actually edit Wikipedia during the working hours at work. Our methodology is not able to answer this question".
    Furthermore, the authors offer a rather far-reaching but (if proven) significant conjecture based on their date: "Cultural and geographical differences in the Wikipedias we studied seemed to have very little effect on the level of activity. This leads us to speculate that the 'trait' of editing Wikipedia is something to which individuals are drawn, not something specific to certain cultures."
    Last year, papers by two other teams (covered in the September issue of this newsletter: Wikipedians' weekends in international comparison", but missing from the "Related work" section of the present paper) had similarly examined daily and weekly patterns on Wikipedia, coming to other results - in particular, different language Wikipedias showed different weekly patterns.
  • Simple English Wikipedia is only partially simpler/controversy reduces complexity: "A practical approach to language complexity: a Wikipedia case study"[19] analyzed samples of articles from the English Wikipedia and the Simple English Wikipedia from the end of 2010 with respect to the Gunning fog index as well as other measures for language complexity. Comparing them with other corpora including Charles Dickens' books, they observe that "Remarkably, the fog index of Simple English Wikipedia is higher than that of Dickens, whose writing style is sophisticated but doesn’t rely on the use of longer latinate words which are hard to avoid in an encyclopedia. The British National Corpus, which is a reasonable approximation to what we would want to think of as ‘English in general’ is a third of the way between Simple and Main, demonstrating the accomplishments of Simple editors, who pushed Simple half as much below average complexity as the encyclopedia genre pushes Main above it." However, the number of distinct tokens used (a measure for vocabulary richness) is almost the same on the English and Simple Wikipedia (the samples were chosen to be of the same size). Still "detailed analysis of longer units (n-grams rather than words alone) shows that the language of Simple is indeed less complex". In another finding, the authors "investigate the relation between conflict and language complexity by analysing the content of the talk pages associated to controversial and peacefully developing articles, concluding that controversy has the effect of reducing language complexity."
  • Contributions from South America. "Mapping Wikipedia edits from South America",[20] the latest from a series of studies and visualizations by Oxford Internet Institute researcher Mark Graham and his team, reports that almost half of all edits to Wikipedia from South America come from Brazil, which is unsurprising considering that the largest population of Internet users in South America lives in Brazil. More interestingly, Chile –- a country with only 5-6% of the continent's Internet population -- contributes more than 12% of edits to Wikipedia.
  • Deaths generate edit bursts: A student paper titled "Death and Change Tracking : Wikipedia Edit Bursts"[21] examines the editing activity in nine articles about celebrity actors on the English Wikipedia after they died.
  • Searching by example: This month's WWW 2012 conference in Lyon, France saw a demo titled "SWiPE: Searching Wikipedia by Example"[22], showcasing a tool where the user can search for articles similar to a given one by modifying entries in that article's infobox, and also ask questions in natural language.
  • Wikipedia in the eyes of PR professionals. A study published in the journal of the Public Relations Society of America (PRSA)[23] surveyed public relations and communications professionals about their perception of Wikipedia contribution and conflict of interest. The online survey was pilot-tested with members of the Corporate Representatives for Ethical Wikipedia Engagement (many of whom have recently pushed for Wikipedia to let PR professionals edit articles about their clients to a greater extent) and produced 1,284 usable responses after being disseminated via various outlets. The results indicate that "of the 35% who had engaged with Wikipedia, most did so by making edits directly on the Wikipedia articles of their companies or clients". The response time to issues reported on talk pages was found to be one of the important barriers in the interaction between Wikipedia community members and PR professionals. The author observes that "when the wait becomes too long, the content is defamatory, or a dispute with a Wikipedian needs to be elevated, there are resources to help. Unfortunately, only a small percentage of the respondents in this study had used them and many had never heard of these resources". As another argument against the "bright line" rule advocated by Wikipedia's Jimmy Wales (which says that PR professionals should not edit Wikipedia articles they are involved in), a separate result of the paper has been offered, which has met with heavy criticism by Wikimedians regarding statistical biases and other issues (see e.g. last week's Signpost coverage: "Spin doctors spin Jimmy's 'bright line'"): 32% of the respondents said that "there are currently factual errors on their company or client’s Wikipedia articles", corresponding to 41% of those respondents who said that such articles existed, or 60% of those respondents who said that such articles existed but did not reply "don't know" to that question. The press releases of the author's college and of PRSA interpreted the result as "Sixty percent of Wikipedia articles about companies contain factual errors", although the latter was updated after the criticism "to clarify the survey findings described in this press release and help prevent any misinterpretation of the data that this release may have caused".
  • Wikipedia coverage of marketing terms found accurate: The proceedings of the recent "International Collegiate Conference Faculty" of the American Marketing Association (AMA) offer a more positive view on Wikipedia from PR professionals: "Is Wikipedia A Reliable Tool for Marketing Educators and Students? A Surprising Heck Yes!".[24] The paper chose a more systematic way to examine the quality of Wikipedia articles than the PRSA study and focused on AMA's area of expertise, starting out from a "random sample of marketing glossary terms [that] were collected from 3 marketing management textbooks and 4 marketing principles textbooks", and rating corresponding Wikipedia entries from 1 to 3 according to a standard procedure for content analysis: "Each textbook definition was compared to the corresponding Wikipedia definition and rated using a 3-point Likert scale where 1=Correct Definition, 2=Correct but difficult to find the term or the definition was not easy to decipher, or 3=Incorrect definition when compared to the textbook term.". Of 459 items in the eventual sample only five were rated 3, and "the average score across all textbooks was a 1.18 demonstrating Wikipedia is an accurate source of marketing content."
  • Wikipedia's osteosarcoma coverage assessed: An abstract published in the Journal of Bone & Joint Surgery[25] finds "that the quality of osteosarcoma-related information found in English Wikipedia is good but inferior to the patient information provided by the National Cancer Institute". The abstract refers to a study and results that appear to be identical to the one reported in a 2010 viewpoint article in the Journal of the American Medical Informatics Association (JAMIA) (Signpost coverage).
  • Wikipedia assignments for Finnish school students: A paper by three Finnish authors[26] describes course assignments to upper secondary school students (age 16–18) involving "writing articles for Wikipedia (a public wiki) and for the school’s own wiki", in subject areas including biology, geography and Finnish history. In particular the paper reports that "a carefully planned library [visit] can help to activate students to use printed materials in their source-based writing assignments. [And that our] findings corroborate the generally held view that students tend to copy-paste and plagiarise, especially when exploiting Web sources."
  • Wikipedia as a thermodynamic system - becoming more efficient over time: A paper titled "Thermodynamic Principles in Social Collaborations"[27] (presented at this month's Collective Intelligence 2012 conference) applies principles and concepts from Statistical mechanics to the collaboration on (the English) Wikipedia. The analogy is based on interpreting the edit count of a user as the energy level of a particle, positing a "logarithmic energy model" for edits which assumes a "decreasing effort required for a given user to make additional edits in a relatively short period of time (e.g., one month) or to a particular page". (According to the authors this contrasts with two other theories which also explain the observed power law distribution of edit counts: The "Wikipedia editors are 'born'" notion, which assumes that different users need to expend different amounts of energy on the same kind of edits due to "an extreme heterogeneity of preference among the potential user population", and the "Wikipedia editors are 'made'" notion, which sees positive or negative feedback from other users as the defining influence.) Using the analogy, the authors define the entropy, free energy, temperature, entropy efficiency and entropy reduction of an editing community and their edits during a particular timespan. They then calculate the latter two for each month in the English Wikipedia's history from January 2002 to December 2009. They conclude that "Wikipedia has become more efficient in terms of entropy efficiency, and more ordered according to entropy reduction. The increasing power-law coefficient causes the shift of the contributions from elites to crowd. The saturation of free energy reduction ratio may cause the saturation of the active editors." The next section finds that "entropy efficiency is correlated with the quality of the social collaboration", and one figure is interpreted as implying "that the nature of Wikipedia is a true media of the masses, where pages produced by crowd wisdom will have higher quality and thus more readership compared to that produced by a few elites."
  • Too many docs don't spoil the broth: Another paper[28] presented at the Collective Intelligence 2012 conference similarly found "that the number of contributors has a curvilinear relationship to information quality, more contributors improving quality but only up to a certain point" - based on an examination of 16,068 articles in the realm of the WikiProject Medicine.
  • The most influential biographies vary depending on the language/culture: Barcelona Media Foundation studied "the most influential characters" in the 15 largest language Wikipedias[29], by asking which biographies are the most linked to ("central") from other Wikipedia biography articles. Political and artistic biographies are the most central, and the particular biographies depend on the language. They found, for instance, that Shakespeare's biography is among the most important for Russian, Chinese, Spanish, and Dutch, but not for English. And they estimated the Jaccard similarity coefficient (similarity) between the social networks in different language editions: most similarity can be explained by language-family and geographical or historical ties. One interesting finding is that Dutch "seems to serve as a bridge between different language and cultural groups". Some social connections are very common, and they produce a graph of the connections found in at least 13 of the language editions. The authors note that articles on people from non-Anglo-Saxon cultures may be missing if they are not known internationally, since the initial list of notable people is extracted from DBPedia. A blog post on Technology Review highlighted the fact that in the paper's table of most connected biographies (listing the top 5 from 15 language versions), among the 75 entries "only three are women: Queen Elizabeth II, Marilyn Monroe and Margaret Thatcher", which it interprets as one of "The Worrying Consequences of the Wikipedia Gender Gap". (Summary at AcaWiki)
Biographical social network of the connections between persons present in at least 13 of the 15 largest language Wikipedias, as described in Aragón et al.[29]

References

  1. ^ Restivo, M. & van de Rijt, A. (2012). Experimental Study of Informal Rewards in Peer Production. PLoS ONE 7(3): e34358. PDFDOI Open access icon
  2. ^ a b Meyer, C. M., & Gurevych, I. (2012). Wiktionary: a new rival for expert-built lexicons? Exploring the possibilities of collaborative lexicography. In S. Granger & M. Paquot (Eds.), Electronic Lexicography. Oxford: Oxford University Press. PDF Open access icon
  3. ^ Lepore, J. (2006). Noah's Mark, The New Yorker, November 6, 2006, pp. 78-86. HTML Open access icon
  4. ^ Xiao, L., & Askin, N. (2012). Wikipedia for Academic Publishing: Advantages and Challenges. Online Information Review, 36(3), 2. Emerald Group Publishing Limited. HTML Closed access icon
  5. ^ Wodak, S. J.; Mietchen, D.; Collings, A. M.; Russell, R. B.; Bourne, P. E. (2012). "Topic Pages: PLoS Computational Biology Meets Wikipedia". PLOS Computational Biology. 8 (3): e1002446. Bibcode:2012PLSCB...8E2446W. doi:10.1371/journal.pcbi.1002446. PMC 3315447. PMID 22479174. Open access icon
  6. ^ Baker, D. J. (2012). A Jester's Promenade: Citations to Wikipedia in Law Reviews, 2002–2008. I/S: A Journal of Law and Policy for the Information Society, 7(2):1–44. PDF Open access icon
  7. ^ Anderka, M., & Stein, B. (2012). A breakdown of quality flaws in Wikipedia. Proceedings of the 2nd Joint WICOW/AIRWeb Workshop on Web Quality – WebQuality '12 (p. 11). New York: ACM Press. DOIPDF Open access icon
  8. ^ Anderka, M., Stein, B., & Lipka, N. (2011). Towards automatic quality assurance in Wikipedia. Proceedings of the 20th international conference companion on World Wide Web – WWW '11. New York: ACM Press. DOIPDF Open access icon
  9. ^ Kaltenbrunner, A., & Laniado, D. (2012). There is No Deadline – Time Evolution of Wikipedia Discussions. ArXiV. Computers and Society; Physics and Society. PDF Open access icon
  10. ^ Yousaf, J., Li, J., Zhang, H., & Hou, L. (2012). Exploration and Visualization of Administrator Network in Wikipedia. In: Q. Z. Sheng, G. Wang, C. S. Jensen, & G. Xu (Eds.), Web Technologies and Applications, Lecture Notes in Computer Science 7235:46-59. Berlin, Heidelberg: Springer Berlin Heidelberg. DOI Closed access icon
  11. ^ Hattori, Y., & Nadamoto, A. (2012). Search for Minority Information from Wikipedia Based on Similarity of Majority Information. In: Q. Z. Sheng, G. Wang, C. S. Jensen, & G. Xu (Eds.) Web Technologies and Applications, Lecture Notes in Computer Science 7235:158-169. Berlin, Heidelberg: Springer Berlin Heidelberg. DOI Closed access icon
  12. ^ Fujiwara, Y., Suzuki, Y., Konishi, Y., Nadamoto, A., Sheng, Q., Wang, G., Jensen, C., et al. (2012). Extracting Difference Information from Multilingual Wikipedia. In: Q. Z. Sheng, G. Wang, C. S. Jensen, & G. Xu (Eds.) Web Technologies and Applications, Lecture Notes in Computer Science 7235:496-503. Berlin, Heidelberg: Springer Berlin Heidelberg. DOIClosed access icon
  13. ^ a b Halfaker, A. (2012). Kids these days: the quality of new Wikipedia editors over time. Wikimedia Foundation blog. HTML Open access icon
  14. ^ Ciampaglia, G. L. (2011). User participation and community formation in peer production systems. PhD Thesis, Università della Svizzera Italiana PDF Open access icon
  15. ^ a b Hyland, A. (2012). Comparing article quality by article class and article feedback ratings. Wikipedia. HTML Open access icon
  16. ^ Huggett, S. (2012). The influence of free encyclopedias on science. Research Trends, (27). HTMLOpen access icon
  17. ^ Elder, D., Westbrook, R. N., & Reilly, M. (2012). Wikipedia Lover, Not a Hater: Harnessing Wikipedia to Increase the Discoverability of Library Resources. Journal of Web Librarianship, 6(1), 32-44. Routledge. DOI Closed access icon
  18. ^ Karkulahti, O., & Kangasharju, J. (2012). Surveying Wikipedia activity: Collaboration, commercialism, and culture. The International Conference on Information Network 2012 (pp. 384-389). IEEE. DOI Closed access icon
  19. ^ Yasseri, T., Kornai, A., Kertész, J. (2012). A practical approach to language complexity: a Wikipedia case study. ArXiv. Computation and Language. PDF Open access icon
  20. ^ Graham, M. (2012). Mapping Wikipedia edits from South America. Zero Geography. HTML Open access icon
  21. ^ Lincoln, M. (2012). Death and Change Tracking : Wikipedia Edit Bursts. PDF Open access icon
  22. ^ Atzori, M., & Zaniolo, C. (2012). SWiPE: Searching wikipedia by example. Proceedings of the 21st international conference companion on World Wide Web - WWW '12 Companion (p. 309). New York, New York, USA: ACM Press. DOIPDF Open access icon
  23. ^ DiStaso, M. W. (2012). Measuring Public Relations Wikipedia Engagement: How Bright is the Rule? Public Relations Journal, 6(2) HTML Open access icon
  24. ^ Gray, D. M., & Peltier, J. (2012). Is Wikipedia Reliable Tool for Marketing Educators and Students? A Surprising Heck Yes! Marketing Always Evolving. 34th Annual International Collegiate Conference. PDF Open access icon
  25. ^ Leithner, A., Maurer-Ertl, W., Glehr, M., Friesenbichler, J., Leithner, K., & Windhager, R. (2012). Wikipedia and Osteosarcoma: An educational opportunity and professional responsibility for Emsos. Journal of Bone & Joint Surgery, BR, 94-B(SUPP XIV), 13. British Editorial Society of Bone and Joint Surgery. HTML Closed access icon
  26. ^ Sormunen, E., Eriksson, H., & Kurkipäa, T. (2012). Wikipedia and wikis as forums of information literacy instruction in schools. The Road to Information Literacy: Librarians as Facilitators of Learning. IFLA 2012 Congress Satellite Meeting (pp. 1-23). PDF Open access icon
  27. ^ Peng, H.-K., Zhang, Y., Pirolli, P., & Hogg, T. (2012). Thermodynamic Principles in Social Collaborations. ArXiV. Physics and Society. PDF Open access icon
  28. ^ Kane, G. C., & Ransbotham, S. (2012). Collaborative Development in Wikipedia. ArXiv. PDF Open access icon
  29. ^ a b Aragón, P., Kaltenbrunner, A., Laniado, D., & Volkovich, Y. (2012). Biographical Social Networks on Wikipedia - A cross-cultural study of links that made history. ArXiV. Computers and Society; Physics and Society, PDF Open access icon


Reader comments

2012-04-30

'ReferenceTooltips' by default

ReferenceTooltips

Reference Tooltips (stylized as "ReferenceTooltips") allows a user to roll over any inline citation to see reference information, instead of having to jump away from the article text. Yair rand is the initiator of the current discussion to allow inline citation pop-ups to appear by default rather than as a user preference.

Proposal

At the moment, to enable ReferenceTooltips, any logged-in editor can go to My preferencesGadgets → and click ReferenceTooltips.

Alternatively, any logged-in editor can manually install the script into their skin.js or their common.js page:

importScript('User:Yair rand/ReferenceTooltips.js');
importStylesheet('User:Yair rand/ReferenceTooltips.css');.

The proposal is to make this choice the default, so all editors have this gadget. Any editor who does not want it can then disable it in their preference panel.

Discussion

At the time of writing, there were 17 support votes and 5 oppose votes for this proposal. The support votes are mainly driven by the fact that it would make references more usable. For example, instead of clicking on a reference and then jumping to the bottom of the page to find the reference, ReferenceTooltips enables the user to move their mouse over the reference and read the information. The oppose votes are compelled by the technical limitations of ReferenceTooltips and how the pop-ups would make the Wikipedia experience worse. For instance, enabling the reference to pop-up by mere hovering will cause pop-ups all over the place if an editor is just scrolling through a page. In addition, there are concerns that browsers will block the pop-up as an advertisement.

Some suggestions to avert a technical mishap are to only enable a reference to pop-up when the user clicks the inline citation. Still, all of the oppose votes believe that most editors won't use the reference tool and only researchers would be able to use this tool. The oppose voters believe that ReferenceTooltips should be left as an opt-in tool or gadget rather than being available by default as many editors would find it obtrusive.

Voting

In favour of supporting the gadget by default, an argument provided by Silver seren was: "Yes! This would be extremely useful, rather than having to hit back to go to the spot you were in the article before you clicked it. This way, [you] can tell beforehand if it's a reference you will actually want to click into. Furthermore, it lets you know directly which reference that number is referring to, without having to go to the reference list. [ReferenceTooltips] [h]elps you understand the narrative of the article and its references without a bunch of back and forth clicking."

A contention provided by Nageh opposing the proposal (but later moved to "Weak oppose/neutral") was: "The vast majority of unregistered readers give a damn about references. They just want their information and they are done. Also, popups can easily become an annoyance, and they usually annoy me, too, even though I actually like this tool. That does not mean it should be activated by default. Leave it as an opt-in tool, as it is now, and anyone registered and really interested in this additional functionality can easily activate it."

Reader comments

2012-04-30

The Cartographers of WikiProject Maps

WikiProject news
News in brief
Submit your project's news and announcements for next week's WikiProject Report at the Signpost's WikiProject Desk.

This week, we located WikiProject Maps. Launched in February 2004, the project has grown to 4,000 articles and files, including five featured articles and one good article. The project maintains guidelines for creating and editing maps while teaming up with the Graphic Lab to provide a workshop for mapmakers. We interviewed EdwardLane and Yug.

What motivated you to join WikiProject Maps? What is the most interesting map you have uploaded or edited?

EdwardLane: I've always been interested in maps as I like to imagine there are dragons in the unexplored spaces. I joined WikiProject Maps when I realized that I kept coming back for answers to cartography-related questions. I've not (yet) made a map for Wikipedia, but I do aim to.
Yug: "Maps is emotion". I naturally have a visual profile. Images, drawings, attract me a lot. But after years to look at, work with, and design maps, I realized that for me, maps are "emotions". When looking at a map, I can read the core dynamics, the strategic places, the balance of powers, the populations moves leaving the insecure areas then flooding toward more secures cities, or richer lands. It's both intellectually challenging and emotionally touching. It's how I currently explain my odd fascination for maps.
My involvement for the Map project is a by-product of this attraction for maps, knowledge sharing (ie: editing Wikipedia), and my leadership within the Wikipedia:Graphic Lab created in 2005. Following the need for graphics, the Graphic Lab has since spread into a dozen language teams (en, de, fr, es, it, ru, ...) and improved or created from requests about 15,000 images and 5,000 maps so far. Request after request, maps appeared to be a core media for Wikipedia: clean, semantically rich, communicative. But the situation was quite messy, with hundreds of independent map styles, icons sets, color sets, and naming conventions. With the assistance of wiki-friends, I've led a six-year effort to make sense of this, drafting the current Wikipedia map conventions.
This animated map of the Battle of Trebia is used as a tutorial for how to create a map using layers (click image if animation does not play automatically)

While the majority of the project's assessments are for image files, some articles are included under the project's scope. What kinds of articles are these? What difficulties does the project face when improving articles under its scope?

EdwardLane: The scope has recently expanded to include improving all map- and cartography-related articles, WikiProject Maps was originally (and still is) focused on creating maps when people request maps on the talk page for articles using templates like {{reqmapin|somewhere}}.
Yug: The Map project members are massively graphists with visual-oriented profiles. We lack encyclopedic/academic profiles to do scholarly researches to write good and featured articles. The very top priority is the article cartography, which is currently quite messy (the French version provide a good outline for anyone willing to launch a such rewriting).

How often do territorial disputes, civil wars, and disasters result in map changes? How does the project handle territories claimed by more than one government or group? What steps can the project take to prevent editors from altering maps to match their national or political point of view?

EdwardLane: Well, synchronicity strikes; WikiProject Maps has just had some bickering on this subject brought up in a RFC, and I feel a bit like ArbCom, having just worked out what I think would be an appropriate NPOV solution.
South Sudan's recent split from Sudan also triggered a reasonable amount of action from WikiProject Maps (and others) to update the relevant template maps. There are always changes ongoing, but making a map for Wikipedia means you need well-sourced data for the map, and that seems to solve most of those issues. Political issues between the de facto and de jure control of a territory on maps do raise issues, but mostly just portraying both boundaries or labeling the map correctly resolves those. And listing the source of the data in the meta-tags at least lets you know what it is showing.
Which national/political view is portrayed in a map will always be affected by the cartographer, I'll try to quickly explain cartographic generalization.
Imagine you could draw a perfect map of the US: on what scale do you draw it, and is there room for a particular city to be labeled – that's a political choice. For example, on Google maps, Baltimore only gets a label when you zoom in five times, while Philadelphia appears after three zooms, New York and Washington after four. Is there a reason? Well it's mostly to do with space on the map, as Philadelphia is probably not "more important" than Washington and New York, but is probably more important than the other names that could be written in that space and still be in the right spot.
Making those sorts of calls will always have political significance, or at least involve a value judgment, Cartography is in many ways all about deciding what you want the map to show, historically kings and emperors have paid good money to get a map showing their realm to be more powerful/influential/successful/pious than their neighbors.
Yug: More recently, an endless dispute over the People's Republic of China's map and its territorial claims opened again. ArbCom requested that WikiProject Maps suggest a fair/NPOV graphic solution. Edward and I defined the needs and are currently examining maps, collecting the current Wikipedia practices, and will soon suggest a new map convention for disputed areas.

Do you tend to see political or physical maps used most frequently on Wikipedia? Is one preferred over the other? What are some unusual or unique types of maps included in Wikipedia articles?

EdwardLane: Maps are not all about the "perfect" depiction of geography: some show the stars, some show how many people voted in a particular election, some show fictional worlds, some are abstract concept maps, some show the surface of other planets, or like the London Underground Map distort real geography to make a map which is much easier to read.
Yug: Administrative maps are the most common maps displayed across Wikipedia. Its norm is nowadays called "location maps" (guideline here) : a grey based map with administrative limits. They are frequently used as base maps for more complex maps such as animals ranges, election maps, as well as more complex historical maps —the maps within the history—, which are a critical element of an encyclopedia's map landscape. Other kinds of maps such as cartograms are also present in wikipedia, while rare.

How was the standard palette of colors selected for Wikipedia's maps? Has this color scheme caused any difficulties when building complex maps?

EdwardLane: Check out Wikipedia:WikiProject_Maps#Map_colours – and Wikipedia:WikiProject_Maps/Conventions I don't think they have caused any problems.
Yug: In the earliest history of Wikipedia map-making, the CIA orange maps and grey-green png maps were the norms, aside from hundreds of independent styles. Between 2006 and 2007, two palettes of colors emerged: the 'Indian Project' palette was proposed by Planemad alone, and spread for a time. Its colors are quite vivid, and derived from the earlier CIA maps palette. In parallel, the French cartographic workshop team discussed and built a comprehensive palette with an incremental approach. Users STyx, Sting (Brazil), Sémhur, Yug (myself), NorthNorthWest (Germany) each made significant proposals that were enthusiastically commented on, improved, and implemented. This last palette was from the start conceived for the specific use of Wikipedia. The CIA colors were dropped for both moral/political and pratical reasons, the wiki gray was kept, softened, and enriched by web and screen friendly colors to create and strengthen Wikipedia's maps identity, topography —which often explain demographic occupation, history, battles— was pushed forward, while a set of standard icons and labels was provided. The aim was to coordinate map creations among map creators, with an semi-professional, standardized style increasing Wikipedia's maps readability and credibility. Since then, this palette (File:Maps_template-en.svg) is the real cornerstone of our coordinated effort. Within the public domain, it allows any cartographer to use this toolkit of elegant colors, icons, labels within his/her maps. These styles have been explained in our Map conventions pages, with some further improvements and alignments still planned.

Do any of Wikipedia's maps employ fictitious entries similar to the "copyright traps" used by some professional mapmakers? How can the average reader be sure of a map's accuracy without checking another source?

EdwardLane: Not that I'm aware of, though some might be inherited from the original source; but ideally the reliable source of the data should be listed in the map's meta-data. It's a nice question though.

What are the project's most urgent needs? How can new writers and mapmakers help today?

EdwardLane: Writers can no doubt help clean up the language and organize the cartography and map articles – they both need a fair chunk of work. If someone can organize all the various types of map projections and make sure we've not missed any in the Template:Map Projections, that could tidy things up a lot too. If you want to start making maps, say hello on the WikiProject Maps talk page. You could check out these links to tutorials, or we can point you at lists of requested maps.
Yug: We currently seriously need new SVG mapmakers. We recently finished a tutorial with SVG exercises for map-making. If you're interested in learning map-making, that's the place to start. We currently have dozens of requests in the backlog for map creation – which are dozens of learning opportunities!
For the future, I personally think that map-making and image creation in general now need a stronger and ACTIVE support from the Wikimedia foundation. Wikipedia is both text (wiki editor system) and images, with maps having a special place. Some innovative technical solutions and projects are already financed by the Wikimedia Foundation on the editing side. Serious and professional technical innovations projects are needed for images and maps as well. A good direction, for example, would be the development of a free on-the-cloud global map-making system similar to Google-map. Sharemap.org is creating a such online system specifically for encyclopedic maps and Wikipedia, but currently without any official support. But as for other heavy-coding projects, only some financial support can avoid failure and keep them going to improve the Wikipedia map sites. I sincerely wish the foundation can wake up and support this graphic side of its projects.

Next week, we'll learn a new language. Until then, practice your linguistics in the archive.

Gerard van Schagen, a cartographer from Amsterdam known for his maps, completed this map of the world in 1689.


Reader comments

2012-04-30

Featured content spreads its wings

The body of the Atlas moth (Attacus atlas) is hairy and disproportionately small compared to its wings. They are predominantly tawny to maroon in colour with roughly triangular, diaphanous "eyes" on both forewing and hindwing, bordered in black. Patterns and colouration vary among the many described subspecies. From a new featured picture.
Reverse of the 1921 Assay Commission medal by Mint Engraver George T. Morgan. One was struck in gold and presented to President Woodrow Wilson. From the newly featured article.
Canadian Pacific Railway Locomotive No. 2816 display at Steamtown, USA. From the new featured article.
Closeup of the head of a giraffe. From the newly featured article.
1947 award winner Patricia Neal. From the newly featured list Tony Award for Best Featured Actress in a Play.
A newly featured picture is a map of the Battle of Guam, 1944, during the Pacific Campaign.

Six featured articles were promoted this week:

  • United States Assay Commission (nom) by Wehwalt. The United States Assay Commission was an agency of the United States government from 1792 to 1980. Its function was to annually supervise testing of the gold, silver, and (in its final years) base metal coins produced by the United States Mint to ensure that they met specifications. Although some members were designated by statute, most of the commission consisted of prominent Americans, including numismatists. Appointment to the Commission was eagerly sought—for one, commissioners received a commemorative medal, different each year and, with the exception of the 1977 issue which was sold to the general public, rare and collectible.
  • Hedley Verity (nom) by Sarastro1. Hedley Verity (1905–43) was a professional cricketer who played for Yorkshire and England between 1930 and 1939. A slow left-arm orthodox bowler, he took 1,956 wickets in first-class cricket at an average of 14.90 and 144 wickets in 40 Tests at an average of 24.37. Named as one of the Wisden Cricketers of the Year in 1932, he is regarded as one of the most effective slow left-arm bowlers to have played cricket. Never one who spun the ball sharply, he achieved success through the accuracy of his bowling. On difficult pitches, particularly ones affected by rain, he could be almost impossible to bat against.
  • Steamtown, USA (nom) by Ishtar456. Steamtown, USA was a steam locomotive museum that ran steam excursions out of North Walpole, New Hampshire, and Bellows Falls, Vermont, from the 1960s to 1983. The museum, founded by millionaire seafood industrialist F. Nelson Blount, was operated primarily by the non-profit Steamtown Foundation after his death in 1967. Due to Vermont air quality regulations that restricted steam excursions, declining visitor attendance, and disputes over the use of track, some pieces of the collection were relocated to Scranton, Pennsylvania, in the mid 1980s; the rest were auctioned off. The National Park Service conducted historical research on the remaining equipment which was used for a Scope of Collections Statement for Steamtown National Historic Site and published in 1991.
  • American Cream Draft (nom) by Dana boomer. The American Cream Draft is a rare draft horse breed, the only such breed developed in the United States that is still in existence. It is recognized by its cream color, known as "gold champagne", produced by the action of the champagne gene upon a chestnut base color, and by its amber eyes, also characteristic of the gene; the only other color found in the breed is chestnut. Like several other breeds of draft horses, the American Cream is at risk for the autosomal recessive genetic disease junctional epidermolysis bullosa.
  • Giraffe (nom) by LittleJerry. The giraffe (Giraffa camelopardalis) is an African even-toed ungulate mammal, the tallest living terrestrial animal and the largest ruminant. Its specific name refers to its camel-like face and and the patches of color on its fur, which bear a vague resemblance to a leopard's spots. The giraffe is noted for its extremely long neck and legs, as well as its horn-like ossicones. It stands 5–6 m (16–20 ft) tall and has an average weight of 1,600 kg (3,500 lb) for males and 830 kg (1,800 lb) for females. It is classified under the family Giraffidae, along with its closest extant relative, the okapi. There are nine subspecies, distinguished by their coat patterns.
  • Battle of Radzymin (1920) (nom) by Halibutt. The Battle of Radzymin took place during the Polish–Soviet War (1919–21). The battle occurred near the town of Radzymin, some 20 kilometres (12 mi) north-east of Warsaw, between August 13 and 16, 1920. Along with the Battle of Ossów and the Polish counteroffensive from the Wieprz River area, this engagement was a key part of what later became known as the Battle of Warsaw. It also proved to be the bloodiest and the most intense.

One featured list was promoted this week:

  • Tony Award for Best Featured Actress in a Play (nom) by Albacore. The Tony Award for Best Featured Actress in a Play is an honor presented at the Tony Awards, a ceremony established in 1947 as the Antoinette Perry Awards for Excellence in Theatre, to actresses for quality supporting roles in a Broadway play. The awards are named after Antoinette Perry, an American actress who died in 1946. Honors in several categories are presented at the ceremony annually by the Tony Award Productions, a joint venture of The Broadway League and the American Theatre Wing, to "honor the best performances and stage productions of the previous year."

Six featured pictures were promoted this week:

  • Fyodor Dostoyevsky, oil on canvass painting (nom, related article), created by Vasily Perov, a Russian realist painter, and nominated by GreatOrangePumpkin who described it as a "large, informative, impressive, high-quality, great reproduction". In response to questions about the painting's darkness, a reviewer pointed out that darkness is a feature of the light shined on the painting when photographed.
  • Australian White Ibis (nom, related article), created and nominated by JJ Harrison. Although an editor complained that the bird was too "white" and asked if it had been washed, the image passed because, in the words of reviewer Saffron Blaze, "no one wants to see a dirty bird anyway." The Australian White Ibis, a wading bird native to Australia, has been moving to urban areas over the past 40 years.
  • Indian Yellow-nosed Albatross (nom, related article), created and nominated by JJ Harrison. Passed unanimously although there were complaints about the brightness of the white in the photograph. The albatross, the smallest of the mollymawks, is found in the Indian Ocean.
  • Second Battle of Guam (nom; related article), created and nominated by Grandiose, with the rationale: "Using a verifiable map of the US military, [the map] was converted to SVG form, aiding in clarity, using conventional colours and scalable format." The Second Battle of Guam lasted for several weeks, starting in mid-1944.
  • Atlas Moth (Attacus atlas) (nom, related article), created and nominated by Quartl. Editors agreed that the quality was great. A lightened version was proposed, but the original was overwhelmingly preferred. The Atlas moth, native to Southeast Asia and the Malay Archipelago, has the largest wing surface area of any known moth.
  • USS Arizona (BB-39) (nom, related article); created by US Navy (Enrique Muller, Jr.), restored by Centpacrr and Crisco 1492; second version restored by Mmxx; nominated by Crisco 1492. Some editors complained of distortion in the photograph. A second version was proposed, but ultimately the editors preferred the original nomination. The image shows the Arizona passing through the East River in New York shortly after being commissioned in November 1916.
This newly featured picture of Russian writer Fyodor Dostoyevsky, whose works explored human psychology, was painted in 1872 by Vasily Perov.


Reader comments

2012-04-30

R&I Review remains in voting, two open cases

The Arbitration Committee opened no cases this week, keeping the number of open cases at two.

Open cases

A review of the Race and intelligence case was opened as a compromise between starting a new case and proceeding with a ruling by motion. The review is intended to be a simplified form of a full case, and has the stated scope of conduct issues that have purportedly arisen since the closure of the 2010 case.

A complete decision was proposed on 16 April by drafter Roger Davies. The proposed principles include clarifications of harassment policies and sockpuppet investigation procedures. After a long series of findings of fact, the proposed decision seeks to admonish one editor involved in disruptive actions and to ban two others for 12 months. Voting so far has established a tentative consensus on some principles and some findings of fact; agreement on the remedy in the case has not been reached.

The case involves accusations of disruptive editing against Rich Farmbrough. Specifically, concerns have been raised about the editor and his observance of bot policy. Arbitrator Hersfold originally filed the case, which the committee accepted four weeks ago.

Workshop submissions closed several weeks ago, with most parties presenting suggestions on principles to include in a final decision. The draft or "proposed" decision is due to be posted in a few days, by arbitrator Newyorkbrad.

Other requests and committee action

  • The Ban Appeals Subcommittee announced the opening of community input regarding an appeal by Altenmann.
  • Voting on a series of proposals regarding evidence limits in arbitration cases is still in progress.

    Reader comments

2012-04-30

What Git means for end users, design controversies and pertinent poll results

Git: the state of play

Developer and Git switchover manager Chad Horohoe presenting last year in New Orleans

Recently "Technology reports" have abounded with different stories arising from the Git switchover on March 21; it can be easy to miss the wood for the trees when negotiating one of the largest changes to their workflows developers have experienced in years. To assist in establishing the current "state of play" when it comes to the switchover, the Signpost caught up with Chad Horohoe, the WMF developer responsible for managing the switchover.

Chad, are you happy with how things have gone so far? Would you have done anything differently, and if so what?

So far, I think the migration has gone well. There's still a learning curve that people are trying to get past. As far as what I'd do differently if I had to do this whole process again, I would have been much more aggressive in recruiting guinea pigs to help me test our new system. The biggest complaint I have seen from users so far have been related to learning Gerrit and overcoming the Git learning curve I mentioned. Getting people involved in testing the process at an earlier point would've made this easier. Also, given some of the reservations with Gerrit, I think having people involved earlier would've helped us discover these issues sooner.

The move to Git has probably sounded rather abstract to many Wikimedians. What can they expect in the way of tangible differences?

The most important part of this process has been changing our commit workflow to a "pre-commit review" model. The MediaWiki codebase and its extensions have to be runnable at all times—we shouldn't break things when we can avoid it. So by changing our review model, we are trying to accomplish two big things:
  • We're trying to lower the bar to contribution. Since the review process now keeps the codebase clean of things that aren't quite ready for production, we're trying to encourage a lot more casual contributors who maybe didn't have the level of skill that we'd look for when granting commit access (the ability to modify core MediaWiki code). As of this week, everyone's code is reviewed beforehand, so we're trying to level the playing field for everyone who wants to write code (whether it's a one-line fix or a huge new feature).
  • By keeping the code more stable, we're trying to reduce the time it takes to release MediaWiki to our primary users—WMF wikis. Our targeted goal is currently deploying the latest reviewed code every 2 weeks. This encourages contributors who like seeing their work live on the sites, as well as gets fixes and new features in the users' hands much faster.

Technology Reports since "Git day" have included coverage of some of the issues that have arisen since the switchover. How confident are you that once developers get used to the new way of working, those concerns will be resolved?

I think there's two types of issues that have arisen from the changes. The first are "Git issues". These are all problems stemming from the fact that we're trying to teach people how to use a radically different tool from the past. Git has a learning curve, but I think we're starting to get more people over that hump and used to some of the day-to-day work. The second set of issues people are having are "Gerrit issues". Gerrit is not a perfect tool and there are some rough edges to work out. While I will be looking at the work Daniel Friesen and others put into alternative code review tools, I must say that I disagree with the assertion that Gerrit is fundamentally flawed. I've found the Gerrit development community to be active and responsive so I believe some of the more pressing bugs we've uncovered will be fixed for us. Overall, I think that these concerns will resolve over time as people get used to the new system and some of the more glaring issues are fixed.

Is it possible to avoid controversy when changing a design?

Changing the Wikipedia "puzzle globe" logo in May 2010 drew a similar amount of controversy as this month's diff colour update.

In 1957, C. Northcote Parkinson bemoaned the fact that getting agreement on the design for a new bikeshed is uniformly more difficult than getting agreement on the design of a nuclear reactor; though fewer people are affected, the entire community (in Parkinson's case a committee) are willing and able to give their opinion on the matter. MediaWiki tries to avoid this problem by allowing logged-in users to choose how they wish the proverbial bikeshed to appear to them, but it is often not enough: participants still argue over how interface elements should appear to the overwhelming majority of users who are not logged in.

Such was the situation this week as the English Wikipedia's Technical Village Pump became a forum for discussing the changes to MediaWiki's default diff colouration and formatting schema, brought in last week with the local deployment of 1.20wmf1. Predictably (see previous Signpost coverage), the result was much consternation and fierce debate (as of time of writing, it seems as though the new global default will remain the default on the English Wikipedia, albeit with possible tweaks).

Design controversy is nothing new to Wikimedia wikis, however. In May 2010, for example, an update to the famous Wikipedia "puzzle globe" logo caused pages of on- and off-wiki debate. Indeed, it was an episode that bore all the hallmarks of the present diff colour discussion: the change was primarily aimed at fixing an objective problem (incorrect characters) but also incorporated purely aesthetic changes, and hence sparked disagreement. In the end, the logo was adjusted slightly to respond to the criticism of it by Wikipedians, but the update was not reverted. It was around the same time that the Vector skin was rolled out – first optionally and then as the default for all users – prompting a similar number of complaints. These complaints included those of one user, still an active Wikimedia Commons editor, who wrote that "the kind of morons with no place whatsoever in Wikipedia ... I expect donations to plummet in reply to this change".

Not all central changes have stuck, either: the furore over a change to the colouring using in the new messages bar prompted it to be widely reverted. Of course, the correct analysis of this historical record is itself a controversial issue; commentators seem split between those who feel that controversy is a part of the design process that can't be eliminated and those who feel that it can be, but that developers and designers have never tried hard enough to eliminate it. One thing is certain, though: with design changes of some sort or another occurring on an increasingly rapid basis, it's rarely been a more topical issue.

In brief

Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for many weeks.

  • Loss of session data still an issue: The tentative close of bug #35900 ("Odd session bugs") reported in last week's "Technology report" unfortunately had to be reversed this week after editors on the English Wikipedia continued to have problems remaining logged in. Although a recurring issue, the causes of this bout of session data loss have baffled developers, causing the bug to be escalated to WMF Lead Platform Architect Tim Starling in the hope of resolution. Pertinently, this week's poll results (shown right) suggest that approximately one-third of users would favour significantly greater WMF emphasis on performance versus feature development.
  • Three MediaWiki releases: The first release candidate for MediaWiki 1.19 was announced on April 26, two months after the MediaWiki version was deployed to Wikimedia wikis (the intervening months being taken up with the Git switchover and moving to a new release cycle). It was accompanied at the same time by so-called "point releases" for both MediaWiki 1.17 (1.17.4) and MediaWiki 1.18 (1.18.3); these were targeted at fixing a small number of significant bugs in their applicable version. The releases prompted bugmeister Mark Hershberger (about to start his final month at the WMF) to investigate the upgrade state of external wikis. He found that only 15% of non-WMF wikis were updating regularly, with 4% not having updated since MediaWiki 1.10 (for a similar study conducted in August 2010 with not entirely dissimilar results, see previous Signpost coverage).
  • Watchlist email notifications enabled on all wikis: With the resolution of bug #28026 (performance impact notwithstanding), users on all wikis are now able to receive email updates when an item on their watchlist is changed. Discussion on the wikitech-l mailing list focussed on what form default notifications should take, if the feature is to be enabled by default at all. Elsewhere, there was extended discussion about Wikimedia's readiness for the introduction of widespread IPv6 use among internet surfers (a subject which also gets its own page on meta); an RFC has also been opened on the subject.
  • Wikipedia Zero: There was a significant uptick in attention this week for Wikipedia Zero, a WMF-led initiative aimed at negotiating free 2G Wikipedia access in regions where other forms of internet access are severely limited. The scheme, which is achieved through a combination of negotiation with network providers and WMF technical support in order to ensure it is not abused, will (for example) be launching with mobile provider Digi Malaysia shortly. Blogger Gerard Meijssen pointed out that the same technology could be used to provide free access to specialised wikis, including those used to share free agricultural knowledge.
  • New Engineering Community Group established: The creation of a new Engineering Community Group has been announced on the wikitech-l mailing list. The group, which will be led by former Volunteer Development Coordinator Sumana Harihareswara, will take on the responsibilities of the "Technical Liaison; Developer Relations" group, which is being disbanded. Its responsibilities will include "facilitating collaboration and communication between the Wikimedia Foundation, its employees and the larger Wikimedia developer community, and facilitating collaboration and communication between the Wikimedia developer community and other Wikimedia communities". The news was met positively by the Wikimedia community. Harihareswara's specific remit will continue to include many of her previous responsibilities, including overseeing this year's Google Summer of Code projects (details of which, contrary to last week's story, will in fact be covered in detail in next week's issue).
    Highly preliminary sketch for the feedback page
  • NewPageTriage to go live: The development of Special:PageTriage, a dashboard-style special page aimed at providing a more useful alternative to Special:NewPages, will take a step forward on Wednesday when an early prototype – little more than a redesign of the old page in many respects – is deployed by private URL this week to test its compatibility with the production environment. However New Page Triage (WP:NPT) missed its April date for the first level demonstration of its new interface. Okeyes (WMF), community liaison, said there were very minor delays due to last minute attempts to accommodate community requests and do further testing to identify "any and all rare bugs". Okeyes (WMF) has scheduled and booked May 2 for the deployment date.
  • Article Feedback Tool/Version 5. Wikipedia:Article Feedback Tool/Version 5 has scheduled May 2 to deploy the test alternative versions of Option 1 feedback form. Feedback continues at Article Feedback Tool/Version 5. Interested users can also test a version of the tool hosted on Wikimedia Labs. It should be noted that the tool is eventually intended to have a variety of important features not yet present on the prototype. Elsewhere, there will be an Office Hours session at 18:00 UTC on May 4 in #wikimedia-office connect to discuss progress on the development of version 5 of the Article Feedback tool. WMF community liaison Oliver Keyes suggested that the office hours would be used as an opportunity to "show off the almost-finished feedback page and prep it for a more public release".
  • One bot approved: 1 BRfA was recently approved for use on the English Wikipedia:
    1. MadmanBot's 13th BRfA, generating Wikipedia:Inactive administrators reports; delivering messages and e-mails to inactive administrators as appropriate.
At the time of this writing, 11 BRfAs are active. As always, community input is encouraged.

Reader comments
If articles have been updated, you may need to refresh the single-page edition.