Home  

Random  

Nearby  



Log in  



Settings  



Donate  



About Wikipedia  

Disclaimers  



Wikipedia





Wikipedia:Wikipedia Signpost/2016-01-13/Community view





Project page  

Talk  



Language  

Watch  

View source  


< Wikipedia:Wikipedia Signpost | 2016-01-13
 


The Signpost
View Latest Issue


Community view

Battle for the soul of the WMF

Contribute  —  

Share this

  • Facebook
  • Twitter
  • LinkedIn
  • Reddit
  • Digg
  • ByLiam Wyatt


    Wikimedia Foundation Executive Director Lila Tretikov with Board of Trustees member Jimmy Wales


    This week is Wikipedia’s 15th birthday, the first draft of the long awaited strategic plan of the Wikimedia Foundation will be published for comment, and last week was its annual All Hands employee meeting. Meanwhile, there is a battle going on at the top for its soul.

    Related articles

    Knowledge Engine

    WMF strategy consultant brings background in crisis reputation management; Team behind popular WMF software put "on pause"
    6 February 2017

    Knowledge Engine and the Wales–Heilman emails
    24 April 2016

    [UPDATED] WMF in limbo as decision on Tretikov nears
    24 February 2016

    Search and destroy: the Knowledge Engine and the undoing of Lila Tretikov
    17 February 2016

    New internal documents raise questions about the origins of the Knowledge Engine
    10 February 2016


    More articles

  • over the last year, there has been extreme "churn" in senior staff, as noted by William Beutler (WWB) and MZMcBride and most notably by former WMF Director of Features Engineering Terry Chay;
  • there has been a "transparency gap" including the mid-2015 major, yet secretly planned, "re-org" of the engineering department (see the list on this talk page);
  • last week was the unprecedented dismissal of Dr. James Heilman (Doc James), a community-recommended member of the Board of Trustees who I personally know and trust, due to a loss of “mutual confidence”. The decision was persuasively defended by Denny Vrandečić, a community-recommended member of the Board who I also know and trust, but with insufficient justification for many – including the longest-serving employee of the WMF, Tim Starling;
  • this week, in a blow in terms of diversity-of-perspectives, two American, San Francisco bay-resident, tech industry insiders, have been appointed to the Board – one of whom (appointed specifically for his human resources experience) was named in a US Department of Justice investigation into anti-competitive wage-fixing cartel among tech companies, as comprehensively summarised by Jim Heaphy (Cullen328)
  • It is my supposition that this is not a list of unrelated incidents, but that this is part of a wider theme: That a portion of the Board of Trustees and the Executive Director of the Wikimedia Foundation believe that it should be treated as a technology organisation in the style of a dot-com company, out of step with the staff and without the awareness of the community. By contrast, it’s always been my belief that the Wikimedia Foundation is an education charity that happens to exist primarily in a technology field. Of course software engineering is crucial to the work we do and should represent the major proportion of staff and budget, but that is the means, not the end.

    All this background makes the draft Strategic Plan a very important document. For the 2010-15 plan there was a massive community consultation project, but this time around there was only a 2-question survey. As Philippe Beaudette (Philippe), the Community Facilitator on that original strategy process and later the WMF Director of Community Advocacy (who also recently left the organisation), said to me [with permission to publish here]:



    The November staff presentation gives a strategy preview that speaks of three priorities (slides 28-30): “1. Engage more people globally (reach) 2. Facilitate communities at-scale (community) 3. Include broader content (knowledge)”; and describes a need to “prioritise core work” (slides 32-33). All laudable goals, but they only include “example objectives” such as “build capacity”, “improve trust”, and “improve tools”.

    Nevertheless, I suspect that the major strategic direction has already been privately determined. In short, it appears there will be an attempt to create the internet's Next Big Thing™ at the expense of improving the great thing that we already have.

    The "knowledge engine" which is the source of much debate over transparency and the direction of the WMF.

  • The June staff presentation “strategy preview” talks about creating a “knowledge engine where users, institutions and computers around the world contribute and discover knowledge”. The FAQ page for the “Discovery department”, describes this project as “…improving the existing CirrusSearch infrastructure with better relevance, multi language, multi projects search and incorporating new data sources for our projects.”
  • In September, the Knight Foundation announced a grant of $250,000 to build a "knowledge engine". This was announced by the WMF two days ago. This is a “restricted grant” but, as has been describedbyPete Forsyth, there is none of the associated documentation – for example the formal grant deliverables – except for a short FAQ.
  • As mentioned above, we now have two new Silicon Valley executives appointed to the Board of Trustees. They join the previously appointed member of the board Silicon Valley venture-capitalist Guy Kawasaki, as well as internet entrepreneur Jimmy Wales himself. There is no one appointed for their professional experience in education, charities, communities, or developing countries.
  • While I agree with the general premise that the search system on the Wikimedia projects can be improved, I don’t know anyone who thinks "an indexed & structured cache" of "Federated Open Data Sources" should be the strategic priority. Starting something entirely new like Federated Searchishard and trying to include external sources (that link also suggests trying to also integrate the US Census, and the Digital Public Library of America) is even harder, especially when there are so many existing technical needs. Quoting Philippe again: "for instance, fixing the inter-relationships between languages and projects, or creating a new admin toolset for mobile, or paying down our technical debt, or establishing a care/command/control operation for critical tools to ensure their sustainability, etc...."

    The Funds Dissemination Committee (on which I sit as a community-elected member) declared in November that it is『…appalled by the closed way that the WMF has undertaken both strategic and annual planning, and the WMF's approach to budget transparency (or lack thereof).』In response, the WMF is considering submitting its 2016-17 annual plan, based on the aforementioned strategic plan, to a "process on-par with the standards of transparency and planning detail required of affiliates going through the Annual Plan Grant (APG) process".

    We will see over the next weeks to what degree the apparent shift towards a Silicon Valley mindset – whether the staff and community like it or not – is indeed true. As the then-Chair of the Board Jan-Bart de Vreede said in describing Lila Tretikov’s appointment as Executive Director:

    Slides presenting the three-year roadmap of the WMF Discovery department.



    Meanwhile, you might be interested in the roadmap for the Discovery department or for the more technically minded there is the "Discovery" workboard on Phabricator and associated mailing-list. Finally, for what it's worth, the term "knowledge engine" itself is now deprecated.


    This article was originally posted on the author's blog and is reprinted with his permission.

    S
    In this issue
    13 January 2016 (all comments)
  • In the media
  • Community view
  • Editorial
  • In focus
  • Op-ed
  • Traffic report
  • Special report
  • News and notes
  • Blog
  • Featured content
  • Arbitration report
  • Technology report
  • + Add a comment

    Discuss this story

    These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.
    == Engine ==

    I don't want to become a part of a knowledge engine. I want to be a member of a community that makes and shares educational resources.

    Wikipedia's search engine isn't very good and should be improved. But building a new project to collect information even less structured than Wikidata is far from our needs and wishes.

    I agree that the board should have several members from educational backgrounds. Technology is a tool, the strategic goals are educational. --NaBUru38 (talk) 15:41, 17 January 2016 (UTC)[reply]

    Discovery is actually devoting the lion's share of its resources trying to improve the existing search, and that's reflected in Discovery's quarterly goals. An example of our work towards this is the completion suggester beta feature, which we recently rolled out, which improves the search algorithm used for the type-ahead search. We're also trying to improve search for multi-lingual users with language detection. It's an incredibly common misconception that the "knowledge engine" represents some new and significantly different direction which does not involve significantly improving our core search, and that's why we've now stopped using the term. --Dan Garry, Wikimedia Foundation (talk) 19:08, 18 January 2016 (UTC)[reply]

    The Signpost is written by editors like you — join in!

    Archives

    Newsroom

    Subscribe

    Suggestions


    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Wikipedia_Signpost/2016-01-13/Community_view&oldid=1193875734"
     



    Last edited on 6 January 2024, at 02:24  


    Languages

     



    This page is not available in other languages.
     

    Wikipedia


    This page was last edited on 6 January 2024, at 02:24 (UTC).

    Content is available under CC BY-SA 4.0 unless otherwise noted.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Terms of Use

    Desktop