According to a post by William Pietri, project manager for the Flagged Revisions Deployment Project, the flaggedrevs extension will be deployed on the English Wikipedia on June 14.
Unlike other projects such as the German Wikipedia (where the extension has been live since 2008), the English Wikipedia will make use of only the "flagged protection" feature, which has been renamed "pending changes" following extensive discussion on the mailing list Foundation-l and the terminology subpage. It allows administrators to apply a new kind of protection to a page, under which it can still be edited by every user, but the change will not be visible (in the default view) to unregistered users unless it has been made or confirmed by a trusted user.
The feature will be activated only for a trial, which is expected to last two months and will be limited to a maximum of 2,000 pages. The trial is likely to generate considerable media attention, given the fact that its mere announcement last August has already received coverage (see Signpost story).
A new help page, with which Pietri has requested assistance, is here. Some diagrams explaining the terminology are here. The feature can be tested out before deployment on the flaggedrevs test wiki.
There was some debate in a recent RfC on whether or not the trial configuration should involve the separate "Reviewers" user rights group or use the existing "Autoconfirmed" group as the trusted users group. Some technical details of the deployment are still being hammered out.
The following table summarizes permissions under current settings for the trial (more details here):
Unregistered or newly registered | Confirmed or autoconfirmed | Extended confirmed | Template editor | Admin | Interface admin | Appropriate for (See also: Wikipedia:Protection policy) | |
---|---|---|---|---|---|---|---|
No protection | Normal editing | The vast majority of pages. This is the default protection level. | |||||
Pending changes | All users can edit Edits by unregistered or new editors (and any subsequent edits by anyone) are hidden from readers who are not logged in until reviewed by a pending changes reviewer or administrator. Logged-in editors will see all edits, whether accepted or not. |
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users. | |||||
Semi | Cannot edit | Normal editing | Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules. | ||||
Extended confirmed | Cannot edit | Normal editing | Normal editing* | Normal editing | Specific topic areas authorized by ArbCom, pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive. | ||
Template | Cannot edit | Normal editing | High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space. | ||||
Full | Cannot edit | Normal editing | Pages with persistent disruption from extended confirmed accounts. Critical templates and modules. | ||||
Interface | Cannot edit | Normal editing | Scripts, stylesheets, and similar objects central to operation of the site or that are in other editors' user spaces. | ||||
* In order for a template editor to be able to edit extended confirmed protected pages, they must also be extended confirmed, but in practice this is almost always the case. | |||||||
Other modes of protection:
|
See also the Signpost's backgrounder on the history of the extension (An extended look at how we got to flagged protection and patrolled revisions, August 2009) and other Signpost coverage dating back to 2006.
The Wikimedia Foundation has hired two new employees: Zack Exley will be Wikimedia's new Chief Community Officer, and Barry Newstead will be the Chief Global Development Officer. According to an FAQ about the positions Exley will be in charge of programs, including Fundraising, Reader relations, Public outreach, and volunteer coordination; Newstead will be in charge of Communications and Business Development.
Zack Exley has worked in high-profile positions organizing fundraising and volunteer activities for MoveOn.org, the 2004 U.S. presidential campaign of John Kerry, and the UK Labour Party's 2005 election campaign. In recent years he has advised other organizations on similar issues, including the ACLU, Amnesty International, the NAACP, the International Rescue Committee and Greenpeace USA. He also ran the parody website gwbush.com.
Barry Newstead is currently a partner at the strategy consultancy firm The Bridgespan Group, where he has been leading the team assisting the Foundation in the Strategic Planning process since last year. Newstead has written a series of blog postings about the process on the web site of the Harvard Business Review. In one of his first postings, Newstead expressed concern that the inner Wikipedia community might not be "open to more radical strategic options that might advance the vision", citing the "near-taboo" of advertising as one possible example. However, in a later posting, Newstead offered huge praise for the contributions of Wikipedia volunteers to the strategy process.
Originally, the Foundation had set out to hire a Chief Development Officer, responsible for fundraising (a common position in non-profits) and a Chief Global Program Officer (responsible for relations with Wikipedians and readers). According to a Q&A and a separate announcement to the community by the Foundation's executive director Sue Gardner, the CDO role was expanded to that of a Chief Community Officer, at the suggestion of Exley, who argued that donors should be regarded as part of the same community as editors and readers, instead of being treated separately.
According to Gardner, filling these positions is the result of a search process of "many months", and "completes the C-level hiring, with the exception of the Chief Human Resources Officer", which is expected to be announced within six weeks. (The other two C-level posts are the Chief Financial and Operating Officer, filled by Véronique Kessler since 2008, and the Chief Technical Officer, for which Danese Cooper was hired earlier this year – see Signpost coverage – following the departure of Brion Vibber.)
In an article titled Venerable British Museum Enlists in the Wikipedia Revolution, The New York Times covered the event at length, explaining that the British Museum's motivation to collaborate with Wikipedia is "to help ensure that the museum’s expertise and notable artifacts are reflected in that digital reference’s pages". The article noted that museums and Wikipedia have as their common interest "educating the public: one has the artifacts and expertise, and the other has the online audience", but also mentioned possible conflicts, recalling the legal threats issued last year by the National Portrait Gallery, but not subsequently pursued, against a Commons user who had uploaded high-resolution scans of public domain images from the Gallery's collection (see Signpost coverage). Regarding the Wikimedia side, the NYT quoted Wyatt's objection to what he saw as free culture "extremism": "‘Content liberation’ is the phrase that has been used within the Wikimedia community, and I hate that: they see them as a repository of images that haven’t been nicked yet." (The term "content liberation" has been used in the past by German Wikipedian Mathias Schindler, now project manager at Wikimedia Germany, who had negotiated large scale image donations from Bundesarchiv and Deutsche Fotothek.)
Among the results of the tour are photos and new articles (including several DYK nominations) about the British Museum's artefacts. Unknown to Wyatt, one participant also started the article Wikipedian in Residence.
The Signpost is delighted to report the announcement of the British Museum's Featured Article Prize: five prizes of £100 (≈$140/€120) at their shop/bookshop for new Featured Articles on topics related to the British Museum in any Wikipedia language edition. Ideally, the topics will be articles about collection items.
The rollout of the new user interface on May 13 brought some controversial changes, among them the relocation of the search box, some of the modifications to the Wikipedia logo (see Signpost coverage) and making Wikipedia inaccessible for some rare browsers (on Blackberry and PS3). The controversy about another change culminated only recently, raising fundamental questions about the relationship between volunteer and paid developers, or more generally the Wikipedia community and the Wikimedia foundation.
In the default view of the new user interface, the interlanguage links to articles about the same topic in other Wikipedia language versions are hidden behind a link titled "Languages" (using the "CollapsibleNav" JavaScript module). Once a user clicks on the link, the whole list will be displayed (as in the old interface), until the end of the browser session.
Many users objected to this, and Bug 23497 was filed. On June 3, a volunteer developer made the requested change and restored the old behavior, only to be reverted by a developer from the usability experience (UX) team which had developed the new user interface in a 16-month effort:
Howie Fung later explained the background of the team's decision as follows:
On the Foundation-l mailing list and on the usability wiki, numerous users still questioned the decision. Sue Gardner defended the usability team, arguing that "[t]he folks here on foundation-l are not representative of readers."
Erik Möller, Deputy director of the Wikimedia Foundation, summarized some of the objections as follows:
Möller and Fung outlined a compromise approach, where only a limited number of language links would be shown per default, and the rest would be hidden under a "see other languages" link. Various ideas were discussed on how to generate a selection that is likely to contain the languages that are most useful to the user (e.g. based on browser language preference). The influence of different configurations on users' clicking behavior will be evaluated.
Altogether, the issue generated more than 160 postings on the Foundation-l mailing list within a few days (although a good part of this was a sub-thread, started by the Chair of the Board of Trustees, about racial, intercultural and gender issues – at one point readers of the list were educated on the origin of the term lynching in the American Revolution.)
In a subsequent post titled Community, collaboration, and cognitive biases, Erik Möller observed that "the massive thread regarding the default sidebar language link expansion state has surfaced a number of fundamental and significant questions regarding the working relationship between the Wikimedia Foundation and the larger Wikimedia volunteer community". He offered a number of general thoughts which he summarized as follows:
Discuss this story
How does one get reviewer rights?--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 23:43, 9 June 2010 (UTC)[reply]
Foundation hires
I must say if Wikipedia started advertising I would consider going somewhere else. It seems that currently fiances are okay so hopefully this will never happen. Doc James (talk · contribs · email) 04:29, 10 June 2010 (UTC)[reply]
British Museum
About [1]: I do think that the existence of the article Wikipedian in Residence is a fact that might interest Signpost readers, many of whom are Wikipedians. However, rereading the previous wording I understand Liam's concern that it might give the wrong impression that he had created that article himself. Hopefully the new wording avoids that misunderstanding. Regards, HaeB (talk) 14:18, 8 June 2010 (UTC)[reply]
Interwiki links
To me, the problem is not that some of those links are hidden (I'm surprised the controversy is over the language links rather than the Toolbox ones, though), but rather that every time my session times out I've got to re-expand the dang list. I don't mind doing it once, but I use "What links here" quite frequently and don't care to have the list hidden by default. Powers T 17:17, 9 June 2010 (UTC)[reply]
(ec) It's hard not to see how the handling of this unwanted change to the default skin as a symptom of an increasingly top-down approach to the Wikimedia communities -- which is directly against the process which has made Wikipedia & related projects so successful. I don't like where that is taking us. -- llywrch (talk) 17:21, 9 June 2010 (UTC)[reply]
It's odd to me. Seems like a solution in need of a problem. Why not just make it a setting under preferences so that an editor can choose based on his or her frequency of use? I personally almost never use them, but sometimes, if I see that FA star, I might check it out to see how it compares to the English article. bahamut0013wordsdeeds 18:21, 9 June 2010 (UTC)[reply]
"Of Monobook and Vector users, 0.95% and 0.28% clicked on the language links " This does immediately show that Vector decreases the number of interwiki clicks by about 3/4 - in other words makes them less usable. If a limited list of languages is displayed, then it needs to be content driven, or at least content drivable - articles about Farsi should display the Farsi link. Certainly weight should be given to displaying FAs in other languages, especially where the home language article is not featured. Rich Farmbrough, 08:52, 10 June 2010 (UTC).[reply]
A small addendum: Following Erik Möller's proposal cited at the end of the story, a page has now been set up on meta to "capture ideas on how the User Experience Team and the Wikipedia Community can collaboratively approach Product Development": meta:Product Development Process Ideas.
Regards, HaeB (talk) 11:04, 10 June 2010 (UTC)[reply]
I would like to add that it shouldn't be all about the click-through ratio. Sometimes just hovering the cursor over an inter-language link (to see where it leads) is all that's needed. This kind of use is not represented by the click-through ratio at all.—Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky) • (yo?); June 10, 2010; 14:38 (UTC)
Chapter-selected seats
As phoebe has a byline in this part, I want to note that the little update on Chapter-selected board seats has not been written by her. (She does take conflict of interest concerns quite seriously.)
Regards, HaeB (talk) 04:15, 9 June 2010 (UTC)[reply]