On Thursday, Bristol Girl Geek Dinners hosted a joint event at the University of Bristol with Wikimedia UK to try to encourage and help women edit Wikipedia. The session was led by Fiona Apps (User:Panyd, an administrator on English Wikipedia) and was supported by Martin Poulter (User:MartinPoulter). As with all Girl Geek Dinner events, the primary audience was women and men could attend if they accompanied a female attendee. Wikimedia UK provided food and drink including a cake decorated to look like the Wikipedia globe.
At the event, after a talk about how to edit and how to avoid the pitfalls, the audience pulled laptops out and started editing. A second presentation soon followed with discussion on some of the problems new editors (both male and female) face including unexplained reversion of their changes and the "excessive zeal" of some experienced Wikipedians in reverting, warning and deleting new content and tagging articles with cleanup tags. Fiona responded by explaining to new contributors about how to resolve disputes on the discussion page.
According to a writeup on the Bristol Wireless blog, "the Bristol Girl Geeks were almost unanimous in their criticism of the Wikipedia editing interface". The event was also written up at thefreshoutlook.com.
The Signpost spoke to Fiona about the event:
Whose idea was having a Wikipedia-related Girl Geek Dinner?
In discussions of gender gap (and systemic bias) issues on Wikipedia, the overall issue often gets obscured by the examples: baseball cards vs. fashion designers, Mexican feminist writers vs. video games. These examples are always inevitably followed by someone pointing out that it is sexist to presume that women are interested in fashion designers rather than baseball cards. Was topic choice something that women attending had any strong opinions on?
There were newbies editing at the event: how did they get on? Any new pages get created? Anyone have any particularly good experiences?
Have you got any thoughts on how the community or the Foundation might help meet the rather modest goal Sue Gardner has set of increasing participation by women? And do you think the participation gap might extend to other groups like ethnic minorities, religious groups, LGBT people etc.?
Do you know if there are any plans to have future Wikimedia events in the UK on women editing Wikipedia, either through the Girl Geek Dinners or independently?
Wikipedia and its ability to be freely edited by anyone has again come under media scrutiny this week after the Toronto Star published a falsified quote attributed to Mike Gillis, the general manager of the Vancouver Canucks ice hockey team, made about former Canucks forward Rick Rypien, who died earlier this week. (The story was later corrected with an accompanying apology, after Gillis and the Canucks criticised the newspaper in a statement.) This is not the first time that journalists have made such a blunder; for example, many newspapers included an erroneous quotation attributed to Maurice Jarre after his death in 2009 (see previous Signpost coverage).
An intern at the Star had found a quote supposedly by Gillis on Wikipedia attributed to the Vancouver Sun, and did not verify its accuracy before including it in his story. His editor likewise assumed that the quote was accurate, as the story did not reference Wikipedia. As a result, Michael Cooke, the Editor of the Star, sent out an internal memo telling writers to verify the accuracy of information obtained from Wikipedia. In the memo, he noted numerous problems with his own biography in Wikipedia, including the fact that "up until a month ago it had me graduating from a university in New Zealand. I have never stepped foot in that country. Other errors remain."
In response, Kathy English, the public editor at the Star, has written an opinion piece titled "Don't trust Wikipedia". In it, she cites a Wikipedia essay, "10 things you did not know about Wikipedia", which says "we do not expect you to trust us", and ends her piece by noting that journalists must know what information to trust, in order to maintain their readers' trust.
A discussion on the administrator's noticeboard highlighted the fact that the quote had been sourced to an online reference (which the Star writer had failed to check), initially reproducing the original faithfully, but then tampered with by a vandal.
Recently, several online publications have focused on a topic of recurring relevance to Wikipedia editors intent on policing its strict policy on neutrality: questionable editing of the encyclopaedia by public relations professionals. The search engine result prominence of Wikipedia, the apparent openness of editing, and its perceived status as a "good enough" authority of neutrality and illumination for a wide breadth of topics make direct engagement with the site perennially attractive to those tasked with improving the online profile of celebrities, products and institutions.
For example, edSocialMedia have released a guide to Wikipedia for educational institutions, advising the addition of flattering photographs, promotional Facebook links, and lists of prominent alumni, and highlighting the Worcester Academy article as a particularly well-written article in the latter regard. Ragan's PR Daily also issued guidance, but noted the potential ethical difficulties for public relations professionals seeking to engage with the encyclopaedia; the four "rules of engagement" offered were "establish notability', "be transparent", "avoid jargon", and "ask for help". In a press release for its own guide, EreviewGuide.com adopted a wary tone, with media relations consultant Oliver Thompson counselling would-be editors of the "dark side" of the project; that "Wikipedia can easily become a trap," and "If used improperly, Wikipedia can get you expelled for plagiarism, can torpedo your term paper grade, can cause professional embarrassment and all sorts of headaches. People need to use Wikipedia with proper tools." Its extensive and well-informed "Wikipedia Survival Guide" encouraged prospective contributors to "read other Wikipedia entries first", "balance opposing views", "for every assertion or claim, offer support", "keep the correct hierarchy of sources in mind", and "no anonymous edits". Notable by its omission was seeking recourse to Wikipedia's internal help network, which is undergoing revision to counter accusations of hostility towards newcomers.
This week, we turn our attention to WikiProject Animation. Started in September 2006 by Klingoncowboy4, the Project covers all articles about animation, including animation studios, animators, animation directors, animated television series, animated films, animated characters and so on. It does not cover any anime series or films. Home to more than 15,800 articles, with 44 Featured articles, 31 Featured lists, 4 Featured media, 473 Good articles, and a portal, the Project has 19 participants and 18 work groups. The Signpost interviewed Project member Jj98.
Tell us a bit about yourself, and what motivated you to become a member of WikiProject Animation?
Your Project has over 15,800 articles associated with it. How does the Project keep all these up to standard, and what are its biggest challenges?
WikiProject Animation has a very respectable number of Featured content, and 477 Good articles. How did your Project achieve this and how can other Projects work toward this?
Does WP:TOON collaborate with other WikiProjects?
How does your Project manage the Animation portal?
What are the most pressing needs for WikiProject Animation? How can a new contributor help today?
Anything else to add?
Next week, it will be 30–love with your turn to serve. Keep track of all the points, sets, games, and matches in the archive.
Reader comments
Two lists were promoted:
No articles were promoted to featured article status over the past week.
How it all started. JJ's particular interest in nature photography was driven by an abiding interest in animal behaviour and a passion for watching wildlife. "I had a few favourite experiences, but they were more to do with observing wildlife than photographing it. I'll always remember some of those early encounters. Like seeing a wild Spotted-tail Quoll bound around the New Pelion Hut in the alpine central highlands of Tasmania—but frustratingly, the right photographic equipment was days' walk away. Or watching a Black-faced Cormorant fish a few metres underneath me as I was snorkelling—but no underwater camera! Or the amazing sight of thousands of waders and shorebirds in Thailand—often in the distance. And I've had a Yellow-throated Honeyeater steal a lock of my hair to use in building its nest." But he warns that some of his memorable experiences haven't been so pleasant. "I get bitten by members of what are commonly known as bull ants pretty regularly, and I've come fairly close to stumbling on poisonous snakes a few times."
So how did JJ learn the art and technique of nature photography? "I guess you could say I'm an autodidact; the internet has been a particularly useful source of information. The reviewers at featured picture candidates gave valuable technical feedback, although while that trains you to identify problems, it doesn't directly teach good technique. I guess the big one is field craft, which requires you to develop knowledge about your subjects, including the best locations and times of year to photograph them. But even knowing these things doesn't allow you to predict what will happen when you go out: you might have a vague idea of what to expect for a given habitat, but usually you can't predict specifically what you'll come across."
JJ settled on birds as his primary interest because they're the most challenging subject he has tried. "The biggest hurdle is that most of them are small, and afraid of you." But the technical problems of photographing birds in the wild go beyond the subjects themselves: "The best times of day are dawn and dusk, and many species can be found only in low-light environments. This throws up many challenges. Even at high ISOs, the slightest camera or subject movement will result in motion blur. My solution is to shoot lots of photos with a remote shutter release; I might get only a few sharp frames out of dozens."
Thailand. During February, JJ spent several weeks in Thailand photographing birds. There he captured images of species that have no coverage at all on Commons, and in some cases no article on Wikipedia. These images have since been trickling through to the nominations page at featured picture candidates as he's processed his work—selecting, uploading, categorising the images, and allocating them to articles on the English Wikipedia. "I knew from experience at home that my chances of finding the best spots were basically nil in two weeks. So the critical thing was to find and engage a local professional bird guide. His name's Reang, and he has expertise in the birds of Thailand; he's been a guide for more than eight years and speaks reasonably good English."
The Thai jungle they visited is very dense, and this made photography difficult due to low light conditions and the dense foliage that physically obscures the subjects. This effect was exaggerated because JJ was "blind" as far as recognising bird calls goes: "that's where Reang's skills were really important", he says. The other technical novelty for JJ was shooting from a boat. "This was not something I’d tried much before, and it has its own challenges. Any boat movement is greatly exaggerated with a telephoto lens. I spent about two days taking photographs from boats. The first time we started here and journeyed down a coastal river for a few kilometres and out into the ocean. The second time we started here, on a sort of lake with rice fields on the edges." (See the picture at the right, of JJ with telephoto lens on the boat about 15 minutes after starting from the side of that lake. Lotus plants can be seen either side of the wake.)
From land, he took some of the photos from inside a car: "birds ignore cars, but take flight if you get out (I shoot from a car at home occasionally, too). But there were opportunities outside from the roadside too, particularly at Kaeng Krachan, where we walked along trails. At that location, there seemed to be only bird watchers and photographers—mostly Thais. We also spent quite a lot of time in portable hunting blinds in areas birds frequent, such as drinking holes and the ubiquitous rubbish dumps, which contain food scraps that attract birds but, ultimately, are damaging the intricate ecosystem.
Queensland. JJ undertook a photographic trip to the northeastern part of the continent in July. This involved travelling to Cairns and from there along the coast, which is mainly rainforest. Because the moisture content of the habitat is dramatically reduced away from the coast, his work extended to the very different bird species that can be found up to 50 kilometres (30 mi) inland. His output from this trip is now making its way to the featured picture candidates page. Two successful nominations are displayed at the top of this section.
Ethical considerations. JJ says you need to be conscious of the ethics of photographing wildlife. "It mostly pertains to both your subjects and their environment. Feeding birds is usually a bad idea: it will probably help feral species out-compete native species; long-term feeding may also cause dependence among wildlife species, increase competition for (nesting) tree hollows, and spread disease. (I have used bait, but only for one night each in different locations—kangaroo pellets for the Eastern Bettong and Eastern Barred Bandicoot photographs.) Be careful not to damage the environment itself—don’t trample vegetation. In certain areas it's important to wash your shoes and tripod to prevent the spread of disease. Don’t move closer to birds if they're showing signs of stress. If they do fly away, don’t repeatedly follow them. You can get closer by moving slowly and using natural cover; and do avoid loitering around nesting birds."
We asked whether there are differences in the practice of wildlife photography in Thailand compared with what he's used to: "The same broad practical and ethical considerations apply, but every species is different—I wasn’t there long enough to really learn the nuances in behaviour among species. One thing I became aware of is that the use of recorded bird calls to attract subjects into position is much more prevalent. Recordings should be used sparingly in my view. And it seemed that far fewer species in Thailand depend on seeds or nectar, and that feeding on fruit is more common than in many parts of the world."
Opportunities for Wikimedians. Much of JJ's photography involves Tasmanian wildlife. Does he plan to widen his geographical purview? "I don't expect I'll live in Tasmania forever—to start with, I'll need to move for postgraduate studies in the next few years. I've probably been able to get featured images for about a third of the bird species in the state (and less than that for mammals), so there's still plenty of work to be done. Please, we need more photographers contributing to Wikimedia sites, and more editors collaborating with them to write articles." JJ says that Wikimedia has good photographic coverage, and usually at much better resolution than Flickr, in which only 800 × 500 px is typical. "However, the distribution of featured pictures is patchy. For example, I'm surprised how little coverage there is for western Europe and North America. There's lots to be done just about everywhere." He says many Wikimedians don't realise how well-positioned they are to photograph wildlife in other parts of the world. "Once you start to identify species, you'd be surprised just how many are around you. Pay attention to bird calls—they're more useful than your eyes for locating subjects."
This was another active week for the Arbitration Committee. One new case has been opened, for a total of four active cases. Details of cases are correct as of Saturday, August 20.
The Senkaku Islands dispute—over a group of five islands in the East China Sea administered by Japan since 1972 but claimed by China—is itself the subject of dispute here on Wikipedia along with its parent article Senkaku Islands.
The figurehead point of controversy appears to be the name, Senkaku Islands, which, as the Japanese name, has been alleged as supportive of the Japanese side in the dispute. As a result, a handful of editors have been pushing for the Chinese name instead, and many arguing for the anglicized The Pinnacle Islands as a correct, NPOV descriptor. The point has seen many discussions, an RFC, and mediation. Since 2005 the article on the Senkaku Islands has been moved eleven times, but is now back where it started. To what extent the article should acknowledge the other names of the islands has also been a point of edit warring, with the current text including significant coverage. Comparisons to the dispute of the name of the Liancourt Rocks—islands claimed by both Japan and South Korea—have been drawn. In that dispute, an anglicized name was chosen over the Korean or Japanese names, although the dominant consensus has consistently been that "Senkaku Islands" is the name most commonly used in English publications for the islands. Edit warring in the body of the two articles has also been significant, with many users feeling that the article endorses the Japanese claim to the islands.
The dispute has seen established users in good standing on both sides of the issue.
The request was opened on August 13 by Qwyrxian who wrote that (s)he has "come to believe that until the behavioral problems are corrected, we will be unable to make constructive progress on the article content". Eleven parties gave statements and the case was accepted unanimously by eight arbitrators with one recusal. Arbitrator Coren wrote in his acceptance that the Senkaku Islands dispute is "a relatively simple case where it's likely consensus could be reached if everyone behaved and where Arbcom could help by making sure everybody does."
Since its opening on August 17 it has seen little activity so far; STSC and Penwhale have presented brief statements of support for the position that 'Senkaku Islands' is not NPOV. Tenmei has posted some stock principles in the workshop.
No drafting arbitrator has been assigned yet.
The case, which centers on the naming of abortion-related articles and related behavioral issues, proceeded into its second week. Three more uses have presented evidence this week:
In the workshop Steven Zhang proposed some very broad principles and remedies, Anythingyouwant and HuskyHuskie proposed principles, findings of fact, and remedies in line with their respective sides of the dispute.
The case involves allegations of non-neutral editing by Cirt and also allegations against Jayen466 that he has stalked and harassed Cirt. Three more users presented evidence this week,
The case, which was broken off from the Cirt and Jayen466 case to be a somewhat unusual investigation of BLP policy, proceeds into its third week. The sluggish addition of actual evidence submitted remarked upon last week appears to have ameliorated. This week nearly twice as much evidence was presented as in the first two weeks of the case combined.
The workshop saw little new this week, a few very pointed questions—with the subtext that the case was being unfair to Cirt—for Cla68 from Jehochman and another pointed question from Prioryman for Delicious Carbuncle listing a post of his on Wikipedia Review and asking him to explain. Also a Mathsci posted two standard "proposed principles" adapted from previous ArbCom cases on Decorum and Conduct on arbitration pages, urging civility.
Last week John Vandenberg noted a trend where abstention votes were being increasingly used to give vote-like opinions, which he noted was "causing elements of arbitration cases and motions to technically pass or fail while the abstain section contains many arbitrator votes consisting of comments heavily leaning for or against". He stated that "The Arbitration Committee needs to review its use of abstention in order to ensure that the committee position on an issue is clear and that they have the requisite support to provide legitimacy for that position." This has been the first time the issue has surfaced around ARBCOM, and the need for a motion was questioned. "Well, I probably would have gone for discussion before writing motions, but meh" wrote Risker, however John Vanderberg's proposal did lead somewhere; after going through six drafts, the motion passed, creating a new "comments" section in addition to the support, oppose, and abstain sections, and advising arbitrators that "abstention votes as a vehicle for comments [... are] not recommended". The motion also guarded against slacktavism, stating "an arbitrator who posts a comment is also expected to vote on the proposal".
Reader comments
The Wikimedia Foundation's Engineering Report for July was published last week on the Wikimedia Techblog and on the MediaWiki wiki, giving an overview of all Foundation-sponsored technical operations in that month. Many of the projects mentioned have been covered in The Signpost, including the deployment of the MoodBar, ArticleFeedback and WikiLove extensions. Among those yet to have received significant coverage but that were highlighted in the report were "the successful implementation of a MySQL-based parser cache on Wikimedia wikis" and work on a "Wikimedia Report Card 2.0".
There was good news for performance, too. Seventy-four new servers were purchased to increase the capacity of our Apache cluster to be installed this month, whilst the reliability of database dumps also settled down after a rocky June. The work on the parser cache was also successful, improving the hit rate (the percentage of requests which do not force the server to regenerate the page from scratch) to 80%, from 30%. On the software side, Roan Kattouw and Timo Tijhof worked on delivering "global gadgets and a gadget manager". According to the report, the "back-end for loading gadgets remotely from another wiki" is now in a workable state, as is an "inventory" of available gadgets.
The HipHop deployment, AcademicAccess, App-level monitoring, and Configuration management projects were "mostly on hold" in July, as was work on LiquidThreads 3.0. Documentation of the status of projects came under more scrutiny in July under the guidance of Guillaume Paumier, now the Foundation's Technical Communications Manager. Paumier "continued to create, update, clean up and organize the project documentation pages for most engineering activities" during July, according to the report, which is itself authored by him.
July also saw the arrival of Jeff Green (Operations Engineer for Special Projects), Ben Hartshorne and contractor Daniel Zahn (Operations Engineers) and Ian Baker (Software Developer). At the same time, however, Chief Technology Officer Danese Cooper and Code Maintenance Engineer Priyanka Dhanda left the Wikimedia Foundation.
Also published this week was a detailed insight into the present fundraising team, who are responsible for making sure Wikimedia websites have the capability to maximise the fundraising potential that the annual drive afford them. It is currently led by Arthur Richards and also includes two developers, an operations engineer, a data analyst, and a general business analyst. The team for this year's fundraiser has now been working on that fundraiser since approximately May, according to the post.
From a technical point of view, Richards stressed that good "code hygiene" was a must, including writing unit tests for all the code they produce in two-week code "sprints". The sprints focus around specific goals which the team can track using the proprietary software Mingle. "While we would much prefer to use an open-source solution, we settled on this proprietary tool as it much more closely meets our needs than any of the others we explored" wrote Richards. Examples of sprint targets include improving the banner tracking system to allow for results to be filtered. This allows the team to improve the banner range available to maximise the number of visitors who see the value in donating to Wikimedia. This year's campaign will again feature localised banners and user stories.
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.
Try out the latest beta of Kiwix, the offline Wikipedia reader. Then leave feedback for its development team.