Showing posts with label Wikimedia Labs. Show all posts
Showing posts with label Wikimedia Labs. Show all posts

Monday, June 12, 2017

#Causegraph, an other way of looking at #Wikidata


Causegraph is a tool to visualize and analyze cause/influence relationships using Wikidata. If you have not seen it yet, give it a spin.

Randomly looking at the galaxy of relations, I found a Charles Frédéric Bassenge, he is in Wikidata because he is the father of Pauline Runge. He is in Wikidata because she has an entry in WikiTree. What amazes me most is the quality of the data for the father and his absence in WikiTree. 

Causegraph works on the basis of there being a direct relation between two persons. For Jacob Palis, the doctoral students and doctoral advisers are included and not the other TWAS award winners.

What is really good is that it is regularly updated. It would be even better when it was a Labs tool. This might enable real time updates .. <grin> there is always a wish for more and better </grin>
Thanks,
       GerardM

Thursday, March 03, 2016

#Wikidata - to share the sum of all data

The BBC featured an article about all the battles of the world in space and time. The cool thing is that the people from Nodegoat used data from Wikidata and DBpedia and consequently the article is not about Wikidata but about what you can do with its data.

Nodegoat enables people to bring data together and visualise it in a way so that people can comprehend it. The BBC article describes the "Geography of Violence map"; it includes data about all known battles ever that include place and time information. Most of the data is from DBpedia and some of it is from Wikidata.

There are two issues to consider;
  • Nodegoat available for everyone 
  • curating data from DBpedia and Wikidata
When Nodegoat is available at Wikimedia Labs, it will enable people to come up with new ideas, presenting data that is otherwise obscure. They will find that much data is missing or wrong and at Wikidata they can improve the data as they see fit. Lab1100 is considering what license for Nodegoat and when we would make Nodegoat available at Labs, it would give them a firm push towards a free license.

DBpedia is a real strong project; it has gleaned a lot of data from Wikipedia and its quality is high. When there is an error in the data you can only change it in Wikipedia and wait for DBpedia to update. With Wikidata you can update the data itself. The data that is included was largely retrieved with similar routines used by DBpedia so it actually makes sense to collaborate with DBpedia and have them update Wikidata as well.

When the sum of all data is available to all and when many tools are available to leverage the data, more people will have incentives to improve the underlying data. Sharing the sum of all data and providing tools that make a difference is the best way to fulfill our mission.
Thanks,
        GerardM

Sunday, October 25, 2015

#Wikidata - #Blazegraph does it matter?

In an argument that is hardly of relevance for all of us, issues about Wikidata centre around a tool called blazegraph. The tool is server based and as we do not all have a spare server to run a tool like this what does it take to make this relevant?

When issues with a tool have an impact on Wikidata, it is hardly a problem for the rest of us. When people make points like this they are in "insularly thinking mode", it is self centred on them and their ivory tower peers.

This mode of thinking can also be found in their tools that puts them in places where mere mortals do not venture. When asked, Wikimedia Labs is maybe for later. At issue is that integration of such tools for the rest of us is not considered. Labs is exactly there to have all the tools and share result and integrate for better results.

When tools like Blazegraph are only available in proprietary settings, arguments about this kind of proprietary use should be irrelevant. This does not need to be. All it takes is the installation of Blazegraph in a Wikimedia Labs setting for the "rest" of us.
Thanks,
      GerardM



Friday, March 06, 2015

#Kiwix - getting #Labs ready for the #Wikipedia big time

Offline #Wikipedia received a big boost. It is updating monthly its images for most of the #Wikimedia projects. Most but not all. Emmanuel was asked to write up about his challenges and I am happy to share this with his permission. Developments like this make both Labs and Kiwix even more strategic to out goals.
Thanks,
       GerardM

Following Yuvi's and Andrew's invitation, I write this email to explain what I want to do with Labs and share with you my first experiences. 
== Context == 
Most of the people still don't have a free and cheap broadband access to fully enjoy reading Wikimedia web sites. With Kiwix and openZIM, a WikimediaCH program, we have been working on solutions for almost ten years to bring Wikimedia content "offline".
We have built a multi-platform reader and have created ZIM, a file format to store web site snapshots. As a result, Kiwix is currently the most successful solution to access Wikipedia offline. 
== Problem == 
However, one of the weak point of the project is that we still don't achieve to generate often enough new fresh snapshots (ZIM files). Generating ZIM snapshots periodically (we want to provide a new fresh version each month) of +800 projects needs pretty much hardware resources.
This might look like a detail but it's not. The lack of up-to-date snapshots brakes many action within our movement to advert more broadly our offer. As a consequence, too few people are aware about it reported last Wikimedia readership update. An other side effect is that every few months, volunteer developers get the idea to build a new offline reader based on the XML dumps (the only up2date snapshots we provide for now), which is near to be a dead-end approach. 
== Goal == 
Our goal with Labs  is to have a sustainable and efficient solution to build, one time a month, new ZIM files for all our projects (for each project, one with thumbnails and one without). This is at the same time a requirement for and a part of a broader initiative which has for purpose to increase the awareness about our "offline offer". Other tasks are for example, storing all the ZIM files on Wikimedia servers (we currently only store part of them on download.wikimedia.org) and improve their accessibility by making them more visible (WPAR has for example customised their sidebar to provide a direct access 
== Needs == 
Building a ZIM file from a MediaWiki is done using a tool called mwoffliner which is a scraper based on both Parsoid & MediaWiki APIs. mwoffliner, after scraping and rewriting content, store them in a directory. At the end, the content is then self-sufficient (without online dependencies) and can be then packed in one step in a ZIM file (using a tool called zimwriterfs).
To run this software you better have:
  • A little bit bandwidth
  • Low network latency (lots of HTTP requests)
  • Fast storage
  • Pretty much storage (~100GB per million article)
  • Many cores for compression (ZIM, ZIP and picture optimisation)
  • Time (~400.000 articles can be dumped per day on a machine)
My guess is that we need a total of around a dozen of VMs and 1.5 TB of storage. 
== Current achievements == 
We have currently 3 x-large VMs in our "MWoffliner" project:
With them we are able to provide, one time a month, ZIM for all instances of Wikivoyage, Wikinews, Wikiquote, Wikiversity, Wikibooks, Wikispecies, Wikisource, Wiktionary and a few minors Wikipedias.
Here are a few feedbacks about our first months with Labs:
  • Labs is a great tool, it's fully in the Wikimedia spirit and it works.
  • Support on IRC is efficient and friendly
  • We faced a little bit instability in December but instances seem to be stable now
  • The Documentation on wikitech wiki seems to be pretty complete, but the overall presentation is to my opinion too chaotic and stepping-in is might be easier with a more user-friendly presentation.
  • Mediawiki Sementic & OpenStackManager sync/cache/cookie problems are a little bit annoying
  • Overall VM performance looks good although suffering from sporadic instabilities (bandwidth not available, all the processes stuck in "kernel time", slow storage).
In general, Labs does the job, we are satisfied and think this is an adapted solution to our project. 
== Next steps == 
We want to complete our effort and mirror the biggest Wikipedia projects. Unfortunately, we have reached the limits of a traditional usage of Labs. We need more quota and we need to experiment with the NFS storage because an x-large instance in not able to mirror more than 1.5 millions of articles at a time. How might that be made possible?

Sunday, March 01, 2015

#Hackathon - the #genealogy of Catharina-Amalia, Princess of Orange

Visualising the genealogy of person can be extremely interesting. The tool that was the best we had exists in Reasonator and for the Dutch Royal family it did not really work. Too many people are involved.

The approach of a new tool developed at the hackathon in Bern is really interesting. It limits itself to five generations and it shows pictures of the people. It is nice to see princess Catharina-Amalia.

It is also great to notice that you can have the same information in for instance Chinese or Russian. When you click on one of the persons in the genealogy, it will produce the genealogy for that person..

At this time the new tool is very much in development. It is great to show why hackathons are so relevant.
Thanks,
     GerardM

Thursday, February 26, 2015

#Wikimedia #Labs - Risc analysis

Labs is a wonderful and successful project; more virtual machines are added all the time. More data is produced all the time and more people rely on it all the time.

Sounds good? It is!

From a management point of view it becomes increasingly problematic because for many of the most valuable Wikimedians it became a production resource and, as Labs is growing really quickly, it easily escapes the boundaries set earlier. Staffing, hardware it could all be better and it should all be better.

Having the best possible Labs will grow Labs even more. The best will outwit and outperform expectations. Classical budget think is a disservice to what we may achieve: share more information as widely as possible. One approach is to maintain a risc analysis of the services provided by Labs. It will help management to manage, to think and to use funds when the need and the justification is bigger than the budget

Today new virtual machines have been started that are starting to produce ZIM files based on the latest dumps. This will improve off-line reading of our projects a lot. The ZIM files will in future be and remain fresh..

This is just one day in the life of Labs...
Thanks,
      GerardM

Tuesday, February 24, 2015

#Wikidata - #Alumni by university or college in #India

As one of the most populous countries in the world, it is no surprise that India has many universities. The alumni of Indian universities or colleges can be found through a Wikipedia category.

Whenever tools are down I have been adding these alumni to Wikidata. It seems obvious that not all universities and colleges are represented. It is certain that many alumni cannot be found in these categories. This is because there may be no article about them or they have not been included in the category.

It is relatively easy to do this for India given that English is the main language for subjects about India. For China, Russia and Japan it is not so easy. Someone else has to get involved as I do not know the languages.

All of Labs is down again. So this time my customary hyperlinks are sadly absent..
Thanks,
      GerardM

Friday, November 28, 2014

#Wikimedia #Labs - my #stake is rare, bruised

I have a stake in Wikimedia Labs. I rely on it. I am not the only one. Wikimedia chapters rely on it; they need it for many of their activities. Glam is one area vital to them that relies on Labs.

For the Wikimedia Foundation, Labs is second tier. They have a few people dedicated to Labs. Good people, well intentioned people but what they offer is not production quality. They cannot for several reasons. There are not enough resources for them to do what is needed.

Chapters are second class citizens as well, The fact that Labs is vital to achieve their aims so far did not make a noticeable difference. In my opinion it is not only the Wikimedia Foundation who can and should make a difference. It is the chapters themselves as well.

I urge the chapters to invest in Wikimedia Labs.. It is BOTH the responsibility of the WMF and the chapters to provide adequate support. During business hours operational support should be available. Stakeholders in both WMF projects and chapter projects rely on adequate service.

Today is black friday in the USA. Yesterday was Thanksgiving. When all staff celebrate their turkey we are left to fend with even less.
Thanks,
       GerardM

Monday, October 20, 2014

#Google - Let us #share in the sum of all #knowledge

Dear Google, in our own ways, we share the aspiration to share in the sum of all knowledge. We are really happy to share everything we have with you. Our licenses are designed to share widely.

Dear Google, could you please help us make sure that our Labs webservices survive your bots? What we do not want is for your bots not to run. What we want is for our webservers to serve our own needs first and use all the spare capacity for you. As it is our software dies.

We really want you to have our data and, there are several other ways whereby you can get all out data any way. For this reason please help us with our software so that we can continue to share the sum of all our available knowledge with you.
Thanks,
     GerardM

Tuesday, September 23, 2014

#Wikimedia #Labs - when is enough enough

Wikimedia Labs is a success. It is used a lot. It is increasingly stable. It grows quite quickly and, it has its own staff who are knowledgeable and happy to work with anyone and help where needed.

It is a great project that increasingly provides important and useful services to Wikimedia projects. Some services stand on their own to the benefit of the wider open source and content world.

It is a happy story where growth is limited by the availability of hardware and support. With more hardware, with support available around the clock, the sky is the limit.

Unbounded success is great but it will on occasion overtake the projects it supports. As the demands on the projects grow, the infrastructure changes. Great best effort prevents most mishaps from happening but occasionally services do become unavailable. That is not a drama, it is the way of things.

Lately there was another snafu; it partially affected the work that I do. I noticed that the issue was actively taken care off. I send a mail to Magnus about it. In the end the issue was resolved and the services I use are back in full swing. It took a few days, there was no drama. That is success.
Thanks,
     GerardM

Friday, July 25, 2014

#Wikidata #statistics - waiting for storage

With the Games being really popular and with the mass additions of statements using AutoList2, you would expect that it shows in the stats for Wikidata.

It does not. There is a problem. Labs ran out of storage. New hardware was ordered and with a bit of luck, the three shelves of new storage will provide ample space for the foreseeable future.. There is a truism that has it that discs will fill up in half the expected time..

Yesterday they were initialising the hard drives and next will be moving and copying the data to its new location. With a bit of luck the software that generates the statistics will find it and, we will have something to ponder again.
Thanks,
     GerardM

Saturday, May 24, 2014

#Wikimedia-#Labs its script kiddies and its public

Labs is the home of many tools. These tools are often essential to workflows or they show people information that they cannot get in any other way. When you want to work on people who died in 2014, you use this script. When you want to have information about 土门岭村, a village in China, you use Reasonator.

Labs has three types of public; there are the heroes who develop tools, there are the people who use these tools to generate more data and there are the consumers of all the information that becomes available.

They all have one thing in common. For them to function Labs has to be operational.

When Labs is not always available, when the quality of service suffers, the tools will not get the exposure they seek. Script kiddies will not generate more data and the public will not share in the information that should be available to them.
Thanks,
     GerardM

Thursday, March 06, 2014

#Wikidata - the building of the Nationalbank in #Bern


The building of the Nationalbank in Bern is a monument. It does not have a Wikipedia article and yet, it is known to Wikidata.. When you check out the external source, you find that the source is running on the Toolserver. This probably means that this tool needs to be migrated to labs in the near future.

The database is on the Toolserver probably because of Wiki loves monuments. When you look at the data, you find that among other things it refers to a list on the German Wikipedia. You will also find that much of the data can be included in Wikidata. When all the data is hosted on Wikidata, it is not even necessary to migrate the data to labs.

When monuments like this building have their data on Wikidata, it will make it easier to integrate Commons in Wikidata. As you may know, this is scheduled for the second half of 2014.
Thanks,
      GerardM

Wednesday, March 05, 2014

#Wikidata - the seventeen townships of Boone county #Iowa


There are multiple Boone counties and this is about Boone county in Iowa. Recently there were some issues with the reliability of the data used by Reasonator. Data was missing; it did not show. For several days we have been getting the data right that should show in the "Category:Townships in Boone County, Iowa". Seventeen townships should show up. Initially none showed up.

Now several days later, the migration of Wikimedia labs has happened. The dump of Wikidata finished but it did not find its way to where it was expected to be, the IP address for the proxy for the changes to Wikidata had changed, the incremental backups of Wikidata have been suspended during the move and, life goes on regardless.

The big thing in all this is the migration of Wikimedia labs. It is under way it has been well prepared and a lot of TLC is given by Coren and the other labs staff to the people who want their tools migrated. They are doing an impressive job. The incremental backups are one of those jobs that were created on the fly and gained unexpected relevance. At some point in time they will be running again at their new home.

Some of the missing townships did not even show when everything was supposed to be good. Further analysis indicated that they have to be both a township and be in Boone County, Iowa. Now that they are and do, they show up all right.
Thanks,
      GerardM

Wednesday, December 25, 2013

Reasons to be cheerful

#Wikimedia #Labs had its issues lately. There were problems with file systems, with tools that failed. There was not much that could be done about it.

The good news is that Labs does get attention. Support is given on IRC and the feeling I got was that there was a gentle progression from the big issues to the smaller ones.

Widar was not working for me. As things had become quit, there was room to look at the code. There was an easy way to make it more efficient, to make the code perform better.

Such attention is a gift. It helps me and other users of the tool. Such service is a reason to be cheerful, to be grateful. It also makes labs a pleasant environment.
Thanks,
      GerardM

Thursday, December 05, 2013

The Tech #Barnstar

Yesterday, the #Wikimedia #labs had a problem; it was being hammered by what looked like a DDOS attack. It proved that the script that provided the Wikidata search functionality needed to be optimised more than a bit.

The software was killed but soon after that a modified version went life. Definitely a reason to be cheerful, also a moment to be grateful. I would like to present this Tech Barnstar to

  • Magnus for writing the original software
  • The Ops / Labs team for having to deal with a nasty situation
  • Legoktm for modifying the software that has the approval of the Ops team
Thanks,
      GerardM

Wednesday, October 30, 2013

Magnus, master of #Wikimedia #tools

When Magnus agreed to answer some questions, I wanted his answers to have impact. So I asked a few influential people what they would ask Magnus. I am happy both with the questions and the answers; they offer us plenty opportunities for making more of an impact.
Thanks,
      GerardM

Lydia: what's his next cool hack
Technically, since the moment I received these questions, it would be AutoLists. 
I haven't decided what to do after this. There is the prospect of extending/rewriting the Free Image Search Tool to use Wikidata, and to suggest images for Wikidata from the various Wikimedia projects in return. 
Also, with the long-term plans to use Wikidata, or at least its software, to finally get a grip on metadata for files on Commons, it might be interesting to create and seed a database for the "obvious cases", which could then in turn seed "Wikidata Commons", when it finally shows up.
Lydia: and what he'd like to do but doesn't get to (so others can do it)
A million things! Many of my tools could do with some fixing, code review, extension, you name it. If you can code, have a look at the existing tools and maybe sign up for a tool or two which you would like to improve (not just mine, of course!). 
I still have to port tools from the toolserver. Have a look here at tools to port and, help me prioritise! 
Another thing I had started back on the toolserver was a "tool pipeline", where you could chain up tools so that the output of one tool is the input of the next. This could be quite powerful, especially for less tech-savy users who can't write their own glue code, even if the concept sounds uncomfortably like the human centipede ;-) Have a look at my attempt back in 2012.
Brion: What's the awesomest tool you've created that people don't (yet?) know about?
That's a hard one, as I carefully and thoroughly spam the community for every new tool I create ;-) 
One that is probably less known, and that I use myself on Wikipedia, is a special CSS for wide screens, where it shows the Wikipedia main text in a central column, and arranges TOC, infoboxes, thumbnails, and small tables on the left or right. Screenshot & CSS

As for actual running code, less known but with huge potential IMHO, are live category intersects on Wikipedia. Together with [[User:Obiwankenobi]], we came up With this: Screenshot JS
Brion: What's the best way to make things happen? (getting cool projects done, even if nobody else is working on them yet
Have something to show people. Even if it's little more than a mock-up. Even if it's full of bugs, slow, ugly, fails half the time, and does only 1% of what it should do. A single thing that people can see and click on can get people to the cause, where a hundred pages of text will not. Stallman's GNUpedia existed on a mailing list with many a fancy idea; Wikipedia was there to see, to "touch", to edit. Even if it was a single, bare Perl script.
Alolita: what are your recommendations are for the next 5 innovative tools WMF needs to fund to build for Wikimedia websites
Not sure about funding for tools; coding projects big enough to fund should probably be designed as Wiki(m|p)edia-default extensions, or even MediaWiki core. In terms of new functionality prioritised in-house beyond the current scope, these would be the most interesting ones for me:
  • OSM integration. This has been on the WMF back burner for years.
  • Commons file metadata as Wikidata. On Wikidata itself, or added to Commons itself.
  • More data for Tools Labs. View data so that we can support GLAM projects; there has been some talk about this lately, but it has been a few weeks away for years now. Also, faster access to the wikitext than through the API/dumps would be useful.
  • Add Wikispecies to Wikidata. It might revive Wikispecies (which seems sadly underused), or at least rescue much of its information onto Wikidata.
  • One old pet idea of mine: Wikimedia (bi-)weekly magazine. Consider an amalgamate of Wikinews (which, let's face it, has pretty much failed as a daily source of news), Wikipedia "did you know"-type interesting articles, interesting places from Wikivoyage (which appears to be booming), fascinating images from Commons, an excerpt from Wikibooks, a short story from Wikisource, you get the idea. An editorial text, or political comment (relevant to the Wikimedia world; think CISPA), from individuals might not be too far fetched an idea. An issue would be generated in the usual fashion, maybe with an editor-in-chief (rotating? elected every three months?) to address the time-critical nature of the project. A completed issue would then be generated in several formats; on-wiki, PDF, etc. Maybe even go through proprietary distribution channels like Amazon or Apple, if the license situation allows it. I am sure tablet users would flock to it, and we might get some of these "consumers" to participate in one of the Wikimedia projects, maybe with "photos by readers" as an entry-level drug :-)
Alolita: How WMF can help support the development community better * process recommendations * policy recommendations * participation in helping grow more developer contributors
I'll answer these as one question. For tool developers, Labs is already a fine solution. There are a few rough edges which could be smoothed, though; "find someone on IRC" is often the way things are done, which is not always the best. There were a few outages recently, which can happen, and it took hours for someone to have a look a the issue, which is not exactly a life-or-death situation, but still frustrating for tool authors, and not just because of "your tool is broken" messages piling up around them. I understand that only core systems can have someone on standby 24/7, but maybe Labs issues could bubble up the chain automatically if no one from the usual Labs crew is around. 
Getting more people to make use of the great Labs facilities is important. Part of that could be a simple visibility issue: if more people knew that Labs offers not only CPU and storage, but live mirrors of the Wikimedia databases, or that they could easily help fixing or improving that vital tool, we would probably see more widespread adoption of Labs by programmers. Labs-based git repositories for each tool could also enhance visibility, and improve code reuse (which I practice heavily within my own tools). 
In terms of adoption of tools and extensions by volunteer developers into Wikimedia wikis, MediaWiki core itself, or as stand-alone systems, clear and time-limited review procedures would be required, as well as assistance by Wikimedia developers to get code up to MediaWiki standards. On the other end, a public listing with project ideas that, if implemented, would be considered for adoption by Wikimedia, could focus volunteer programmer participation. I am talking about a simple list of "we would like to have these, but don't have the manpower" issues, written by Wikimedia staff, as opposed to obscure feature requests in bugzilla that might be long obsolete.
Open source is also to work together on software, tools. Your tools are available, how do we get more people to cooperate on them
By refusing to fix bugs, we could force the bug submitter to do it ;-) 
On a more serious note, I think improving visibility, as mentioned above, of the great things Labs offers, and that participation on existing tools is encouraged and welcome. Just like many people use Wikipedia but still are not aware that they could edit it themselves, potential volunteer programmers might think that these tools are done by Wikimedia staff, or some carefully chosen group, rather than by run-of-the-mill geeks like them.
When you had someone to work on improving ONE tool; what would you want him or her to do?
Extend Wiri a.k.a. "the talk page". It is not so much a normal, "useful" tool, but a nice technology demo, not just for Wikidata, but for a confluence of technologies (data from Wikidata, speech generation from third-party open source, speech recognition from Google) enables functionality that plays in the same ballpark as big commercial solutions like Siri or Google Now. 
I am well aware it will never be en par with the Mathematica/Wolfram Alpha backend in terms of calculation power, or up-to-the-minute sports results. But even simple improvements, like a listing of options if the (speech) input is ambiguous (e.g. several people with the same name), translating complex questions into Wikidata query requests, displaying images, maps, or using AutoLists to show multiple results, could turn it from a mere demo into an actually useful tool. With proper, fault-tolerant grammar parsing, real reasoning, and the ability to explain the reasoning, it could be amazing!

Thursday, April 25, 2013

#OmegaWiki works and so can #Wikidata

OmegaWiki provides functionality that is on the agenda for Wikidata. The OmegaWiki community has ALWAYS wanted to be a Wikimedia project.

What it already provides is:
  • links to Wikipedia articles in other languages when the article does NOT exist in the preferred language
  • links to a commons category associated with a concept
  • a picture painting the thousand words associated with the concept
Yes, it is quite shocking; it also provides multi lingual dictionary support. OmegaWiki has even been described in a book on the development of lexicography.

Both OmegaWiki and Wikidata are "right in front of us" and, the functionality described above is imho "right for us". The challenge we face is to do something that is "shockingly rare"; meet halfway.

The road towards such a meeting could be:
  • Adopt OmegaWiki by the WMF in a labs kinda construction
  • Create the logical requirements of OmegaWiki data in Wikidata
  • Convert the OmegaWiki content to Wikidata technology
  • See how it fits in the big picture
  • Make it fit in the big picture
We do not need much talk and, the amount of work needed is relatively minor. The benefits are legion because even when all the OmegaWiki data is not used in the end, the lessons learned will be.
Thanks,
      GerardM

Saturday, March 23, 2013

#ASL; the most challenging language at #Translatewiki

A #Wikipedia in "our" language is what people are working towards in the incubator. There are many challenges that need to be taken before this dream is fulfilled. Messages need to be localised, articles need to be written and finally the text has to be proven to be in "my" language. Several challenges that take time and effort, all for the big moment when one more Wikipedia is created.

They are challenges but they are dwarfed by the challenges facing the people working towards a Wikipedia in American Sign Language. First of all, their effort cannot be part of the incubator. Their incubator project is in a Wikimedia Labs environment. An environment with experimental software that allows them to write their own language.

The SignWriting script is written from top to bottom as you can see in the screenshot. This is not supported by MediaWiki. The SignWriting script is not yet part of Unicode. MediaWiki only supports scripts that are encoded in Unicode.


Consider what it does to localising the software at translatewiki.net. Below you find what Wednesday looks like for Adam, who is working on the localisation of the most used messages. It must be copying data from one environment to the next, not even knowing what the effect will be when it finally shows in the labs environment.


If anything I know how much hard work goes into new projects. The effort for the Wikipedia in American Sign Language is probably the most complicated of them all.
Thanks,
        GerardM