Showing posts with label language committee. Show all posts
Showing posts with label language committee. Show all posts

Sunday, February 12, 2017

#Wikimedia language committee and #trust

The Wikimedia language committee was originally created to stem the flow of new projects that just did not work. At the end of a lengthy process a specialist is sought to certify that the language used is indeed the language a new Wikipedia is about.

Rehmat Aziz Chitrali is such a specialist for the Khowar language. When you read one of the Wikipedia articles about him, there are seventeen articles, it is obvious that he is more than qualified for the task.

With so many articles, it is obvious that awards he received may have well been documented in some but not in other languages. For Wikidata several but not all awards were added to do some justice.

When the news is in that the Khowar incubator is indeed in Khowar, we will soon have a new Wikipedia.
Thanks,
      GerardM

Wednesday, April 30, 2014

#Wikidata - #Marwari, a language from #India


Thanks to new #MediaWiki functionality, Wikidata can support languages that are not available elsewhere. It is a consequence of a change in the policy of Wikimedia's language committee. For languages that are "eligible", that is in essence that they are recognised in the ISO 639-3, people can ask for recognition of their eligibility.

The way it works is that you can add the language to your Babel template. This will make sure that labels will show in Wikidata. You can also change your user preference to rwr or Marwari and, it will be the default that shows the labels in all statements.

Reasonator is however the easiest way to work on Marwari. It will show labels in Marwari but it shows labels in the specified fall-back languages. This makes it convenient to add missing labels. One prerequisite however is that Widar has been set up properly.
Thanks,
      GerardM

Saturday, January 18, 2014

What #Wikidata has to offer to languages in the #Incubator

One of the objectives of Wikidata is to provide "information box support". These info-boxes use information from Wikidata on articles that are linked to it. The information is shown in the local language. For Incubator, things are .. complex. For starters, incubator is a multiple language wiki. To make it worse, Incubator includes some languages that will never have a Wikipedia.

Wikidata is more inclusive in its support for languages than any of the other projects. It can support extinct languages, it can support constructed languages, it can support multiple scripts for the same language and, the requirements are minimal. What is required is that the language is recognised in the ISO-639-3 and that a script is actually in use or has been used.

Let us consider the Maithili language. There is an incubator project for this language for a Wikipedia and for a Wikibooks. It can be used in Wikidata. Currently there is one label for one item. When all the labels used on relevant items like "India", "Gandhi", "Delhi", "horse" and "rabbit" have been added, millions of items will show at least a few labels in Maithili. The information for the info boxes for these five items are complete as well and could in theory be used in the Incubator project.

Info-boxes supported in the incubator that use Wikidata data seems to be an achievable goal. Adding Wikidata search support in the Incubator is actually a no-brainer because it just works. Thanks to the Reasonator all that data will be really well presented, it will even be informative. That is a step up from many of the awkward stub articles that are often found in the Incubator.

Wikidata is a great start for providing information in any language. All you need to do is add missing labels. The next step is start a stub with an informative info-box. This can be followed up by taking the time to write a decent article.

You know what, this does work equally well in any Wikipedia.
Thanks,
      GerardM

Sunday, June 09, 2013

Thanks for all the fish

Milosh is leaving the movement. It takes me aback. Last time I met him was at the Amsterdam hackathon, we discussed several things that might help our shared dream of more linguistic diversity in the Wikimedia movement.
  • Wikidata is to be opened to any and all languages that are recognised as a language. This includes artificial languages and dead languages. Some people may find it controversial that we consider Wikidata to be a project in its own right and, the connection to Wikipedia incidental.
  • Wikisource should be one project like Commons and Wikidata. It would be best when all the instances of Wikisource are merged. Wikisource as we know it, is very much a workbench. Important is that people know how to use the tools. It makes no difference what language your user interface has, what matters is the language of the text. This can be any language
  • When the work is "done" on Wikisource, it should be advertised, it should be marketed, it should find a public. That is very much something best done OUTSIDE of Wikisource. 
Ah well, these things make sense, they will improve linguistic diversity and they will create an environment that will even stimulate the creation of more Wikipedias. The question is how to find the energy to make this happen.. The Dutch are known for their windmills, just like the Spanish. We will miss Milosh for this fight.
Thanks,
      GerardM

Saturday, March 03, 2012

New templates for new #Wikimedia projects

People do request new languages on Meta. When a new language is requested, people will have to comply with a series of requirements. They are things like the localisation of messages, the writing of a few hundred articles that allow us to assess if what is written is really in that language..

When the requirements are met, when the members of the language committee are happy with the results, an e-mail is send to the chair of the board of the Wikimedia Foundation with the recommendation to approve the new project. Typically these recommendations are followed.

The next step in this workflow is the creation of a bug in bugzilla requesting the creation of the new Wiki. At that time specific technical information is needed. This information is needed by the Wikimedia engineers to create the project.


Robin made changes to the template and, we have changed the request for the Gujarati Wikisource. This request is in the final stage and we want to learn if the changes to the template make it easier to complete the necessary information.
Thanks,
      Gerard

Monday, October 03, 2011

Looking for language support for #Lezghian

People want a #Wikipedia in Lezghian. They have done the localisation of the most used messages for MediaWiki. Articles have been written so everything is ready for the final phase.

Checking if what has been written is Lezghian takes a bit of doing. Amir is on it. He will find people who can but in a way Amir does not scale. There are some 300 Wikipedia and incubator languages and ambitions for many, many more.

We need plan B. Plan A is doing everything ourselves, plan B is to have a framework for language support provide us with the answers. The WMF language committee has a need and the WMF localisation team is setting up a framework that may be able to help.

When people know their language well, they can do so much more for their language. Not only to get a Wikipedia but also to get a Wikipedia.
Thanks,
      GerardM

Sunday, August 14, 2011

What makes a #language a living language

The #Wikimedia Foundation provides hosting to any and all languages that are able to comply with the minimal requirements that have been defined in the language policy. For languages that have sufficient vitality and infrastructure this is a godsend; a Wikipedia is seen as recognition for a language.

Wikipedia is well positioned for this because of one early design decision for MediaWiki; the exclusive use of Unicode fonts. All languages that are supported with fonts are in luck. Recent work on for instance right to left languages will percolate into production in the near future, we are working on WebFonts and input methods and all this will be a game changer for many of the existing Wikimedia languages.

The Wikimedia Foundation has always been clear that its primary interest is not in the preservation of languages but in providing information to the people of the world. It has taken its time before the WMF is getting involved in increasing its support for languages. This is driven largely by the lack of growth in the "global north" and an astounding room for growth in the "global south".

When a language is a living language, it will at some stage have a presence on the Internet. Failure to do so will mean it will be increasingly marginalised. There may be mitigating circumstances like the use by a locked in community like the deaf and their many sign languages.

In the WMF language committee there is a big discussion about what to do with the languages that do not have a WMF project. Should we go out and stimulate people to start a WMF project in their language. Should we technically enable languages for the Internet and stimulate its use in the hope of a living WMF project at some later date...

Projects like indigenoustweets.com are very much the kind of projects we can support to further the use of more languages on the Internet. Even the use of Facebook or Google+ is a net gain when people use their language on the Internet. I am all for it, I am even for providing social software at the WMF. When we can help people use the Internet in any way, it will stimulate a language, a culture. First you give them their voice and then we may find a request for a new Wikimedia project. At the same time the chance of finding content about such a culture and language in for instance the English Wikipedia will increase. Now that, the sum of all knowledge, is what the WMF is about.
Thanks,
      GerardM

Saturday, August 13, 2011

#Wikimania question: "Jimmy what would you do with a million dollar"

The oral history of Wikimania has it that during a traditional board Q&A, I asked Jimmy Wales what we would do with one million dollars. Jimmy referred to this in his latest "state of the Wiki", the closing presentation of all Wikimanias.

In those days, the scrutiny of the community was no less; for many people Wikipedia only needed money for hosting, all other things were considered distractions from our "mission".

The Wikimedia Foundation has grown up considerably, its budget runs now in the multiple millions, its staff has grown to run programs that absorb the money that is put to good use. There is a steady flow of reports. The Wikimedia Foundation is doing well.

It is different with some of our chapters. Chapters are very much integral of our movement, they often gain considerable amounts of money during the annual fund raiser and it is often not known what they do, if they spend it and, how they spend it.

I urged several chapter people at Wikimania to let their stories be heard. Many of them are truly inspirational, a lot of good work is done but unknown to our wider community. As you approach them with good faith, even when you accept their good intentions, the sheer amount of money involved makes it hard if not impossible to accept the radio silence from many chapters. Spending money well is an art in itself, it is already hard when you are flush with cash and you have to consider even more money from future fund raisers...

There is a big dust up between chapter people and the board of the WMF. The board now insists on the transparency that has always been a must in the fund raising agreement. No longer is it a matter only of "thou shall be transparent", there are now sanctions on the horizon as well.

So, dear chapters get your stories out, become transparent, plan ahead, spend your money wisely, be happy to share your wealth when it achieves our goals. One more piece of advice and one question.
  • all chapters could do with one PR man getting the chapter stories out
  • the language committee knows how to spend some of your money... developing fonts for instance. Even the Latin script will benefit.
Thanks,
      GerardM


Tuesday, August 02, 2011

Sterkebak does good work and wants to continue doing it


I travelled to #Wikimania with Huib. He and Robin are fellow members of the language committee. Both are doing great work, both equally deserve some positive attention. Their stories are quite different.. Enjoy..
Thanks,
      GerardM

Who are you, where are you from
A 25 year old man from the Netherlands, with a love for taking pictures and currently setting up my own company. 

What WMF projects are you active on

I'm still active on Incubator, it used to be Commons and Meta also.

What are your personal priorities for Wikimedia projects
Sharing the things I know and doing the things I can do best. This includes sharing the pictures I can make. These are the most important things for me. 

You are a member of the language committee and admin on the Incubator, how do these two relate for you
I think both go hand in hand, being active on both incubator and the language committee makes it possible for me to be active in the whole process. From helping new languages to discussing them and after that importing it to the a own Wiki. It makes me proud to be a part of that process.
You have a sad reputation related to sock puppetry; can you explain this and explain yourself
First of all the reputation is a little bit not true, yes there are other account but it used to be that when a account is renamed the old account still exist. I'm renamed multiple times leaving those accounts behind. When you strike those accounts there are still 3 accounts left. The reason those accounts are being used is kind of simple. When you love a project very much you want to edit it. I just cant see the things I could do and look away.

You want to regain standing in WMF projects, what is important to you and what activities do you want to do
For me its important that I do the things I like and the things I'm good in, this includes my work as a photographer. I always believed it was important to share my pictures and I uploaded a complete portfolio to Commons. I come on some places where other people wouldn't easily come and its really important to me and it makes me proud that those pictures are shared under free licensing also. Since 2010 I'm a member of the language committee also and I believe that that work is very import and I like doing it.

The Dutch Wikipedia is the main source of issues, can you talk about your on wiki activities prior to your block.
I started on Wikipedia writing articles about graveyards (fields of honour) later on I start taking pictures with those articles as subject, from that moment on I stopped more and more writing and started adding pictures with that my edits also started to be less until it completely stopped because I spend more energy in other projects.
 
How relevant is it for you to be unblocked on nl.wp
Its not, I stopped editing there almost one year before the latest block, I prefer to work with images and writing articles is just not my thing.

Any comments on the “automatic” blocking on other projects ?
I think all project should decide for them self when they block somebody. Automatic blocks... I don't think they are being the best for the projects.

WikiWeet is the source of your problems, this is a project external to WMF Why did this spill into our Wiki world ?
The WikiWeet project was mend to be a project for children so they could start there and move later on to Wikipedia or Commons. This worked very well and lots of people don't see the difference between the two also because the children that used to be active there are now on Wikipedia. I think that the WikiWeet did what is was made for and it brought good children to Wikimedia but it brought some problems with it.

Sunday, July 31, 2011

SPQRobin does #Haifa

Tomorrow I am travelling with Robin to #Wikimania. We are looking forward to meet our Wiki friends irl. We will have fun meeting new and old friends and we may see the sights of another beautiful city.
Thanks,
      GerardM

- Who is SPQRobin in real life

I am Robin Pepermans and I live in Flanders, the northern part of Belgium. I just finished my secondary education, having studied Latin and modern languages. My next studies will likely be Public Administration and/or Translation Studies in Ghent. I started editing the Dutch Wikipedia in 2006 under my username SPQRobin. At that time I was very interested in Roman history and the Roman Empire. Even though my interests quickly shifted, I remained known under this nickname since then.

- You are involved in multiple projects, what are they and what role do you play

As I become more active in the wiki world, I discovered Meta, Commons, and also the Incubator. It was a relatively new project, where new language editions of existing Wikimedia projects are developed and maintained until they are active enough to have their own sub-domain. Incubator was however not maintained well, so I improved it and helped the users there. A few more people joined me, and there is now a little group who maintains the Incubator. Not only was Incubator itself not maintained, the process to start a new wiki was often slow and people kept asking when their wiki would be created (sometimes with no response). To improve communication, I became a member of the language committee in 2009. This committee is in charge of deciding which Incubator wikis are ready for creation. Incubator, being a special wiki like Commons, required some software features that are not easily available in MediaWiki. Therefore I applied for commit access so I could create a MediaWiki extension that provides these features. It took quite some time for this extension to be enabled, maybe because Incubator is a lesser-known project and not a high priority. I am working further on this extension, for example the plan (that especially I and Milos Rancic are pushing forward) is to make subdomains of non-existing wikis (e.g. xmf.wiktionary.org and yua.wikipedia.org) redirect to the respective welcome pages or main pages at the Incubator, (xmf Wiktionary and yua Wikipedia).

- Lately you have worked on bugs that have to do with RTL languages like Hebrew and Arabic. Are these patches in production and what are these patches about

Recently I became more involved in fixing bugs and making the software better. It was clear that a lot of the interface and features had poor support for right-to-left languages, even though a lot of the RTL bugs are relatively easy to fix. You don't have to be able to read an RTL language to be able to fix them :-) I noticed that ResourceLoader included CSSJanus, which automatically flips CSS, making the software A LOT better and easier to maintain for RTL interface. Even the old bug 6100 (interface direction should follow user language and not content language) would be fixed. However, the content was flipped as well, so this was disabled. I fixed this issue, along with many others, and I generally improved the directionality support of MediaWiki. These improvements are now part of the upcoming MediaWiki 1.18, and will hopefully soon be deployed on Wikimedia wikis. You can already enjoy the improvements on e.g. translatewiki.net, which always runs the latest software. If you have any bug reports or suggestions regarding RTL interface, don't hesitate to contact me :-)


- You are going to your first Wikimania, what do you expect

I am really looking forward to my first Wikimania. I hope to see a lot of people who I know from Wikimedia in real life, and to meet other people as well. I am going to the developer days, where I will talk about my RTL work and improve it even further with other developers, especially for the issues that I am not able to fix myself :) I could also talk about the Incubator improvements that I am developing, such as the welcome pages for non-existing wikis.

Since Belgium, my country is one of the few Western countries without a chapter, I might talk with other Belgians and Dutch people about a possible Wikimedia Belgium or even a possible Wikimedia Benelux.

The sad thing is that the developer days coincide with the Global South Meeting and Chapters Meeting, which both seem to be very interesting.


New wikis in 2010
- How many more languages will we support in two years time

Currently we are growing quite slowly in my opinion. There are yearly some ten to twenty new wikis opened, most of which are in European languages. Sometimes there are promising projects organised, that want to help languages in the Global South to get their Wikipedia, but then I didn't hear of them anymore. My hope is that the chapters set up such projects. For example India, Indonesia and Australia are starting to become active in helping small languages get support and get their Wikimedia wikis. South America is less active but I hope they will join too.
 -Robin

Monday, May 16, 2011

#mwhack11; most used messages have changed

In #MediaWiki, the "most often used messages" are called that for a reason. They are the messages that most often used. As software evolves, the messages that are most often used change with the time.

At the Berlin Hackathon, Siebrand was provided with new statistics and he has changed the composition of this group.

When you look at the group statistics, you will see that as a result there are now only 51 languages who have a complete set of localised messages. I do not have to repeat why it makes sense to do these messages first, but hey, they are the ones who are most often in your face. So do check them out...

The language committee will be processing all the outstanding requests and, all the languages that qualify for their first project will be judged against the old most used messages. Obviously, from a usability point of view even these projects do benefit from at least completing these messages.
Thanks,
      GerardM

Monday, May 09, 2011

The #Bihari #Wikipedia is actually written in #Bhojpuri

This is the kind of article that has many people's eyes glaze over. It is about standards, scientific documents and it is about languages most of my readers have never heard about. For the people that do speak one of the languages that are considered Bihari it is extremely relevant and it has implications for Wikipedia.

This is information provided by Umesh Mandal that explains about the "Bihari group of languages" in relation to the Maithili language:
Kellogg (1876/1893) and Hoernle (1880) regarded Maithili as a dialect of Eastern Hindi; Beames (1872/reprint 1966: 84-85), regarded Maithili as a dialect of Bengali, Grierson has done a great service to Maithili language, however, he erred when he gave a false notional term of "Bihari" language, after that western linguists started categorizing Maithili as a dialect of "Bihari" language; although there is nothing known as "Bihari Language" and both Maithili and Bhojpuri are spoken in Bihar (of India) as well as in Nepal.
Umesh is working on the localisation of MediaWiki for the Maithili language and as this language is currently in the Incubator, the language committee does its due diligence and tries to understand if Maithili can have a place in the Bihari Wikipedia. The information provided by Umesh makes it quite clear: "no".

This still leaves us with the misnomer that is the Bihari Wikipedia. Apparently the language used for the localisation and the articles is Bhojpuri. Bhojpuri has the ISO-639-3 code "bho". 

Are you still following all this? Ok, there is one question I am not asking: How about the Kaithi script?
Thanks,
      GerardM

Monday, April 04, 2011

The #CLDR does not work for us

A #standard works when it solves problems. #Wikipedia supports more languages than the CLDR and the result is that we cannot rely on the date format being available.

At translatewiki.net we are very much in favour of using data supplied by standards and, we would applaud it when we can work with Unicode to compile data that is its remit. One of the ways could be to have an area with a friendly interface where people can add this information.

The availability of such data could even be considered essential for the running of a new Wikimedia wiki in a language. The benefit would be that we cut the number of requests for changes to values and formats of data in our projects. The benefit for the CLDR will be that for many more languages information will be available.

The CLDR has as part of its process that information is verified by experts. This is also true when a new language gets its first Wikimedia wiki. Asking the expert to take special care for the locale data will help accept the CLDR to accept this data.
Thanks,
      GerardM

Wednesday, March 09, 2011

Comment period for 2010 #ISO 639-3 Change requests

Every year #SIL, the maintainer of the ISO 639-3 prepare a list of changes that people can comment on with the changes of the previous period. This list contains changes like codes for new languages, changes to existing codes and last but not least codes that are retired.

When the language committee decides that a request for a new language is not admissible, applying for a code is the best way of getting a reversal of that decision. This has happened several times.

So this is your chance to peruse the crop of changes to the standard. When your language is in there, we will be happy to consider your request for a Wikipedia once these changes are finalised.
Thanks,
       GerardM

Wednesday, March 02, 2011

Narayam shows the scope of an #Internet #language issue

Narayam is a #MediaWiki extension and it helps with writing articles in #Wikipedia. With several languages supported, additions for Narayam are queuing up.

When a mail is received from someone who is working for the government of Karnataka on a knowledge base asking for support in his application, a better perspective of the issue transpires. It is truly hard work to write Indic language content.

With the recent addition of Santhosh Thottingal to the Wikimedia language committee, we have a person who adds a history of practical involvement to the existing awareness of issues like these. When we provide support in MediaWiki for a language like Kannada or Singhala, similar support is needed in LibreOffice, Drupal or Wordpress to name but a few.

As the Wikimedia Foundation is through its projects the 500 pound gorilla of diverse language content, we hope to effectively raise awareness of language issues and stimulate solutions inside and outside our movement.
Thanks,
      GerardM

Saturday, February 19, 2011

What more should we talk about

In Berlin, in parallel to the #MediaWiki hackathon, members of the language committee of the Wikimedia Foundation will meet for a first time in real life.

As I read the roster of the people who may attend, I am amazed at their qualifications. All people are involved in their Wikipedias in the Incubator, they are linguists, standard people, a script expert, Wikimedians.

The first line of our business will be to evaluate what we do. We will get to know each other better and we will talk endlessly about language, Wikipedia and what not.

You can help us be more focused by suggesting topics to our agenda. Anything goes and when we understand the issue raised, we will attempt to formulate an opinion. When such an opinion is actionable, we will raise it with the people that can make a difference.

The topics may be all over the map and they do not need to be confined to the language policy or the Wikimedia Foundation. When there are issues in MediaWiki, we may pop over to the people at the Hackathon and ask their opinion.
Thanks,
      GerardM

Wednesday, November 03, 2010

A case for a #Wikisource in #Sanskrit

Sanskrit as a language is comparable to Latin and less so Old Greek. It is of immense cultural importance to the culture of India. There are a few people who speak Sanskrit as their mother tongue but this is less relevant compared to its importance as a language for source material.

There is a request for a Sanskrit Wikisource and some well respected Wikipedians urge the language committee to allow for its creation and wave the requirement for a full localisation in Sanskrit.

I am happy to support this request because we would allow for a dead language without localisation. Sanskrit is important for the whole of the Indian community; I believe that this will stimulate all the projects in languages of the Indian subcontinent. I am happy for the language committee to make an exception to the rule without changing the rules.

I hate complicated rules. The language committee contains capable and competent people, they are well able to consider situations where it makes sense to ignore the rules.
Thanks,
       GerardM

Thursday, September 16, 2010

News from the language committee

Following the example of the science committee, we now have a logo as well. It consist of the outline of the Rosetta stone and some characters that can be found on the Wikipedia globe.

The best news is that after some internal discussions we have found a way to be more open about our deliberations. The big change is that the reason for our confidentiality has been largely taken away.


Our future mail exchanges will be published in the same way because when needed it will be possible to flag portions as confidential. This will be used sparingly and it will be to protect privacy when needed.
Thanks,
        GerardM

Wednesday, September 15, 2010

Six more weeks

Now that the Usability Initiative software has been rolled out to all the #Wikimedia Foundation's projects it is close to that time when it makes sense to reassess the most often used messages.

The most often used messages are selected because they truly are seen most often by our users. This makes it a reasonable requirement for them to be localised before a new language gets its first project. It has been more then a year and half since this list was last updated and with the introduction of the Usability Initiative software we expect that the composition of the messages will change significantly.

The messages at translatewiki.net will remain the same for some five, six more weeks. The language committee is happy to assess if all the requirements are met in that time. Once the messages have changed, it will be the new list that is used to assess if the requirements are met.
Thanks,
        GerardM

Thursday, September 02, 2010

About openness and transparancy

CafePress.co.uk
It is annoying when other people tell you what to do. It is even worse when they do not listen to the arguments why things became in a certain way.

My communications to the Language committee are not open for public scrutiny. That is not that special as there are many WMF communications that are confidential.

One conversation with a person subscribed to the internal-l told me: "it is common practice to post on foundation-l when the subject does not need to be confidential and, that it should be posted to foundation-l as well".

This practice is flawed because of a number of people who refuse to enlist to the foundation-l. The consequences are twofold. First of all things do not get posted to foundation-l and secondly, their contributions are kept secret without a reason.

To me it is obvious that nothing will change. But the people who are on internal and not on the foundation list and bitch can buy me the t-shirt.. I prefer one in the XXL size.
Thanks,
       GerardM