This means that Durova is roughly 77.33% as popular as Barack Obama. It's amazing what Wikipedia will do.
by Juliancolton (noreply@blogger.com) at November 06, 2009 07:50 PM
by Juliancolton (noreply@blogger.com) at November 06, 2009 07:50 PM
by Lise Broer (noreply@blogger.com) at November 06, 2009 10:58 AM
Waldir has previously guest-blogged here and I am happy to welcome him back for his second post. Congrats on helping make this cool project happen! —Brianna

Image by AntWeb, licensed CC-BY-SA-3.0
written by Waldir Pimenta
Did you know that the most venomous insect in the world is an ant? That’s right. One sting from the Maricopa Harvester Ant is equivalent to twelve honey bee stings — the required amount to kill a 4.5 pound rat.
I found that over a year ago, through University of Florida’s Book of Insect Records. I immediately headed to Wikipedia to see what it had to say about it, but to my surprise there was no such article! I thus started one from scratch, using some information I found in several ant-related websites. Eventually people started adding information to the article, up to the point that it contained a fairly good collection of information about this fascinating species. But still one thing was missing — something that single-handedly could make the article ten times more useful: an image.
So, when searching for images to illustrate it, I found the fantastic images from AntWeb, a project from The California Academy of Sciences, which aims to illustrate the enormous diversity of the ants of the world. I was especially happy to find that they were using a Creative Commons license — but soon after I was disappointed to find that the specific one they used (CC-BY-NC) was not appropriate for Wikipedia (or, more generally, free cultural works, and thus discouraged by Creative Commons itself).
So I sent them an email suggesting them to change the license. When they replied, I found out that they actuallly had been internally discussing license issues for quite a while. I kept in touch, and made sure to let them know the advantages of having their work showcased in such high-traffic websites as Wikipedia, Commons or WikiSpecies.
I like to think that my two cents helped in their decision, some time later, to not only change their license to CC-BY-SA, but also upload all their images to Commons themselves! This was part of their overall mission: “universal access to ant information”. Before, the AntWeb project focused only on digitization of content and development of the web portal; but now they also decided to “export” AntWeb content to improve access. Putting the images and associated metadata in Commons was an example their outreach initiatives.
This was very welcome by the community, and there was a lot of input on how best to perform the mass upload in order to make the images easy to find and be used to illustrate articles and other relevant pages. The process took several days, but finally, over 30,000 images were uploaded, full with EXIF tags, taxonomic data, and geographic information when available.
This is just the beginning, though! As usual in the wiki world, you can help! There are articles to be illustrated in the various Wikipedia language versions (Magnus’ FIST tool comes in handy for finding them!). There are WikiSpecies pages to be illustrated. There are categories in Commons to be created to allow the ant category tree to be navigated and have every ant image reachable through it. And more importantly, there are these great news to spread and let people who are interested in ants know that they can now count on what’s possibly the greatest online repository of free, high-quality ant images.
Many thanks to Brian Fisher, AntWeb Project Leader, who coordinated the license change process, Dave Thau, AntWeb Software Enginer, who wrote the upload script and performed the upload, and to all the AntWeb staff for their outstanding work!
I’m retooling StatusNet’s Sphinx search engine support to pluginize it and better support multiple sites… Putting some notes up on the wiki.
Would love to see any additional issues or suggestions from folks using, or wanting to use, Sphinx for their SN instances!
by Lise Broer (noreply@blogger.com) at November 05, 2009 11:17 AM
I’m thrilled to announce WikiWorks - a MediaWiki-focused consulting company that I just launched. This is my first serious business venture, unless you count Referata. But it doesn’t feel like a huge leap into the unknown, because consulting is already what I do - I’ve done at least some paid MediaWiki work for dozens of sites and companies over the last few years. The difference now is the additional people - WikiWorks is a samll team of programmers around the world, all with significant experience setting up (and, in some cases, developing) MediaWiki; the goal is to make myself expendable, as it were, so projects can run smoothly even if I, or any other one person, can’t work on them at the time. We’re automating the process. Most of us also have other jobs at the moment, but these kinds of projects can almost always be done on a part-time basis, during off-hours; and in-depth projects involving full-time work, should they come, will be handleable in one way or another. The focus is on Semantic MediaWiki-based solutions, though we’re also equipped to take on regular, non-semantic projects.
So - if you’re from a company that would like to set up a wiki the right way, send us an email. If your company has a need for an easily-configured but powerful data integration system, and you would prefer software that’s free to something that costs a million dollars, send us an email. If you have too many Excel spreadsheets flying around the office, send us an email. If you already run a MediaWiki-based wiki, but want to make it nicer-looking, more user-friendly, and more like a true database application, send us an email. We’re looking forward to making some wikis.
The lower left corner on this image makes it a bit more challenging than the other perspective crops of recent posts because the others could all be corrected with a single perspective crop. This requires multiple perspective fixes. After the first set of changes the lower left corner still curls upward and inward. The effect is most apparent at the horizontal border line. That distortion affects the entire far left column of the image.
Here's how it appears after the correction. The change is subtle but it alters the proportions of the figure's hip and spine. Alignment and blending require judicious erasure, partial redrawing of border lines, and minor edits at high resolution.by Lise Broer (noreply@blogger.com) at November 04, 2009 09:31 PM
Maybe you’ve been editing Wikipedia for years. Or maybe you made your first edit a few days ago. Whatever your experience, you likely know at least one central fact about editing – that it can be difficult for newcomers to master the skills necessary for contributing to Wikipedia.
We want to change that, and we need your help. That’s why Wikimedia is kicking off a new project, the Bookshelf Project, developed to extend the reach and improve the quality of Wikipedia articles by increasing participation. We’re designing the Bookshelf Project to create a core set of public outreach materials designed to recruit new, high-value Wikipedia contributors. The idea is that by increasing potential contributor awareness, fostering excitement, and providing the training tools new editors need to get started, we’ll draw many more new editors than we do today. And we believe recruiting new high-value contributors to Wikipedia will necessarily increase the usefulness and quality of our encyclopedia.
Now we already know that many Wikipedia readers have never thought about editing the encyclopedia – even though there’s lots of information available about how to do so. Our goal is to reach out to those editors more actively – both to make them feel welcome and give them a great set of starting tools. We hope to seed the knowledge and enthusiasm about contributing to Wikipedia in such a way that it propagates itself.
We have lots of good reasons to believe this dream is achievable. Here’s one reason: we know anecdotally how easy it can be to inspire someone to edit and to share knowledge about editing. For example, during recent user testing for the Usability project, we interviewed a woman who uses Wikipedia daily, mainly to help her daughter with homework. She is an avid fan but had never edited. During the testing, she edited for the first time and immediately became excited about the possibilities of sharing what she knows and loves with others. She understood and was eager to implement Wikipedia’s core tenets of neutrality and verifiability. And she was eager to go home, share her excitement and recruit others to the effort.
Now, we can’t do one-on-one interviews with every possible new editor. But stories like this one suggest that we can leverage our experience with a few editors in ways that will benefit many more potential contributors. And that is the essence of the Bookshelf materials we plan to develop with your help.
We also plan to tap educational resources, since we know Wikipedia is a fact of life in many educational situations, usually as a reference tool. The Bookshelf Project will support additional educational applications by providing model lesson plans to show secondary school teachers and university professors how they can use writing, editing and collaboration in Wikipedia as core curriculum activities. In developing the Bookshelf Educational materials, we will work with subject matter experts to ensure the materials are relevant and applicable.
The Bookshelf Project will include materials to help journalists and other communications professionals do their jobs more easily, including techniques and information to help them be sure the information they use and the copy they write is accurate and up to date.
The Bookshelf materials will be developed in English and will be designed for translation, adaptation and use by volunteers, chapters and educational institutions such as schools and universities. We will use our new Outreach Wiki for the Bookshelf Project. This will be our place to give updates on the project and to get community feedback. There are lots of opportunities to help out, from acting as subject matter experts, to reviewing, and translation and localization.
We look forward to working together with our community on this initiative. If you’ve been in any way successful as a Wikipedia editor, we would value your input and feedback. There’s more than one way to contribute to Wikipedia’s success, but one major way to contribute has to be in the recruiting and training of new editors. The more we do to bring new, talented editors on board, the more comprehensive, reliable, and useful Wikipedia will be.
Marlita Kahn
Project Manager, Bookshelf Project
by GerardM (noreply@blogger.com) at November 04, 2009 11:01 AM
by GerardM (noreply@blogger.com) at November 04, 2009 09:52 AM
by Lise Broer (noreply@blogger.com) at November 03, 2009 03:37 PM
by GerardM (noreply@blogger.com) at November 03, 2009 09:57 AM
Article contest: Durova wins 2009 WikiCup
Conference report: WikiSym features research on Wikipedia
Election report: 2009 ArbCom elections report
Audit Subcommittee: Inaugural Audit Subcommittee elections underway
Dispatches: Wikipedia remembers the Wall
News and notes: Strategic planning, November conference, brief news and milestones
Discussion report: Discussion Reports and Miscellaneous Articulations
WikiProject report: Project banner meta-templates
Features and admins: Approved this week
Arbitration report: The Report on Lengthy Litigation
Technology report: Bugs, Repairs, and Internal Operational News
by GerardM (noreply@blogger.com) at November 03, 2009 08:31 AM
I had an action-packed trip to California about a week ago. First was the 2009 Google Summer of Code Mentor Summit, which turned out to essentially be an open-source development conference, sponsored in an extremely generous way by Google. It took place at the Google campus, AKA the “Googleplex”, which I saw a long time ago back when it was the SGI campus, but now looks rather different. What can I say - for all the talk of cutbacks, it looks like Googlers still have it pretty good. The cafeteria food was so good, it made me just want to stay in the cafeteria all day.
The conference itself was quite interesting. I especially liked the talks about the non-development aspects of open source software, like the discussions on
marketing and inter-project communication (I wrote the notes for both of those sessions, which I don’t think is a coincidence because I was interested in those topics to begin with). It was eye-opening to see that every open-source project, even the established ones with foundations and business models and lots of users (all categories that potentially describe both Wikimedia and MediaWiki) struggle with the same issues of gaining “buzz” and coordinating decisions that regular software companies, for better or worse, have professionals handling.
I also got to spend with my brother and his wonderful family. And yes, I did go to this party, which was awesome (it was essentially a party full of people at various software startups, which you would never, ever see in New York); and, separately, I went to this great vegetarian restaurant as well.
After the weekend, it was time to head to the new MediaWiki office in San Francisco, where I met for two days with the members of the Wikipedia Usability Initiative. We had some very interesting and fruitful discussions, all on the subject of the template forms project, which is what I’m involved with. Lots of discussions about naming, which is always trickier than it seems!
In what really is a coincidence, earlier today I released the TemplateInfo extension, which is the first draft of my section of the work for the template-forms project. Hopefully it’ll end up on a gigantic website before too long.
Update: Oops, I forgot to post a link to the photo of all GSoC Mentor Summit attendees. Can you spot me? Hint: I’m in the back row, right next to the tree, in a blue hoodie.
1f63
Our build/design friends from Because We Can over in Oakland have done some great work for us over the past two years – including some nice entry-way desks, tables, and advice on how to make our humble space look nice. They’re also an open company that blazes a trail in using open-source software and providing open-source designs. But recently they finished a particularly special, signature production job for us, our brand new Wikipedia globe sign, now hanging in our offices at 149 New Montgomery in San Francisco.
Jeffrey and Jillian have put together a nice blog post that provides a detailed run-through on how they lovingly crafted the sign using their in-shop CNC robot and meticulous hand-painting. It brings our new space together in an exciting way, and yes – if you walk right up, not only does it glow, but you can help piece together that magnificent globe.

We’ll have more news to share about the Wikipedia puzzle globe in the coming weeks, but for now we’re happy to be able to share the inside scoop on how this lovely sign came together.
Jay Walsh, Communications
If you want to know about the state of the MediaWiki localisation, there are the group statistics. If you want to know how a particular language is doing, there are the language statistics on the Portal for a language. These are the statistics for the Indonesian language.by GerardM (noreply@blogger.com) at November 02, 2009 11:48 AM
John Surratt was a Confederate spy who conspired to kidnap Abraham Lincoln in 1864 and who was suspected of conspiring in Lincoln's assassination. His mother Mary Surratt was hanged by the United States Federal Government for her part in the Lincoln assassination plot. John Surratt survived by fleeing to Europe and serving as a Papal zouave; the statute of limitations on most of his activities had expired before he was identified and extradited.by Lise Broer (noreply@blogger.com) at November 02, 2009 11:02 AM
by Lise Broer (noreply@blogger.com) at November 01, 2009 07:18 PM
Coming after part 1 this post is about what’s been happening in the Wikimedia world that will make us more “GLAM friendly”.
We already know that newbie editors have difficulty in the first place due to being bitten by older editors - as has been described and demonstrated. But, at least as far as editors to Wikipedia coming from the gallery, library, archive and museum sector (GLAM) goes, things are getting a little bit friendlier.
1. Advice for the Cultural Sector a.k.a. [[WP:GLAM]]
With the help of some dedicated editors (special thanks to johnbod, johnuniq and uncledougie) I’ve put together a “one stop shop” advice page for professionals from the GLAM sector coming to Wikipedia wanting to edit.
I do not consider it to be complete or finished but I do think it is now ready enough for a more prime-time audience. Not really an essay, wikiproject, or policy page, it’s more of a place for people to seek advice written in terms that they can (hopefully) relate to. So, whilst the advice written there isn’t unique or qualitatively different from the advice on other pages across Wikipedia, it brings together all of the information relevant to people from the GLAM sector, gives relevant examples, and provides a forum for asking questions to people who are interested in improving GLAM-WIKI relations.
In the future this page may grow. It might gain a “GLAM noticeboard” for actions needing attention or perhaps it might become a place where GLAM representatives can meet Wikimedians who are wiling to be wiki-mentors. We’ll see where it takes us. One good suggestion (by Pharos) was the creation of a GLAM userbox that could be used by professionals as a shorthand to indicate that they understand the rules about declaring a CoI.
Something quite interesting happened when I tweeted that this page was now published with the words:
“Gallery, Library, Archive & Museum folks, please check out http://bit.ly/3k2KoY My attempt to make #Wikipedia a #GLAM-friendly place.”
This was re-tweeted by a series of museum sector people (which is awesome) but the phrasing was changed to this:
“Wikipedia now encouraging…” implies that we weren’t before, which gives me some insight into how unwelcome GLAM professionals felt. I never wrote the words “now encouraging” but I’m pleased that that is how the GLAM sector sees it. On the other hand it worries me that they felt discouraged or not allowed to participate before.
2. Conflict of Interest guidelines update
Similarly, the Conflict of Interest guideline has been updated to include a new section that specifically states:
“Museum curators, librarians, archivists, art historians, heritage interpreters, conservators, documentation managers, subject specialists, and managers of an academic special collection (or similar profession) are encouraged to use their knowledge to help improve Wikipedia.” [This is repeated in the aforementioned advice page]
For the last few weeks there has been a section in the “non controversial edits” heading that referred to “archives, special collections or libraries” being allowed to add links back to their collection in certain circumstance. This has now been removed and replaced with the broader statement that people in aforementioned kinds of professions are specifically encouraged to edit Wikipedia. I had received feedback from the first wording that because the word “museum” was not included that museum professionals thought they had been intentionally excluded. This was not the case and the new wording makes this clear - professionals across the cultural/collections sector are encouraged to edit.
There remains significant concern that this policy will bring forth a flood of linkspam from cultural institutions linking out to everything in their collection. So PLEASE, GLAM-folks, focus on writing content in the articles themselves rather than “go crazy” by merely placing lots of links to your institution’s website. Of course, you can reference your website’s collection as part of your work but if someone looking up your edit history (yes, everyone’s edit history is available for view e.g. Jimmy Wales’) and finds that the only thing a GLAM professional’s account has ever done is link back to the same organisation’s website, that might result in a push for more restrictive wording on the CoI guidelines.
Worse still, there is a worry that pseudo-museums will point to this policy and use wikilawyering to add external links to items of dubious notability:
3. Multimedia usability meeting
Later this week there will be a three-day meeting in Paris to hothouse the issues surrounding the use of multimedia in Wikimedia projects. The specific context is the grant given by the Ford Foundation regarding multimedia usability. The team for this grant is now coming into shape and this meeting will kickstart their efforts. First and foremost the multimedia usability team will be working out better and more efficient ways to upload (and mass-upload) images to Wikimedia commons. But, beyond that there are many other things that they might be able to tackle which are of specific relevance to GLAM organisations. If Flickr Commons has major cultural institutions queuing up to upload their own photographs under a free license then surely Wikimedia can get some of that love too. Unlike Flickr (owned by Yahoo! inc.) Wikimedia has the huge advantages, from the GLAMs point of view, that we have no advertising, are non-profit and can provide excellent contextualisation of their cultural works within Wikipedia.
Recently there has been a flurry of activity in the Gallery, Library, Archive and Museum (GLAM) sector about how they can be more “Wikipedia-friendly” both directly and indirectly. But, what’s been happening in the Wikimedia world to make it more “GLAM-friendly”? Actually, a fair bit.
[This is the sign outside "the Domain", a public park in Sydney, but I would like to think that it applies equally to the Public Domain of creative works. Creative works should be used, not just admired from behind a fence].
But before I get to that (in part 2), here is blogpost part 1. listing just some of the things coming out of the GLAM sector that Wikimedians might be interested in.
1. “Collections are for use, but is Wikipedia the prime outlet?” by Josh Hadro at LibraryJournal.com This article states that:
“Special collections are for use…However, opening up digitized special collections to the broadest possible usage isn’t always easy, according to participants, though others stressed the importance of libraries making their collections’ presence known on popular sites.”
It goes on to explicitly discuss the possibility of working with Wikipedia in linking out to library’s special collection archives.
2. “Five rules for museum content” by Seb Chan from the Powerhouse Museum in Sydney (with whom Wikimedia Australia has worked closely with in the past). These “rules” are that museum content (not limited to object but also the information about those objects) should be:
- Discoverable - it is where I am and where I look for it.
- Meaningful - I can understand it.
- Responsive - to my interests, mood, location.
- Usable/Shareable - I can pass it on.
- Available in three locations - online, onsite and offsite.
Combine these simple rules with the Powerhouse Museum’s funky new strategic plan (2009-2012) which calls for “Dissolve boundaries between exhibitions, programs, publications and web content” and “Increase the level of collection information available through open access…” and you have a museum that is trying to lead the way in being open to Wikipedians using and reusing their content.
3. Similarly, the Smithsonian museum has released its new strategy which calls for the creation of the “Smithsonian commons” (on their own blog) (on the Creative Commons blog) which calls for:
“Establish a pan-Institutional policy for sharing and using the Smithsonian’s digital content, with particular focus on Copyright and Public Domain policies that encourage the appropriate re-use and sharing of Smithsonian resources.”
4. The National Library of Australia is creating a “Copyright Status Calculator” which will AFAICT, automate much of the process of determining the copyright status of works in their collection and they intend on making it open source. Once modified for the local copyright laws/exceptions this could be a boon to the staff in GLAM institutions with the often thankless task of undertaking copyright assessment. This program is simple enough to explain but the devil is in the detail. It combines the metadata for the collection item with a flow-chart logic of copyright law. So long as the metadata is in a consistent format the system could conceivably chew through a large proportion of the collection relatively quickly giving precise information. All edge-cases could then be dealt with manually. Very cool. Currently, every single photograph in their collection contains this standard phrase, irrespective of the copyright status of the photo:
“You may save or print this image for research and study. If you wish to use it for any other purposes, you must complete the Request for permission form.” [See my previous post "the digital rail-gauge" for more extensive rant on this topic]
5. Responses to the “GLAM-WIKI recommendations” are starting to come in. Catherine Styles who was with the National Archives of Australia at the time of the conference has recently published her personal response to the recommendations and they are awesome. They point out that in many cases Wikimedians would love to help and do things, in our own esoteric way, that would otherwise cost the institution considerable time and money e.g. digital restoration and metadata cleanup. A theme running through the response is a desire to see a toolkit or training package developed specifically for the GLAM sector to understand all the interlocking issues being raised. Not simply “how to edit” but also more fundamental things like “why not non-commercial”.
5a. Another response to the GLAM-WIK recommendations that will be published soon (and I’m very excited to have heard this) is that the National Library of Australia has convened a high-level committee to make a formal response. As an organisation that already integrates Wikipedia into many of their services (more than anyone else worldwide as far as I know) they are in a fantastic position to really engage with these recommendations. For example, how many libraries do you know that put the Wikipedia biography of the person in their catalogue search records:
A request was made for the localisation of the Karachay-Balkar language at translatewiki.net. As this was a new language, some technical bits had to be done, and Iltever was given translator rights.by GerardM (noreply@blogger.com) at November 01, 2009 01:43 AM
by Lise Broer (noreply@blogger.com) at October 31, 2009 12:56 PM
by GerardM (noreply@blogger.com) at October 31, 2009 12:16 PM
Earlier today, English Wikinews adopted the usability beta as a default interface. The usability team is thrilled that en.wikinews community has reached the consensus to be the first adopter of the usability beta as default. We will continue enhancing the interface to simplify and make it easy to navigate and edit. Our sincere appreciation goes to the entire en.wikinews community for embracing our work. It is a great day for the usability team. We feel blessed.
Naoko Komura on behalf of the entire usability team
Program Manager, Usability Initiative
Today is a great day. Today is the day when we say hello to custom covers for PediaPress books. Today is also a sad day, because we say goodbye to our old but beloved orange and blue covers. We've loved them, we've hated them, well, they have been part of our story, they have been the face of PediaPress for the past two years. We'll miss them, but we felt that we needed to give you the opportunity to make covers that really would adapt to the books you were making. After all, custom books should feature a custom cover, right?
What is a custom cover?
Well, it's very simple really, instead of having a set cover for your book, you have now the possibility to compose the cover that suits your book's content, your mood, or the occasion.
Once you've collected your book, on Wikipedia for example, and you've clicked the button "Order as a printed book", you'll be taken to the PediaPress Website and will land on the custom cover manager.
The first step is to choose the color of the background you want for your book. You can try out a few color schemes.
Once you've chosen your background color, you can add a picture to your cover. At this stage, you have the possibility of adding pictures present in the articles that compose your book. The pictures will display in a row under your cover, and you can scroll right and left to choose the picture you want. The cover manager only displays pictures that are of a high enough quality to look good on your cover (excluding very small pictures or pictures of low resolution). Of course, we want your book to look as good as possible.
And that's it, once you've decided that the cover and the pictures were the right one, all you have to do is order, and you will receive your book just as you've designed it. Take a look at the books we've already made!
Have fun exploring the possibilities of the new custom cover manager! And as always, don't hesitate to give us feedback on this new feature by clicking the feedback button on the right of our website or by commenting this blogpost!
by Delphine (noreply@blogger.com) at October 30, 2009 06:01 PM
by GerardM (noreply@blogger.com) at October 30, 2009 03:06 PM
by GerardM (noreply@blogger.com) at October 30, 2009 01:58 PM
by Lise Broer (noreply@blogger.com) at October 30, 2009 01:50 PM
Every edit on the wiki, every revision, and every comment stays… forever. There is nothing one can do to hide it, save few exceptions. There are always tracks.

Footprints
Take for example this arbitration case… five years later it remains.
Instead or creating history… one could consider sitting down with fellow contributions.
For Wikipedia, or any other wiki is in the real world. Bosses, friends, colleagues, and other interested parties may be watching as well.
Happy editing!