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.
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. | ” |
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. | ” |
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.
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.
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. | ||||||||||||||||||||||||
IntroductionTell 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.
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 StrategiesWhen 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.
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.
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 practicesWhat 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.
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 pictureWhat 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? 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!" |
“ | I am available as a paid editor. I charge $1000 to take an article to featured status. If you don't require your article to be featured, just improved, we can work out a reasonable compensation schedule. Please contact me via my email from this account, or at Wikipediocracy where I am a moderator. I believe my qualifications, as detailed below, speak for themselves. | ” |
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."
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.
"Looks like a pretty effective troll to me. Par for the course for this particular editor."
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."
"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."
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."
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 |
|
---|
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."
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.
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.
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.
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.
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.
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%).
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)
Several of the accepted papers of this month's Asia-Pacific Web Conference APWeb2012 concerned Wikipedia:
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.
At the moment, to enable ReferenceTooltips, any logged-in editor can go to My preferences → Gadgets → 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.
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.
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
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?
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?
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?
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?
How was the standard palette of colors selected for Wikipedia's maps? Has this color scheme caused any difficulties when building complex maps?
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?
What are the project's most urgent needs? How can new writers and mapmakers help today?
Next week, we'll learn a new language. Until then, practice your linguistics in the archive.
Six featured articles were promoted this week:
One featured list was promoted this week:
Six featured pictures were promoted this week:
The Arbitration Committee opened no cases this week, keeping the number of open cases at two.
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.
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?
The move to Git has probably sounded rather abstract to many Wikimedians. What can they expect in the way of tangible differences?
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?
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.
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.