Showing posts with label Strategy. Show all posts
Showing posts with label Strategy. Show all posts

Sunday, June 21, 2020

Marketing @Wikimedia but first some SWOT analysis

The Wikimedia Foundation has a 2030 strategy, it intends to increase its reach, increase its budget and rename projects into "Wikipedia something" in order to improve its visibility.. 

Wikipedia is one of the most visited websites on the Internet, its quality is good and is mostly edited by older white males in the first world. Typically when people mention Wikipedia they refer to the English version but it is only 50% of Wikimedia traffic. From a marketing point of view the English market is saturated, growth can be expected from Wikipedias in other languages and from other projects.

The Wikimedia Foundation is very much tied to the United States. Given the current regime and the possibility that it will prevail in November, this reliance is an existential threat. It is likely that the US government will want to intervene in Wikimedia content after 2020. I doubt it is possible, given the current hardware configuration, to move away from the US and still serve the rest of the world with a NPOV.

At this time the Wikimedia Foundation is centrally led, there are satellite organisations in many countries who are limited in what they can do; their budgets are centrally managed. Fundraising is mostly done from the USA and most of it is raised in the USA. That is problematic in its own right because many "Wikipedians" feel that too much money is raised, money not needed to support their project and people in other countries do not get to feel that it is "their" project because of "their" contributions. As a professional fundraiser, I am convinced contributions from the Netherlands could increase at least tenfold within a year.

The bias for English is huge and it is compounded by the bias for English Wikipedia. At a conference a Dutch professor stated that research not about or linked to the English Wikipedia is unlikely to get published. It follows that the data used for the 2030 strategy includes this same bias. The MediaWiki software is developed first and foremost for English Wikipedia and it is expected to work for other languages and for other projects. There used to be a development team specialised in language technology.. it was dissolved. 

There was a time when English Wikipedia did support the other projects. Because of an anti Wikidata stance by some this changed. There is no solution for false friends and lists are not as well maintained as they could be. When we link to the Wikidata item for an article and no longer to a title for that same article this will change. It is easy enough to build functionality that allows for both and by opt-in projects will understand the benefit and choose to adopt.

When marketing is the reason for changing the name of projects, it is important to consider the ramifications. The "Wikipedians" among us claim ownership of the Foundation, insist on actions in their image. They represent a staid community representing a saturated market. With a strategy in place it is possible to disregard them. This makes only sense when the WMF tackles its bias for English as a priority. This is what is needed to realise the 2030 strategy.
Thanks,
       GerardM

Sunday, August 25, 2019

#Translatewiki.net the @Wikimedia movement infrastructure most people even do not know


Just consider this, there are more than 200 functioning Wikipedias and this is only possible because people localise the MediaWiki software in over 280 languages. It makes translatewiki.net, the website where all this work happens a strategic resource to the Wikimedia movement.

Internationalisation (i18n) and localisation (l10n) are an integral part of software development. It is an integral part of a continuous process and it requires constant attention. The day to day jobs are well in hand. The localisation itself is a community effort and with developers continually expanding the software base a continuous effort is needed of the translators to keep up with their language. This is hard and for many languages it is a struggle to keep up with even the "most used messages".

Managing this effort is a continuous effort, it is essential to maintain the i10n and the localisation optimally. It follows that it should be obvious what messages have the biggest impact first on the readers and then the editors of a Wikipedia. What should be in the "most used messages" changes over time and when it is considered strategic, such maintenance is to be considered a Wikimedia/MediaWiki undertaking. 

Translatewiki has always been an independent partner of the Wikimedia Foundation and it has always been firmly part of the Wikimedia movement. Given that partnerships are a key part of the strategic plans of the WMF, the proof of the partnership pudding is very much in how it interacts with a translatewiki.net. TWN does not need to be part of the WMF organisation for it to fund TWN, it is clearly a quid pro quo. The WMF should even encourage TWN and other partners to collaborate for their i18n and l10n and enable this for strategic purposes, strengthening these partners globally. 
Thanks,
     GerardM

Sunday, February 17, 2019

@WikiResearch - Nihil de nobis, sine nobis

There is this wonderful notion how Research is going to tell us what to do in light of the strategic Wikimedia 2030 plans. Wonderful. There is going to be this taxonomy of the information we are missing.

Let me be clear. We do need research and the data it is based on, it is to be available to us. There is no point in a future taxonomy of missing knowledge when we have been asking for decades : "what articles are people looking for that they cannot find". If there is to be a taxonomy what else should it be based on?

When we are to fill in the gaps of what Wikipedia covers, we can stimulate more new articles by indicating what traffic they get in the first month. Stimulate our readers to learn more by showing what Wikidata has to offer and show its links to texts in other languages. It may even result in new stubs even articles in "their" language. This technology has been available for years now.

The WikiResearch is full of arguments on the importance of citations and Wikidata as the platform for all Wikipedia sources, why then are the WikiResearch papers not in Wikidata from the start. What is it, that WikiResearchers consider that Wikidata is not about them? Just as it is about any other subject Wikidata covers? What is it that makes their work less findable (FAIR) than what is known to have been published as open content by the NIH?

The point I want to make is that no matter how well intended it is what the WikiResearch aims to achieve, they lose the interest, involvement and commitment of people like me, the people they need to get the results they aim for.

Yes do research, but we should not wait for its results, we know how to stimulate people to write new articles.
Thanks,
      GerardM

Thursday, December 14, 2017

A purposeful #strategy for #Wikidata

A strategy for Wikidata? Obvious, it is all about having a purpose. It is not about policies, it is not about what we need or expect of others but it is about the purpose you, I and others have for us to collaborate on in an inclusive Wiki and data project.

The implication of making the purposes of our community rule supreme are huge. Purpose like so many other things can be measured. When people have a purpose for Wikidata and actually use it, their need for quality is self evident. They will invest their time and effort in fulfilling their purpose. The one question is how to fit in the many purposes that exist for Wikidata.

Take for instance the objective of Lsjbot for a rich Wikipedia in the Cebuano language. He uses data from an external database to create articles. Data from these articles are imported later through the Cebuano Wikipedia in Wikidata. This is seen by some as controversial because of the need to integrate data that often already exists. The purpose is obvious; rich information in the Cebuano language. The solution is obvious as well; let Lsjbot use the data at Wikidata to generate the information for the Cebuano Wikipedia. GeoNames is happy to collaborate with us on this, so when we care to collaborate and welcome its data at the front door, we can mix'n'match the data into Wikidata, curate the data where necessary and share improved quality widely, not only on the ceb.wp.

The Biodiversity Heritage Library Consortium is working extremely hard to expose their work to the general public. Over a million illustration found their way to Flickr. Fae imported many of these to Commons and most if not all the associated publications can be read on the Internet Archive or on its website. Their content is awesome, check for instance their Twitter account. We can import all the BHL books in Wikidata, we are importing all associated authors using Mix'n'Match. The images are in Commons but how is this brought together? How do we add value for the BHL and as important, for our shared public?

The Internet Archive is a Wikimedia partner. It provides essential services for us with its "Wayback machine". It is how we can still refer to references that used to be online. One other venture of the Internet Archive is its Open Library.  What we already do for the Open Library is linking their authors and by inference books to the libraries of the world through VIAF. We could share this information with the Wikipedias so that its readers may find books they can read. (Talk about sharing the sum of all knowledge).

Both the IA and the BHL want people to read. They (also) provide scientific publications that may be read to prove the points Wikipedia authors make in articles. Both can be big players strengthening the value of citations in WikiCite. At this time its strength is particularly in the biomedical field and it is already attracting bright people to Wikidata. As data from other fields finds its way, people like Egon and Siobhan will find their way. This will make Wikidata even more inclusive.

To make this future work, to become more inclusive, we should trust people more particularly when they indicate why they use Wikidata. The Black Lunch Table is a great example. The description at Wikidata says: "visual artists of the African diaspora initiative that includes Wikipedia editathons and outreach". One way of knowing how effective this initiative is is the history page of its listeria list. It shows a steady growth of information added. When you analyse it further you find artists added and selected for new editathons. Truly a great example of Wikidata having a purpose.

A strategy based on purpose, is a strategy based on trust. Not blind trust, but the kind of trust where it is seen that people are committed to improve both quantity, quality and usefulness of the data they identify with.
Thanks,
      GerardM

Sunday, November 05, 2017

#Wikimedia - I endorse having a #strategy as it is good to have one

Having a strategy is great. There are objectives and there is an idea how to get there. As the Wikimedia Foundation formulates its strategy, it is complicated. Complicated by necessity because it involves so many interests, people who invested so much of themselves in their project(s), people who speak so many different languages, languages that define them, people with different backgrounds because they define them as well. The strategy must be complicated because it aims to reconcile all these people and the organisations that represent them.

When you are a Wikimedian, it helps when your vision coincides with the vision implicit in this big strategy. I was asked to present at the Wikmedia Nederland conference; I presented a historic view on information gathering and sharing. The presentation was given in English because it was the one common language in the room.

I love presentations but talking with people I love even more. I was asked for stategies behind the things that I do, the things I value. The Luc Hoffman award is an example. It does not have a Wikipedia article but the subject, the science is of real relevance in this time of climate change. The idea of associating links (blue, red and black)  is a non confrontational way to bring Wikidata value to Wikipedia. Adding all the USAmerican alumni from en.wp categories will allow us to keep up with what they hold and know about even more USAmerican alumni. There is method behind the madness.

Now that the Wikimedia strategy goes to the next phase; I hope for many user stories; stories explaining what we are going to do and for whom. I also hope that technical considerations will not prevent innovation and improvements. In the end that is not what a strategy is. It is the hope for the bright future we deserve in our Wikimedia movement.

Sunday, April 02, 2017

#Wikimedia - First a #strategy, then #Action

The people at Open Library have books they love to share. They are in the process of opening what they have even more.

In a previous post it was mentioned that there is a JSON document to getting information on authors like Cicero. There are many works by Cicero and today they have a JSON document in production for the books as well.

So what possible scenario is there for the readers of any Wikipedia; they check in Open Library what books there are for Cicero (or any other authors). They download a book and read it.

Where we are:
  • there is an API informing about authors and their books at Open Library based on the Open Library identifier.
  • an app can now be build that shows this information
    • this app could use identifiers of other "Sources" like Wikidata, VIAF or whatever on the assumption that Wikidata links these "Sources".
    • this app could show information based on Wikidata statements in any language using Wikidata labels.
    • this app may download the book (maybe not yet but certainly in the future)

What next:
  • investigate the JSON and see what we already can do with it
    • publish the results and iterate
  • Add more identifiers of authors known to Open Library to Wikidata
    • there are many OL identifiers in the Freebase information; they need to be extracted and a combined list of Wikidata identifiers and OL identifiers allows OL to curate it for redirects and we can then publish.
  • Raffaele Messuti pointed to existing functionality that retrieves an author ID for Wikidata and VIAF using an ISBN number.
    • Open Library knows about ISBN numbers for its books. When it runs the functionality for all the authors where it does not have a VIAF identifier it can enrich its database and share the information with Wikidata.
    • Alternatively someone does this based on exposed information at Open Library.. :)
  • We add a link to Open Library in the {{authority control}} in Wikipedia
  • We could add information for nearby libraries like they do in Worldcat [1].
  • We can measure how popular it is; how many people we refer to Open Library or to their library.
At the Wikimedia Foundation we aim to share in the sum of all knowledge. We aim to enable people acquire information. Making this happen for people at Wikipedia, Open Library and their library is part of this mission we just have to be bold and make it so.
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?

Friday, August 01, 2014

#Wikidata - #priorities

Wikidata is relevant because it is used. The primary use case that makes Wikidata relevant are the interwiki links. Wikidata gained relevance as more Wikimedia projects used Wikidata for its interwiki links.

There are ambitions to add more relevance to Wikidata. This is done by giving an application to the data that is included in Wikidata.

  • external sources are shown based on Wikidata information
  • automatically generated text for "humans" in English
  • automated descriptions
  • presentation of information in Reasonator
  • query in WDQ, Autolist and Autolist2.
  • automated descriptions are used in "Wikidata search" on many Wikipedias
Particularly for humans, this works rather well. This house of cards relies very much on one premise; that we know what a Wikidata item is about; is it a human, a house, a settlement or a record label?

For most of our items Given that we do not know what an item is about. For me it is a priority that as many items get identified for what they are as soon as possible. This makes it possible to make a statement that a person is a journalist, an engineer or whatever. 

There are issues with this approach. There is this potential for false positives and at the same time it provides us with possibilities as well. Once false positives have been recognised as such, they can be used to identify other items for what they are. Once the right identifiers have been set as well, it becomes easier to remove the wrong identifiers.

The biggest issue however is with our community. Not everyone shares the same priorities and insights and this is made worse because many people Wikidata only know the standard functionality. For them "Widar" is playing a game. They are not aware that the bulk of the edits are done with Widar or by bot and that the interface they use is inferior. These people have good intentions but they have no clue.

Add to this that communication channels do not really function and what we have is quite messy. 

It will not really improve until we share more of our priorities and listen to each others arguments and work together towards solutions. As it is there are too many perspectives and, conflicting priorities aplenty. Consequently there is plenty frustration shared by all.
Thanks,
      GerardM

Saturday, October 01, 2011

Official languages of #India; we support you

#Wikipedia supports over 270 languages from all over the world. This is much less than the 452 languages listed for India.

India is strategic for the Wikimedia Foundation and consequently its localisation team has been tasked to provide the necessary language support. To make it manageable, we will be concentrating our effort on the official languages of India.

This will be challenging; we want to make sure that everybody can actually enter the characters for the scripts involved and see the results. Some languages are written in multiple scripts, will it be possible to see these results in these scripts?

For all these challenges, the team will do the heavy lifting and create enabling functionality. It will be really hard to find the input methods, the fonts, the conversion tools for each language as well. For this reason we need people to join us in our language support teams. We need people who know if zero is a plural or a singular in their language, we need people who can find us the appropriate and freely licensed fonts, we need people who can help us test our software for their language.

We need you.

By the way, if your language is not one of the official languages of India, the heavy lifting for India does provide you with the tools to do the same things for your language. Helping you to help yourself is something that will always be important to us.
Thanks,
      GerardM

Sunday, April 10, 2011

#Newbies nor #admins are the problem. #Trust is.

Once trust is lost, it is hard to regain. #Wikipedia has a problem with the stickiness of newbies. That is, we want the good to stay with the project and we want the bad to take a hike. Something similar is true for admins.

As we need both newbies and admins and as there is a lack of trust, trust is what we must build. Building trust is a process, a process takes time and effort when we are to close the chasm that exists between the good newbies and the good admins.

The Wikimedia board published a resolution where they outline a direction that is to bring us openness and collaboration. The board has cause to take this initiative because they have identified the retention of good people as our number one priority. They charge Sue and the WMF staff to make this their number one priority.

To trust WMF staff, you have to know them. As the staff is to reach out to the communities, information should be available on all the staff with a high quality picture. This makes the staff less remote and it builds trust.

When newbies come to us, the good ones are likely to have friends. When these friends are Wikimedians, we typically trust these friends. When an admin  can ask these friends to take our newbie under their wings, they have reason to trust.

When it is easy for newbies to find their Wikimedia friends, their initiation of our procedural vagaries become less intimidating. When a friendly, open environment is considered to be a deliverable, it does not follow that this gives a free reign to the vandals, the trolls. They are and remain the main cause of the existing lack of trust. Their stickiness is why admins have blocking powers, their wrangling is why we have arbitrators. They can trust us to fight them.

The newbies and the admins are not the trolls. They need an environment that makes trust, particular initial trust easy and this is why we need to be open, collaborative and much more social.
Thanks,
      GerardM

Friday, April 01, 2011

#Newbies are a social problem and require a social solution

The English #Wikipedia has two closely connected problems. Not enough newbies and too many newbies. The second problem is efficiently dealt with and several studies have confirmed the existence of the first.

The strategy of dealing with new articles, particularly new articles is one of scorched earth. This tactic is developed by dedicated, well meaning people whose objective is to maintain a high level of quality.

The lack of newbies who grow into valued editors in our projects is considered to be the most serious challenge we face. Studies are done, statistics compiled, meetings are convened, policy papers are written, IRC discussions with Sue are held, it must be serious.

Making villains out of the recent changes patrolers is one solution but that does present its own problem. Our conventional solutions offer no solace. Really, it is time for desperate measures as we face desperate times. Wikipedia as we know it could die.


Wikipedia needs to change in order to cope. To find out, we need to analyse the situation.
  • a well meaning newbie writes his first contribution
  • in order to cope with the flood of new contributions it gets deleted by a well meaning admin
Let us change the game by introducing a social dimension.
  • a person comes to Wikipedia, he has friends in Facebook, MySpace, Buzz whatever
  • this well meaning newbie writes his first contribution
  • a well meaning admin asks his friends to help him improve his act

All real people have friends, and when someone is attracted to Wikipedia, it is likely that some of his friends are already there. Real friends will help out when asked so why not ask them to help out.

As Wikipedia has a social problem, any technical attempt to a solution will have only a limited impact when it has no social dimension. When Wikipedia welcomes a newbie and knows its friends, we have a realistic alternative to the well meaning admins; they can kick the contribution to the "Russian incubator" where it can be nurtured in a friendly environment.

I bet my reputation that we need more social skills
Thanks,
      GerardM

Thursday, March 31, 2011

Best blogging practices II

My purpose as a blogger is to inform widely about significant developments for a range of topics. Because of my publishing frequency, the stories together read like a narrative; they became more about the journey then about an arrival.

Every time a subject is raised, there has to be a story with a fresh angle with fitting illustrations and appropriate hyper links. Doing this well, grows the audience for a blog and it also raises the ranking of my articles for the search results. This mechanism is the only reason I can think of why this is my best read article with currently 5,692 page views.


It is important to understand that a writing style defines a public. For me no long academic style articles, I think these are overrated because many readers do not finish them. They are not for me because an academic article aims to cover the whole ground while I prefer to celebrate developments and call attention for opportunities. By more then doubling my readers within a year, the numbers prove the viability of my formula.

Traditionally the English Wikipedia and its public dominate wiki publications. The distribution on the map shows that my public is largely in Europe and Asia. This coincides with where the most interesting Wikimedia community developments occur. It is where I expect the biggest growth in activity and traffic for the Wikimedia projects.

The Wikimedia Foundation aims to grow in the "global south"; there is a public, there are able communities held back by a lack of base technology. I raise these issues and I look for partners in crime. It should not be a crime, it should be our way forward.
Thanks,
      GerardM

Wednesday, March 30, 2011

What comes first, the study or the paradigm shift

Citation needed
#Wikipedia on a #mobile sucks big time for many languages. All it takes to realise this is to try it. Even if you don't, our statistics on mobile traffic for Wikipedia prove this conclusively.

When we are to generate more traffic, it is relevant to realise that a mobile is essentially a computer with a different form factor. As mobiles gain their smarts, it is not so much that they become better looking but more that they gain more attributes from a computer.

The big difference between computers and mobile phones is that computers have an open architecture while mobiles do not. Many of the mobile architectures are based on computer architectures and fortunately displaying text is one of these. As a result, the smarter the phone, the easier it is to send web fonts to a device and get a readable result.

There is proof that we can show Malayalam text on an iPhone. When we implement web fonts technology, not only mobiles will benefit. It will bring a paradigm shift to reading Wikipedia; as long as a device can show Unicode properly, any Wikipedia will be readable.

Does it take a study to understand such benefits? No. Does implementation invalidate the study? Possibly. Is there a reason to wait on implementation of web fonts? Yes, it takes more development. Should this development get the highest priority? Depends on how highly we value bringing knowledge to more people.
Thanks,
       GerardM

Friday, March 25, 2011

Money makes the world go around

The #Wikimedia meta discussion on movement roles has a personal point of view published by Sue. One of the issues she addresses is funding.

Funding produces the go-juice for our many activities but this go-juice is not distributed equitably and its mileage can be improved. Funding has a life-cycle; first you acquire the spending power, then you spend it and finally you enjoy the benefits.

Money is best held tightly and in order not to pry it from tight fists, it would work miracles when it can only be held conditional on it going around our world. Benefits going around or not is observable Take WikiPortret, Toolserver or PDF export they all have limited use while having a global potential. Contrast that with Wiki Loves Monuments Europe, GLAM outreach or MediaWiki development where the result goes beyond a language, a country, a culture.

So lets make use of the inclination to be tight fisted and let our organisations retain control over money when its projects have an observable global reach. When "others" rate the reach of projects, it will promote cooperation. As each project is rated, it will be known and, that is in itself observably good.
Thanks,
        GerardM

Saturday, March 12, 2011

From a #Wikimedia #strategy to a #Wikimedia plan

Once a strategy is defined and adopted, it is time to plan. As the strategy took a lot of effort by many people to define, the resulting plan is quite complex as a result.

With the product whitepaper published it is time to read and comment. It is a big read and, it takes quite some effort to take it all in. As Sue writes in her March strategy update, by publishing early we can comment early and be involved.


As you can imagine, there are improvements to make; I would for instance like to see "Text input and rendering" under languages. This allows for web fonts and this will enable more people to read our content. The good news is, that this can be found in the taxonomy (G.2) so it is just needs fixing in this illustration.

It is well worth getting your teeth in to this document and help cross the t and dot the i as the result of this plan will very much influence our future.
Thanks,
      GerardM

Friday, March 11, 2011

Which languages offer the most potential for your website?

When resources are limited, this question is relevant. Then again, what resources are limited. When commercial translators wonder which languages offer the most potential, the resources are people translating.

Affluence is a factor as well as the size of the Internet population. When Inuktitut is rated over Bengali however, it makes you wonder what value such numbers hold. Surely the people in Bangladesh who have Internet make more then the average wage.

For Wikipedia its resources are not limited by the number of editors as they are by volunteers. With over 270 Wikipedias even another language is hardly noticed.

The limiting factor for the potential of many of our projects that is solvable is technology. In order to invest in such technology, the potential of the languages involved has to be considered. The direction of the answer for the Wikimedia Foundation is quite unique; the question is not what language but what technology to invest in. Many enabling technologies have applications for any script, any country even any language.

Technical issues do have a direct impact on the generated traffic; Malayalam Wikipedia provides a typical example. As we support the latest Unicode technology its traffic suffered. There are two solutions that will generate more traffic
  • web fonts so that everyone can read the text
  • providing search engines text expressed in different variations for a script
The best part of many language technologies is that they are generic. The technology is often applicable for multiple languages, scripts and even platforms and applications. As we invest in such things as off line readers, even Internet penetration is not that important when our off line support hits its mark.
Thanks,
      GerardM

Tuesday, March 08, 2011

Keep your eyes on the prize

The #Wikimedia #strategy is clear; double the #traffic and particularly double the traffic from the "global south". With the prize defined, we should  do what it takes to realise this result.

Having defined a goal and knowing our current status, it is important to look for potential. What does it take to realise the involvement of communities that have not warmed to Wikipedia yet.

The two of the biggest success stories are Russian and Indian. Both are inspiring and both leave accepted wisdom behind. The Russian approach to newbies is inspiring and the Indian approach to their languages is outreach at its best.

For the Indian language communities, the English language Wikipedia is where much of its potential readers are hanging out. If they are to take articles in their native languages seriously, the quality of these articles has to be as good. When you look at the number of workshops organised, it is amazing. They come thick and fast for the many languages.

Indian developers are also getting into the act. The first results can be found in the Narayam input methods. This is combined with outreach to the language communities who can benefit from this and testing is done both on a private wiki and at translatewiki.net. These technical Indian Wikimedians are also involved in projects outside of the Wikimedia Foundation. As a consequence, solutions can be local to MediaWiki and external to MediaWiki.

The solutions we should adopt and develop are those that do the most good and provide real solutions for our language communities. Particularly solutions that remedy flawed production processes like our PDF export or the openZIM support are strategic.

They are strategic because they demonstrate the importance the WMF gives to providing equal opportunities to its communities. Any investment that we do not only helps us to enable our communities, but they also provide perfect opportunities to reach out to the people who do not know our projects yet.

These opportunities are what our man in India will want to leverage in marketing our opportunities and culture to the people of a country we recognise as having the biggest unrealised potential.
Thanks,
      GerardM

Friday, December 24, 2010

The #Malayalam enigma

Traffic for the Malayalam Wikipedia has gone down dramatically while the number of articles and the number of editors has gone up. WHY??

When you look at the statistics, you will see that traffic halved in a couple of months. So what happened... and as importantly can we do something about it and do we need support to turn this situation around.

The first clue can be found on the main page. It says:

Reading Problems? Click here

 There are two scenarios; either you see no text or there are too many spelling errors.


When you look up the word "Karnataka" in English on Google, you get about 10,700,000 results. When you look up the word "കർണ്à´£ാà´Ÿà´•" in Malayalam in Unicode 5.1 you get 2,760 results and when you look up the word "à´•à´°്‍à´£്à´£ാà´Ÿà´•" in Malayalam in Unicode 5.0 you get 117,000 results.

Are you surprised when Wikipedia uses the latest edition of Unicode? Are you surprised when Google makes a difference between two words that are actually the same word written with different characters? The real surprise is that the Malayalam community has found a way to show the same text with fonts in either version of Unicode.

The big fall in traffic is because many people use typing tools that produce Unicode 5.0 to type and search the keywords. Search engines understand them as different. There needs to be canonical equivalence between the old and new Unicode. In the above example, both à´•à´°്‍à´£്à´£ാà´Ÿà´• and കർണ്à´£ാà´Ÿà´• should give the same results.

The question then becomes how do we convince the search giants of this world to include both versions of the written words in their results. The big fall in traffic is due to the conversion of all the Malayalam texts to Unicode 5.1.

The good news is that our Malayalam community is quite happy to help the search engines with conversion software because we want our traffic back.
Thanks,
     GerardM

Sunday, December 05, 2010

Welcome to #Wikipedia

We'll have newbies for breakfast and lunch... what is for dinner? Seems to sum up the welcome given to new Wikipedians. Particularly the bigger projects are infamous for the "we know best because we are here longer" mentality.

It certainly proves that we as Wikipedians are not good Christians because otherwise we would have learned that Jezus did not like the practices of the Pharisees and also that what you do for the least of us, you do for Jezus.

So what can we do to welcome our newbies in our ranks. To start off, we can let them be bold and have them introduce themselves. Best practices at translatewiki.net has them identify their language ability and ask for translator rights. This is extremely valuable because it establishes that they understand English. We use the Babel extension for this and it establishes in what language a person can communicate in. It does not require templates so it is particularly beneficial for the small and new communities.

Many Wikipedias have projects dedicated to subjects. It would be nice when people can identify their interests. This allows people with compatible interests to take the newbies under their wings and protect them from the worst abuse.

Finally, we can add value for being a Wikimedian. As the Wikimedia Foundation is a five hundred pound gorilla and unlike with Facebook and Google our users are not the product so it would be a gift when we can like Facebook and Google identify ourselves as Wikimedians.

I would be happy to be identified as a Wikipedian and I would love to learn any argument why a Facebook or a Google would not accept such credentials. By establishing an identity anchored in the Free content world, the merits of our ways will rub off on anyone new to us and this may prove strategic in realising our aims for the next five years.
Thanks,
      GerardM

Wednesday, November 24, 2010

Opportunities, equal for all

When we write our #Wikipedia articles, we are all volunteers. We are given the same opportunity to write in our own language and all our efforts are needed to realise the aim of the Wikimedia Foundation i.e.: "Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment".

The Wikimedia Foundation is responsible for the MediaWiki platform. MediaWiki provides support to many languages; the group statistics at translatewiki have currently 337 entries. Most languages are in the Latin script and these are reasonably well supported. Many other languages have a problem; their script can have debilitating issues that prevent Wikipedians writing their articles with the same ease that is considered normal for the English language.

The native languages of the Indian subcontinent all have a problem. The effect of the script issues can be best appreciated by comparing the Indonesian Wikipedia and the Malayalam Wikipedia. Their number of contributors is roughly the same but the output of new articles in Malayalam is quite different and consequently the traffic it generates is much less.

BBC support for Hindi
for mobiles
When India and with it explicitly the Indic languages are part of a new strategy, the direction is decided. What is not decided is how you get there, the new roads you will have to travel and the companions you will meet on the way. The BBC supports Hindi on mobile telephones by showing texts as images and while this may suffice for readers of Wikipedia for editors this is just not good enough.

When the WMF is serious about an India strategy, it will  take ownership of the issues and tackle them. It can partner with other organisations but it cannot abandon its requirement for a solution. As the WMF is the 500 pound gorilla of the Free Content world it can partner with governments, with standard organisations and the developers of operating systems for mobiles and computers to make the difference that is needed to realise a working strategy for the Indic Wikipedias and for India.
Thanks,
       GerardM