The lateness of The Signpost has long been a running gag. An all-volunteer publication will probably never be on time, but in recent weeks our lateness has become chronic to the point of ridiculousness. We have recently had some additions to The Signpost editorial board which have made things much easier for everyone, but one key position remains vacant: publication manager. This key vacancy is the cause of most of our lateness issues. The duties of this position are:
This position doesn't get a lot of attention, but it is vital. Publishing is not hard! It just takes 30–60 minutes each week. What the Signpost needs is not so much special technical skills as skills at coordination and a preparedness to liaise with the editorial board and writers in the weekly run-up to publication. The editorial board is a nest of libelous gossip aims for professional standards and is a social process of trust and give and take that most people find rewarding.
If you are interested in helping Wikipedia's community newspaper continue to appear every week, please contact our personnel editor Rosiestep.
On Friday 29 January, more than five weeks after dismissing community-selected trustee James Heilman (Doc James), the Wikimedia Foundation Board of Trustees announced that María Sefidari (Raystorm) would fill the vacancy. This comes after a period of indecision by the Board as to how to deal with the aftermath of its dramatic move last December; shortly after the fatal meeting, chair Patricio Lorente announced that the Board would be referring the matter to the volunteer committee that had run the election, rather than making an immediate decision on the vacant seat.
In the June election, Sefidari gained the fourth-highest ranking under the support/(support+oppose) formula that was introduced in 2012. Appointing her to the vacant seat was one of the options canvassed by the committee, along with the holding of a fresh election, leaving the position vacant until the end of the two-year term in mid-2017, and asking the community what to do. She has already served one term as community-selected trustee, from 2013 to 2015.
How do Sefidari's priorities compare with those of the trustee she is replacing? The Signpost's pre-election survey of candidates' priorities revealed that she gave significantly higher priority than Heilman to reducing the gender gap in editing communities, increasing global-south reader and editor participation, and implementing VisualEditor; and significantly lower priority to increasing editor retention, investing more in collecting data, and providing more engineering resources to improve readers' and editors' experience.
We asked Lorente and Sefidari a number of questions about the events of the past seven weeks. Lorente's responses tended to be non-specific and were occasionally evasive. We asked whether the political damage to the Board in the aftermath of Heilman’s removal could have been minimised by appointing Sefidari straight away rather than after a considerable interval; and similarly, whether he regrets not acting earlier on the community’s objection to the Arnnon Geshuri appointment:
“ | There are certain things the Board could have done better in these past weeks. This includes how we communicate with the community about our intentions, how we respond to community concerns in a timely way, and communicating with more plain language and direct words. We are taking steps to improve our efforts here. That said, the Board is not likely to make decisions in a rush. We have a very diverse Board, with strong voices, and we take our responsibilities very seriously. We need to listen carefully to each other, work across very different time zones, and other considerations an international governing group has to consider. | ” |
Lorente did not respond to our question, "As a trustee, are you uncomfortable that the executive director has the support of only 7% of the WMF’s staff, and of only one of the C-level managers?" Sefidari felt freer to comment, perhaps because as a new arrival she does not have to carry the Board's more recent baggage: "It is the Board’s role and responsibility to oversee the Wikimedia Foundation, and to make sure the organization succeeds. We have a legal obligation to oversee the management of the organization and ensure that it fulfills this role. This situation is concerning and is on the radar, as it needs to be."
We asked Sefidari whether she would have preferred an open vote to her appointment without re-election.
“ | I would have been fine with new elections. I believe elections are important. I have run in two community elections, and believe in the importance of community scrutiny ever since I ran for and became an admin on Spanish Wikipedia nine years ago. That said, I am fully aware this is uncharted territory. ... I think it would have been very easy for the Board to leave the seat vacant, as opposed to running elections which do require resources and time. Even members of the Elections Committee seemed highly reluctant to recommend new elections for that reason and others. And I personally would not have liked a precedent in which after a community-selected member is removed or resigns, the seat remains vacant until the next round. It may be legally valid, but I don’t think it morally is. | ” |
Some readers may be surprised that she then raised a scenario that would cast her appointment as nothing more than a band-aid solution: "To expand on this, I think it is perfectly possible to have elections this year, and I am completely open to this option. I think the new Elections Committee can discuss and come up with a new elections system in time for that to happen, even if it is in the second half of the year, without the pressure of knowing they have to get something out fast because otherwise the seat will be vacant at a time when it is important it is not. I would particularly love it if they could figure out a system that promotes diversity."
Sefidari avoided the question of whether Heilman should have been removed, reporting that she was not "up to speed". She wrote: "I was just as surprised as the rest of the community to learn that James had been removed. ... I don’t know yet what happened with James."
Would she have handled the Heilman and Geshuri issues differently to the way the Board did?
“ | I don’t know what happened with James. But if a meeting was called specifically to discuss his continuity in the Board, there should have been contingency planning, including taking into account how to communicate the decision to the community. The mere fact of the removal was going to be shocking to everyone. The way it was communicated all over the place in bits and pieces was disturbing for everyone. For all I know this was prepared, but James posting on Wikimedia-l upended those plans. ...
As for Arnnon, straight communication would have been desirable. The full Board was not aware of his past circumstances. ... A clear communication along the lines of “we acknowledge the concerns, we are discussing this right now internally and with Arnnon and we intend to reach a resolution at our meeting at the end of January” might have helped set community expectations. Everyone knows Board members are volunteers with regular lives and jobs and who are in different time zones. Internal communications are not immediate. Most people are reasonable with what can be demanded of Board members. This doesn’t mean there cannot be at least an acknowledgement of the situation. The perception that the Board was paralyzed was very bad. |
” |
Does she have any sympathy for Heilman’s view that the Board and the Foundation’s management are too secretive? "I think there is a communications issue, which results in the Board looking secretive, and that needs to be addressed." Was she sympathetic towards the community’s vote of no confidence in Arnnon Geshuri? "I understand why that happened. I think a lot of people identified with the positions of Kat Walsh and Florence Devouard, but were willing to wait for what Arnnon or the Board would say. Once Arnnon’s message came out, the matter was sealed."
Sefidari thinks that community perceptions that the Board and the WMF are adopting corporate language and strategies are "a valid concern. ... There’s a difference between sending corporate messaging devoid of content, and professional messaging that balances the different considerations (legal, transparency) and is informative and useful."
As the community's new representative on the Board, María Sefidari summed up the big picture: "We have reached a stage in the organization’s development where we are expected to be behave professionally, to behave like an organization with a clearly defined mission and 200 employees impacting things around the globe. We need to remember though that we’re an organization built on a community."
Editor's note: In December, the Wikimedia Foundation Board of Trustees voted to remove one of their own, community-elected trustee James Heilman (Doc James). Since that time, the exact reasons for the dismissal have been a matter of community debate and even public debate amongst members of the Board themselves about the few details that have been revealed. Heilman has previously spoken out on the matter of transparency and his dismissal in a previous Signpost op-ed.
This timeline is being published in response to the following statement made by the Board in early Jan 2016 at Jimmy Wales' request:
“ | The removal of James as a board member was not due to any disagreement about public discussion of our long term strategy. The board unanimously supports public discussion of our long term strategy, has offered no objections to any board member discussing long term strategy with the community at any time, and strongly supports that the Wikimedia Foundation should develop long term strategy in consultation with the community. | ” |
Jimmy Wales tried to build a search engine, Wikia Search, without success.
The Search and Discovery team came into existence with eleven members.
Risker commented on this very well supported team.
I was selected by the community for a position on the board.
The Knight Foundation grant was awarded for “stage one development of the Knowledge Engine by Wikipedia, a system for discovering reliable and trustworthy public information on the Internet."
The Knight Foundation grant was presented to the board, after which I requested further documents surrounding the grant. They were eventually provided after some resistance from other board members and the executive director, Lila Tretikov.
My email to the board about my concerns regarding this grant:
“ | Hey All
We are at 6 days since being notified of the Knight Foundation grant. I at this point strongly oppose its acceptance. There are too many issues: 1) We are "selling" the Knight Foundation a search engine with passages like "the foundation and its staff have a track record of success and a strong vision of what a search engine can do when it has the right principles, and the right people, firmly behind it." (Aug 2015) Plus we do not have success at building a "search engine". 2) What the WMF board was sold in Mexico was "the largest free open knowledge source". (June 2015 doc) A knowledge source is not a search engine. "Source" means creating / curating content. 3) Lila states we are not building a search engine as of two days ago per chat. A few board members understood we were maybe doing this after Mexico. Others did not. I do not think we as the board have a clear idea of what 10% of our engineering resources are being spent on (ie what exact the discovery team led by Wes Moran is doing). 4) There is a serious lack of transparency around this new "sister project". This has not been discussed with our communities as far as I am aware. Please correct me if I am wrong. As such it has the potential to worsen WMF / community relations. Starting a new sister site without community discussion is not the wiki way. There are more issues but this is the start. We need to request more documents surrounding this topic as it maybe a bigger issue than simply refusing a grant. |
” |
I emailed the board list offering to write up an overview of these ideas for the Signpost, which was met with negative comments by some board members.
The board approved the Knight Foundation grant. I supported its approval following pressure which included comments about potentially removing members of the Board. Assurances were provided that the Knight Foundation and Wikimedia Foundation were on the same page regarding the grant.
My removal from the board.
Publication of the press release about the grant.
Request for release of the grant application and statement by Wales that he will look into it.
As the request for release of the grant application was not replied to, the request was repeated.
Archiving of the page per Wales' request without the question being answered.
Release of further details by Tretikov with the statement that the grant paperwork could not be released due to “donor privacy”
So yes, the majority of the board and I clashed, and yes it was partly about our strategy and whether or not the community should be made aware and involved in these discussions. While the board prefers I not release this information, in the face of contradictory statements, I intend to let the facts speak for themselves.
James Heilman is a Canadian emergency room physician, a founder of Wikimedia Canada and the Wiki Project Med Foundation, and a former member of the Wikimedia Foundation Board of Trustees.
The removal of James Heilman (Doc James) from the Wikimedia Foundation Board of Trustees has brought the issue of the “knowledge engine”, i.e. the work of the WMF’s "Discovery" department, into focus for the volunteer community.
Ever since his dismissal, Heilman has maintained that disagreements about appropriate transparency related to the Discovery, or "Knowledge Engine", project, funded by a restricted grant from the Knight Foundation, were a key factor in the events that led to his removal. Jimmy Wales has referred to these claims as "utter fucking bullshit".
But what is "discovery" and the knowledge engine all about? This is an attempt to make sense of the patchy information that the Wikimedia Foundation has provided to the volunteer community and the public to date, and to extract some of the underlying ideas related to the project.
A few days ago, Lila Tretikov posted a statement titled "Some background on the Knowledge Engine grant" on her talk page on Meta-Wiki. This is worth reading in full; parts of it are excerpted in what follows below. She begins by acknowledging that she should have communicated with the volunteer community sooner.
“ | Why didn't you discuss these ideas with the community sooner?
It was my mistake to not initiate this ideation on-wiki. Quite honestly, I really wish I could start this discussion over in a more collaborative way, knowing what I know today. Of course, that's retrospecting with a firmer understanding of what the ideas are, and what is worthy of actually discussing. In the staff June metrics meeting in 2015, the ideation was beginning to form in my mind from what I was learning through various conversations with staff. I had begun visualizing open knowledge existing in the shape of a universe. I saw the Wikimedia movement as the most motivated and sincere group of beings, united in their mission to build a rocket to explore Universal Free Knowledge. The words "search" and "discovery" and "knowledge" swam around in my mind with some rocket to navigate it. However, "rocket" didn't seem to work, but in my mind, the rocket was really just an engine, or a portal, a TARDIS, that transports people on their journey through Universal Free Knowledge. From the perspective I had in June, however, I was unprepared for the impact uttering the words "Knowledge Engine" would have. Can we all just take a moment and mercifully admit: it's a catchy name. Perhaps not a great one or entirely appropriate in our context (hence we don't use it any more). I was motivated. I didn't yet know exactly what we needed to build, or how we would end up building it. I could've really used your insight and guidance to help shape the ideas, and model the improvements, and test and verify the impacts. However, I was too afraid of engaging the community early on. Why do you think that was? I have a few thoughts, and would like to share them with you separately, as a wider topic. Either way, this was a mistake I have learned enormously from. |
” |
This kind of communication is potentially a good start to mend fences with the community, and redress some of the things that went wrong with how and when this project was started and communicated.
In her statement, Lila Tretikov recalls her thoughts around the knowledge engine in June 2015. But to locate the actual beginning of this project, we have to look back a little further than that.
"Search & Discovery" first appeared as a department on the Wikimedia Foundation Staff & Contractors template on 30 April 2015. There would have been no point in creating a well-staffed, well-funded Search & Discovery department in April 2015 if the WMF leadership had had no practical idea of what this team was going to be working on.
Risker was perhaps the first to raise public questions about the project, which remained unanswered. Reviewing the WMF's draft 2015–2016 Annual Plan in her capacity as a member of the volunteer-staffed Funds Dissemination Committee in May 2015, she said on Meta:
“ | Search and Discovery, a new team, seems to be extraordinarily well-staffed with a disproportionate number of engineers at the same time as other areas seem to be wanting for them. I don't see "fix search" in the Call to Action document; even if it fell into the heading "Improve technology and execution", this seems like an abnormally large concentration of the top WMF Engineering minds to be focusing on a topic that didn't even rate its own mention in the CtA. More explanation of why Search and Discovery has suddenly become such a major focus is required to assess whether this is appropriate resourcing. | ” |
This is in line with what James Heilman said in his Signpost op-ed dated January 13, 2016, describing the ideas around Search & Discovery as having been developed before the April to June 2015 quarter:
“ | Our long-term strategy must be developed in genuine collaboration with our movement. This means that strategy discussions are started early, that ideas are proposed, and that this is done before a year into a project or millions of dollars are spent. Our ideas around "search and discovery" were developed before April to June of 2015 and we presented them first to potential funders rather than our own communities. | ” |
By September 2015 – more than four months before the WMF publicly announced the grant to the community and the world at large on January 6, 2016 – the Knight Foundation had clearly made a decision to support a WMF knowledge engine project. A still extant page on the Knight Foundation website mentions a grant for $250,000, with a grant period running from 1 September 2015 to 31 August 2016, funding work –
“ | To advance new models for finding information by supporting stage one development of the Knowledge Engine by Wikipedia, a system for discovering reliable and trustworthy public information on the Internet. | ” |
James Heilman's dating of the project matches the facts. And Risker's questions, posed in May 2015, indicate that the volunteer community – including the FDC – had been out of the loop well before June 2015.
Lila Tretikov addresses another question in her statement:
“ | Why did the board not publish this grant paperwork?
Generally we do not post donor documents without advance agreement, because doing so breaks donor privacy required in maintaining sustainable donor relations. In practice, I am told we have not actually published grant paperwork since 2010, but we do publicize grants in blogs when requested and agreed to by donors. A portion of the KF knowledge engine grant document that outlines the actual commitments we've made I quoted below. |
” |
This seems to differ from her predecessor Sue Gardner's statement of WMF policy in October 2011. In this statement, Gardner said,
“ | The Wikimedia Foundation has a policy of publishing our grant applications when the grantmaking institution is okay with it. We don't do a lot of grant applications, and of the ones we do, I am guesstimating that two-thirds of the grantmakers have said it's fine with them for us to publish, and about a third have asked us not to. Some grantmaking institutions are very happy to publish, because they believe the sector as a whole benefits from transparency about how things work. | ” |
Sue Gardner said publishing grant applications is standard policy unless the donor objects. Lila Tretikov says it is standard policy not to publish grant applications, unless "requested and agreed to by donors."
This seems like a subtle move away from the transparency which the WMF has traditionally emphasised as one of its core values.
Volunteers have called for weeks for the Knight Foundation grant application and grant letter to be published. A month ago, for example, MLauba addressed Jimmy Wales on his talk page, responding to statements by Wales that James Heilman's narrative was "misdirection", a "trap", "not true" and that he – Wales – was "a much stronger advocate of transparency than James":
“ | As for your claim to be a bigger champion for transparency, please back it up with the details on the restricted grant from the Knight foundation immediately. Talk is cheap, actions speak volumes. MLauba (Talk) 18:02, 8 January 2016 (UTC) | ” |
Wales replied,
“ | What sort of details do you want? I'll have to talk to others to make sure there are no contractual reasons not to do so, but in my opinion the grant letter should be published on meta. The Knight Grant is a red herring here, so it would be best to clear the air around that completely as soon as possible.--Jimbo Wales (talk) 18:19, 8 January 2016 (UTC) | ” |
This sounded promising. Yet nothing happened on that front for the best part of a month, until Lila Tretikov's recent statement on her Meta talk page. In the relatively brief discussion that has ensued there to date, James Heilman has reiterated his call for the grant application to be published:
“ | What has been requested is the "grant application". This is a document prepared by the WMF and submitted to the Knight Foundation rather than a document from the donor. All other mo[ve]ment entities, including chapters and those applying for individual engagement grants publicly post proposals for funding. I do not understan[d] the reasons the WMF cannot also? Doc James (talk •contribs • email) 16:56, 30 January 2016 (UTC) |
” |
Yet the responses posted by Jimmy Wales and fellow Board member Denny Vrandečić (Denny) on that page are anything but encouraging. The WMF board seems remarkably reluctant to publish both the grant application and the grant letter for community review.
What Lila Tretikov has now provided on her Meta talk page is a list of expected outcomes of the Knight Foundation grant, deliverable at the conclusion of the first stage. The mention of a first stage raises the obvious question of how many stages are envisaged, and what the expected deliverables for the other stages are.
Liam Wyatt (Wittylama) mentions in his most recent blog post that the WMF's original grant application seems to have been for a much larger amount than the relatively modest $250,000 the Knight Foundation has actually committed to. As others have pointed out, $250,000 is an amount the Wikimedia Foundation can raise and has raised in a few hours on a December afternoon. Liam Wyatt's assertion that the original application was for a much larger amount seems at least plausible.
Details of the grand vision for this multi-stage project, couched in approachable language understandable by anyone, is still lacking. Publication of the grant application would help volunteers and the public understand the WMF leadership's thinking, and the long-term goals of the Discovery project.
Some related information is available in a Discovery Year 0–1–2 presentation on MediaWiki – but when originally delivered, its slides would have been accompanied by spoken commentary. As it is, the slides are written in such a shorthand and jargon-laden style that it seems likely few general readers will be able to follow the content, and fill in the gaps.
What's described on page 9 of that document however is clearly some form of search engine for open content on the Internet.
This is also reflected in the original Knight Foundation announcement from September 2015:
“ | To advance new models for finding information by supporting stage one development of the Knowledge Engine by Wikipedia, a system for discovering reliable and trustworthy public information on the Internet. | ” |
Of course, this is not the first time the idea of a search engine has been raised in the Wikimedia universe. Those with long memories will recall Wikia Search, a short-lived free and open-source Web search engine launched by Jimmy Wales' for-profit wiki-hosting company Wikia in 2008.
Wikia Search was conceived as a competitor to the established search engines. It was not a success, closing down in 2009 after failing to attract an audience.
That there have been questions among WMF staff and volunteers whether the WMF is engaged in building a search engine is borne out by a corresponding section in the Discovery FAQ on MediaWiki:
“ | Are you building a new search engine?
We are not building Google. We are improving the existing CirrusSearch infrastructure with better relevance, multi language, multi projects search and incorporating new data sources for our projects. We want a relevant and consistent experience for users across searches for both wikipedia.org and our project sites. |
” |
At the same time, the Discovery FAQ on MediaWiki asks,
“ | Would users go to Wikipedia if it were an open channel beyond an encyclopedia? The Wikimedia movement's vision is to make the sum of all human knowledge freely available to everyone. Wikipedia is our largest and most well-known project, but there are many other projects like Wikimedia Commons and Wikidata that move us towards realising our vision. These projects have millions of users every month! So, yes, if we can make a search system that's good enough and meets the needs of our users, people absolutely would use it. |
” |
It is perhaps significant that Wikipedia is now one of the search engine options for the search box in Firefox, alongside Google, Yahoo!, Bing and others.
Assessing whether users would "go to Wikipedia if it were an open channel beyond an encyclopedia" is also one of the key questions the work funded by the Knight Foundation is expected to answer.
The sections of the Knight Foundation grant documentation that Lila Tretikov has quoted on her Meta talk page read as follows:
“ | What are the expected outcomes of this grant? (quoted text from the grant) At the conclusion of the first stage, the results will include:
What are the activities this grant supports? (quoted text from the grant)
|
” |
Responding to a question about the mention of Original Equipment Manufacturers in the above grant excerpt, Lila Tretikov has indicated on her talk page in Meta that the WMF is
“ | working with manufacturers that produce mobile phones to put Wikipedia on them at manufacturing time, before those devices are sold. This is especially helpful to raise awareness in emerging markets where Wikipedia is not well known. | ” |
There is no reason to assume that this type of arrangement will be restricted to mobile phones. Even today, the Amazon Kindle e-book reader for example has a Wikipedia look-up function pre-installed, as does the Amazon Echo, a household infotainment assistant that like Apple's Siri responds to voice commands.
One problem the Foundation appears to want to address is that Search often returns "zero results" – i.e. cases where a user query is not mapped to a Wikipedia article.
Kindle users trying to look up a word in a book they're reading will be familiar with this problem. To give an example, the other day I was faced with the term "unentailed" in a Victorian short story. Neither of the Kindle's built-in dictionaries knew the term. Querying Wikipedia on the Kindle yielded the disappointing message: "No Wikipedia results were found for your selection", along with an option to "open Wikipedia". When I did so, I found many Wikipedia articles containing the term, but only one was useful in helping me understand the word: Fee tail.
A better search function might have presented me with that article to begin with. Similarly, I might not have had a zero results message if the Wikipedia search function extended to other Wikimedia projects. Instead, my Kindle might have pointed me to the Wiktionary entry for the word unentailed.
Search improvements like this would make locating information more convenient for Kindle users. Amazon would arguably profit from having a more desirable product.
The ongoing community consultation on Meta suggests that one possible approach the Wikimedia Foundation might take would be to
“ | Explore ways to scale machine-generated, machine-verified and machine-assisted content | ” |
More than half of all language versions of Wikipedia suffer from a long-term dearth or indeed complete lack of human volunteer editors. Wikidata content could be used to have machines generate simple articles "on the fly", using a store of simple sentence templates that Wikidata values are then plugged into. This, too, would reduce the number of times users' searches come up empty.
A key concern for search engines is which information to "surface" in response to a query, i.e. identifying which information is most "relevant" to a user query. (In the above example, for instance, this might have been the Wiktionary entry for the word "unentailed", or the Wikipedia article for "fee tail".)
Here, too, Wikidata and Discovery are apparently envisaged to play a key role in future. A little-visited Discovery RfC draft subpage on MediaWiki speaks of "public curation of relevance":
“ | We'd like to explore a relevance model where Wikidata could be used as a component of our relevance calculations. This would not only leverage the high quality data in Wikidata but could empower our communities to affect relevance calculations rather than letting algorithms do all the work. As with any system that allows user contributions we would have to be very sensitive and cognizant of anyone gaming the system. | ” |
There are obvious alarm bells attached to that last caveat. Increasing or diminishing the visibility of information to search engine users is what search engine optimisation is all about. Public curation of relevance provides a mechanism that seems tailor-made for that purpose – hence the caveat.
As discussed in a previous Signpost op-ed, search engines are increasingly re-publishing open content deemed relevant to users' queries on their own sites.
The purpose of a search engine used to be to provide the user with a directory of relevant links. This purpose has shifted: search engines are morphing into answer engines that aim to provide the answers to users' questions directly, obviating users' need to click through to any other site. This supports the search engines' business model: search engines derive a significant part of their income from the ads displayed on search engine results pages. Making sure that users stay on these pages and do not click through to other sites (including Wikipedia) improves the search engines' bottom line.
The Knight FAQ on MediaWiki emphasises the importance of APIs (application programming interfaces):
“ | It's important that apps and third parties can search our site too. | ” |
The availability of a Wikipedia knowledge engine would not just benefit users of Wikimedia sites. There are clear overlaps with commercial search engines. Google itself for example, when introducing the Knowledge Graph to the public, referred to it as a "knowledge engine". As mentioned in that publicity video, a key concern when deciding what content to show in response to a query is what other users have judged relevant to their query.
Seen from the viewpoint of potential re-users like Google, Bing, Yandex and other search engines, public curation of relevance, as mentioned above, could help them identify free information sources that human users are likely to find useful.
Thus the API might deliver volunteer-derived data that those answer engines can use to optimise their product – for example through optimised page ranking for open content pages, or direct inclusion of user-preferred free content in answer boxes, knowledge panels and the like.
Given the information presently available, it seems reasonable to assume that the long-term goal of the Discovery project, including public curation of relevance, is to build a search engine for free information sources on the Internet, and for capturing and defining patterns of human user interaction with such content.
The failed Wikia Search project was designed to compete against Google. Not least because of this failure, it seems unlikely to me that the present Discovery project pursues similar long-term ambitions.
It simply doesn't seem very plausible that the Discovery project could or could even be intended to compete against the likes of Google, Bing and Yandex, given that –
At most, the Wikimedia Foundation board appears to entertain the idea of charging re-users for API use. In other words, the work done by volunteers might be of sufficient economic value to re-users to open up another source of income for the Foundation.
I recall listening to Lila Tretikov's "Facing the Now" speech at Wikimania 2014, in which she stressed that Wikipedia, while apparently at the peak of its success at the time, was in danger of being left behind by technology developments, and would need to adapt to remain relevant. I wondered at the time what she was driving at, but it seems to become clearer now.
As people's infotainment needs and usage patterns move away from desktop computers to mobile phones, voice-controlled electronic assistants and other products that will be as commonplace in ten or twenty years' time as they are unimagined by most of us today, many of the people who used to visit Wikipedia pages may find their information needs more conveniently satisfied elsewhere than on the pages of an encyclopedia.
The march of technological progress can't be halted. And indeed, many of us find that progress inherently exciting. The idea of positioning the Wikimedia community as the central engine driving many different types of information products and services – or at least a major component of such an engine – is likely to appeal to many Wikimedians. It would certainly keep Wikimedia relevant.
And one might ask, in the absence of scalable alternatives, is there really a better process for generating and curating such content today? Google has long argued that volunteers outperform paid contributors when it comes to such work.
Yet there is also much to be disturbed about. Omnipresent snippets, delivered to a potential audience of billions, amplify the risk of manipulation, creating an information infrastructure that seems more vulnerable to activist influence, or indeed Gleichschaltung, than conventional media. It has been established that even today, search engines would have the power to sway elections if they put their mind to it.
To the extent that volunteer labour helps corporations like Apple, Google, Amazon, and Microsoft make billion-dollar profits, the potential labour patterns described here involve obvious and profound social and economic injustices. On Jimmy Wales' talk page, volunteers have begun to wonder whether they need to unionise to have any influence on the future of their movement.
The increasing importance of machine-generated and machine-read content in efforts to serve global information demand may be anathema to many Wikimedians committed to the idea of an encyclopedia written by people, for people.
And there are other concerns: to what extent do Silicon Valley-facing developments like those described here, efforts to build a technologically slicker product and achieve greater market penetration, detract from other efforts that volunteers might consider more relevant to the core goal of writing an encyclopedia? Making Kindle search functions more easy and satisfying to use is all well and good, but what should the relative priority of such efforts be?
James Heilman is a Wikipedian who has gained much acclaim for his efforts to make Wikipedia's medical content truly reliable. Bringing a Wikipedia article to a quality level that was good enough to make it eligible for inclusion in a peer-reviewed journal (see previous Signpost coverage) – the first Wikipedia article to qualify as a reliable source under Wikipedia's own rules – was a milestone in Wikipedia history, though one the Foundation made no great effort to publicise at the time.
In an alternative universe, the Wikimedia Foundation might put equal focus on supporting and expanding such efforts, believing that a quality product will always have a readership. Ubiquity is not the same as quality; Gresham's law could easily be applied to the world of information as well.
As stated above, this op-ed is my attempt to make sense of the patchy information that has been made public about Discovery, or the Knowledge Engine. I will be grateful to have my interpretations and conclusions confirmed or corrected as appropriate by WMF personnel – and, I am sure, so will the volunteer community.
But most importantly, there are matters here that the community should make an input to. The ongoing community consultation on strategy touches on many of the issues discussed here. It will close on February 15, 2016.
There is also an ongoing issue of transparency. The WMF board should make the Knight Foundation grant application and grant letter public, in line with WMF policy as stated by Sue Gardner in the past. If for some reason the Knight Foundation objects, that should be openly stated and an explanation provided.
For another perspective on these developments, see Liam Wyatt's blog post Strategy and controversy, part 2.
Update: The grant agreement has since been published, and some further documents have been leaked to the Signpost. See Signpost coverage.
Andreas Kolbe has been a Wikipedia contributor since 2006. He is a member of the Signpost's editorial board. The views expressed in this editorial are his alone and do not reflect any official opinions of this publication. Responses and critical commentary are invited in the comments section.
As announced by the WMF's Patrick Earley on the Wikimedia-l mailing list, a report on the results of the 2015 Harassment Survey has been released:
“ | This information is an important factor in gaining a better understanding of both the forms harassment takes and the impact it has on the Wikimedia projects. We welcome your feedback and impressions on the Research talk page on Meta. | ” |
The survey results have been discussed on both Jimmy Wales' talk page and on the survey's talk page on Meta. Volunteers have questioned some of the results and alleged design defects in the survey, and WMF staff have responded.
Wikimedia Foundation Executive Director Lila Tretikov announced on February 8 on the wikimedia-l mailing list that Luis Villa is leaving the WMF:
“ | Dear all,
I am sad to let you know that Luis Villa, our lead for the Community Engagement department, will be leaving the Wikimedia Foundation. A year ago, Luis took on a big challenge, transitioning from the Legal Department to lead the newly created Community Engagement organization. In that role, Luis and our teams were tasked with many recent community initiatives, such as the creation of the Community Tech team, gender-related and anti-harassment programs, and improved alignment of WMF annual planning with the Funds Dissemination Committee. Prior to that, as Deputy General Counsel he was responsible for a number of legal initiatives, including licensing, contracts, and product counseling. I’m grateful for his counsel, and his leadership in the WMF movement throughout these years. Later this month, Luis will transition out of his current position with the Wikimedia Foundation to pursue other opportunities. He will remain in a consulting role with the Foundation over the next few months, continuing to support our ongoing strategy and annual planning processes. [...] Maggie Dennis [a.k.a. Moonriddengirl] will step in as the interim director for the CE team effective immediately. Her deep community background, passion for our mission, and outstanding teamwork are great assets in this transition. She will also continue to serve as Director of Support and Safety. Maggie is a respected leader, colleague, and community member. I am confident she will bring critical insights, especially now as we plan for our next year. |
” |
Lila Tretikov has released some background information on the knowledge engine grant on her user talk page in Meta.
For this issue of the Arbitration Report: We recap the decisions the Committee has made from 14 January to now.
It's pretty clear what's on Wikipedians' (read: Americans') minds this week: The fiftieth Super Bowl, which kicks off on 7 February. Past Super Bowls have frequently overwhelmed the top 25 with related articles, which is all the more astounding because the event is of little or no importance to the rest of the world.
For the full top-25 list, see WP:TOP25. See this section for an explanation of any exclusions. For a list of the most edited articles of the week, see here.
As prepared by Serendipodous, for the week of 24 to 30 January, 2016, the 10 most popular articles on Wikipedia, as determined from the report of the most viewed pages, were:
Rank | Article | Class | Views | Image | Notes |
---|---|---|---|---|---|
1 | Royal Rumble (2016) | N/A | 1,557,865 | Wikipedians love their wrestling, but none more so than the annual WWE Royal Rumble, which usually finishes either at or near the top of the list in normal weeks (though it wouldn't have stood a chance in the previous few weeks). What is Royal Rumble, you might possibly ask? Well it's when 30 or so guys fight in the same ring until one is left. For the record, Triple H (pictured) was the last man standing, beating previous winner Roman Reigns. | |
2 | Zika virus | 1,354,360 | This unassuming flavivirus had, since its discovery in in Uganda in 1947, been seen as a meek also ran when stood among its more formidable cousins, such as Dengue, Yellow fever and West Nile. Whereas those could often prove fatal, Zika symptoms mostly compared to a nasty case of flu. However, its sudden pandemic spread throughout the Americas has triggered a panic in the US, particularly after a potentially related spate of microcephalic childbirths in Brazil. | ||
3 | Cam Newton | 1,319,633 | Super Bowl 50 is due this week, and Wikipedians have once again reduced the game to a duel between quarterbacks. Cam Newton, the quarterback for the Carolina Panthers, has earned substantially more views than his rival Peyton Manning, below, perhaps due to controversy over his behaviour, which has been described as arrogant, leading to charges of incipient racism. | ||
4 | Peyton Manning | 947,294 | After injury and concerns as to his increasing age, the popular quarterback for the Denver Broncos led his team to their second Super Bowl in three years. | ||
5 | Airlift (film) | 887,316 | An Indian war thriller film released on January 22. Akshay Kumar stars. | ||
6 | The Revenant (2015 film) | 807,384 | Alejandro González Iñárritu's Western survival epic starring Leonardo di Caprio (pictured) continues to be popular in the leadup to the Oscars, having earned nearly $300 million worldwide as of 4 February. | ||
7 | Republic Day (India) | 801,807 | The annual holiday in India celebrating the Constitution of India on January 26 got nearly double the views of last year. | ||
8 | Super Bowl 50 | 758,841 | The fiftieth annual clash between the National Football Conference champions (Carolina Panthers this year) and American Football Conference champions (Denver Broncos this year) will be held on 7 February at the Levi's Stadium outside San Francisco (pictured) with the Panthers favourites to win. | ||
9 | The X-Files (miniseries) | 745,805 | Despite "meh" reviews, the brief revival of the 1990s cult hit paranormal investigation series has proven relatively strong in the ratings, leading to speculation that it may make a more permanent return. | ||
10 | Steven Avery | 713,641 | Avery is an American prisoner who is the subject of the popular new Netflix documentary series Making a Murderer which was released on December 18. (Episode 1 is available free on YouTube.) Avery served 18 years in prison, from 1985–2003, after being framed by the local police for a sexual assault he plainly did not commit. During his subsequent civil lawsuit for compensation, during a period of explosive depositions, he was charged with the murder of a local photographer, and later convicted. The documentary is compelling to watch, and it causing a fair amount of controversy, and thus bringing continuing attention to this article. |
Eight featured articles were promoted this week.
Five featured lists were promoted this week.
One featured portal was promoted this week.
Six featured pictures were promoted this week.