Posts Tagged Wikipedia

Presentations from Wikimania and More

Many folks do not know, but we actually try to upload and make available all our presentations.  Presently, you can see a list of them on our Wikitech wiki.  You can follow this link to see them all.

Keep checking back, because the conference isn’t finished!!

, , ,

1 Comment

Improving Wikimedia’s Discussion System

Hi all,

Some of you might have already seen my blog posts about LiquidThreads, Wikimedia’s in-development discussion system.

For those who haven’t, this is a quick primer on what LiquidThreads is, and what it’s going to do for Wikimedia’s communities.

Currently, Wikimedia’s discussion system sucks. Here’s why:

  • It’s not easily usable by the average user. It isn’t obvious how to leave a comment on a talk page, or how to reply to a comment. The indenting we use now is ad-hoc and unsustainable for long discussions.
  • Signatures are done manually and we have to jump on poor unsuspecting newbies who don’t know this (or write bots…)
  • Archiving is done unevenly by bots, which are maintained by users and therefore of very uneven quality. Archives are something of a black hole — they aren’t searchable, easily maintainable or easily accessible. You can’t resurrect an archived discussion easily, nor can you view its history.
  • It’s stored as plain wikitext, which is opaque to any sort of automated process.
  • You can’t move a thread to a different discussion page and preserve its history.
  • There’s no encouragement, mechanism or incentive for quoted, point by point inline replies like we’re all used to with e-mail.
Imagine being a new user and trying to figure out how to add your comment to this.

Imagine being a new user and trying to figure out how to add your comment to this.

Enter LiquidThreads. LiquidThreads is a system that makes MediaWiki’s discussion system behave like a forum or comments thread, while still maintaining the unique refinements that make wikis work. It was originally designed by a Google Summer of Code student, David McCabe, and I’ve been making incremental improvements to make it work for Wikimedia.

Overview of the new LiquidThreads interface

Overview of the new LiquidThreads interface

So, what’s changed?

  • Comments are separated from each other in the wikitext, so there are no more edit conflicts in discussions, and the usability is vastly improved.
  • Instead of indenting, each comment is in its own box, along with its replies. It makes it much easier to follow each post and its replies, and it’s much nicer on the horizontal whitespace. Hopefully, it will be the death of the ‘arbitrary section break’!
  • Each post has its own history page, making it easy to see what’s going on with individual threads without trying to navigate the history of a whole page.
  • It’s easy to move threads between pages, preserving the page history.
  • Discussions  are never ‘archived’. Instead, older discussions fall to the bottom of the page, and eventually they drop off entirely, to hit a new page. If you missed the chance to have your say, just reply to a discussion and it’ll be bumped right up to the top of the page again!
  • Discussions with recent changes are at the top of the page. Discussions that have fallen dormant fall to the bottom. It’s easy to find out what’s happening!
  • You can watch individual threads of a discussion, and even get an email when they’re replied to.
  • It’s easy to link to a discussion, and the links are permanent unless the discussion is deleted. There’s no need to point to an archive or to an old revision ID.

If you’re interested, I’ve put together a test setup for you to play with it.

As always, questions, comments and suggestions are more than welcome, in the comments or elsewhere.

, , ,

8 Comments

First usability release, Acai, is now available.

Screenshot-Editing July 1 Wikipedia

The first usability release, Acai, hit Wikipedia and sister projects this afternoon. The new skin, Vector, and the enhanced toolbar can be turned on from the user preference under “Appearance” and “Editing”. Search result page now has a new layout with less daunting information. Vector is only available for left-to-right languages at a moment due to IE6 incompatibility. However, the enhanced toolbar can be selected from all languages and the new search result page is enabled globally. We could not roll out two features we had planned. First, warning messages for unsaved changes when a user switches away from the edit tab did not work properly thus they are disabled. So please be careful when you switch away from the edit tab. Secondly importing language specific configuration for special characters were not graceful, so we disabled special character function from the toolbar. We are working on the fixes and plan to roll them out as soon as we have stable solutions. The usability project wiki has Vector and the new toolbar as a default, so if you prefer to check them out without changing your preferences it is a good place to visit first. Let us know what you think. We would love to hear from you.

Best,

Naoko

, ,

No Comments

First usability release is coming up soon.

Screenshot of enhanced toolbar

Screenshot of enhanced toolbar

I am happy to announce that the first set of usability improvements is scheduled to be integrated in MediaWiki and will be enabled as one of user preferences in Wikipedia in the first week of July. The nickname for this release is called Acai. The release names will follow the names of tropical fruits in alphabetical order. The description of features are found in this release page. The major improvements are; 1) reorganized tabs which clearly indicates the state of “Read” and “Edit”, 2) enhanced edit toolbar which is expandable based on users’ needs, 3) search result page which hides the clutter and make search results more visible, and etc. We are still combating with IE6 bugs , but come and play with the prototypes and let us know your feedback. On the localization front, we have introduced a set of new texts for localization. If you are a MediaWiki translator, your collaboration on localization is greatly appreciated as always.

Naoko Komura

Wikipedia Usability Initiative

, ,

3 Comments

The Wikipedia Usability Initiative is still hiring.

The Wikipedia Usability Initiative has extended the application deadline for the Software Developer position till May 30th. We are recruiting two candidates for this position. Both local applicants to the San Francisco Bay Area and remote applicants are encouraged to apply. Please help spread the word.

http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(project)

Naoko Komura
Wikipedia Usability Initiative

, ,

No Comments

OpenStreetMap maps will be added to Wikimedia projects

There has been rapid progress on the subject of adding OpenStreetMap maps to Wikimedia projects (e.g. Wikipedia) during the MediaWiki Developer Meet-Up taking place right now in Berlin.

We now have a clear plan of action for getting OpenStreetMap maps embedded in Wikimedia wiki (e.g. Wikipedia) pages:

  • Wikimedia will set up a database to mirror the OSM data (Planet.osm)
  • Wikimedia will set up its own rendering infrastructure for rendering tiles & other maps from the OSM data
  • The existing MediaWiki extensions for displaying OSM data in a MediaWiki article will be improved to work acceptably in production on Wikimedia servers

To prototype all this we’ll be using new infrastructure provided by Wikimedia Deutschland. Once things have been tested there they’ll eventually be deployed on the main Wikimedia sites.

After discussion with the Wikimedia operations people (including Brion Vibber, Mark Bergsma et al) there seem to be no objections to the above plan as long as:

  • The maps will work not only for JavaScript enabled browsers but also non-JavaScript enabled ones
  • The tools involved are improved to be relatively stable & deployable on Wikimedia, e.g. being able to embed more than one slippy map, the internationalization of error messages etc.
  • The end product (the generated tiles or map files) are cachable so that they can be thrown at the frontend squids, as they’re static images this should be easy.

The featureset that we’re aiming for to be able to deploy this on Wikimedia sites from the view of the user (more can be added later once we’ve got it working) is:

  • The ability to embed OSM maps in articles with something like the Simple image extension, perhaps automagically turning into a Slippy Map if the browser supports it
  • A static or slippy map that can be used by geotagged articles so we can have maps without explicit inclusion of a <map> tag.

We’ll also set up a map toolserver for experimenting with other uses of OpenStreetMap data on Wikimedia. People with relevant projects can get access to this toolserver to try out their ideas for tools that could eventually be integrated on the main Wikimedia sites.

This project is seeking help from anyone who’s interested who’d like to be a part of making this happen, if you want to be a part of adding free maps to the world’s largest encyclopedia please subscribe to this mailing list:

And/or read/edit/comment on the relevant wiki coordination pages:

,

2 Comments