Showing posts with label hackathon. Show all posts
Showing posts with label hackathon. Show all posts

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

Saturday, August 23, 2014

#Wikidata - the #beta label lister


At the hackathon of #Wikimania2014, work was done on a new version of the label lister. It is a gadget that allows you to edit labels and aliases in other languages. It proved to be an indispensable tool to me. Today I learned that the new label lister is now available.

The most wonderful thing is that it became much more compact, you do not need to click as much anymore and it "just works". In the screenshot you see Mrs Bundschuh, she is a former member of the Landtag of Bavaria, and as you can see it is trivially easy to add a label in your language.

I hope that functionality like the label lister will make it into a core feature of Wikidata.
Thanks,
     GerardM

Monday, May 12, 2014

#WMHack #Maps and #Wikidata II

This hackathon had many people with an interest in maps come together in Zurich. There were several challenges they faced; how to represent maps in a wiki, how to store them and what do we need to know about them in Wikidata. In this mix of challenges the differences between contemporary maps and historic maps feature as well.

Wikidata needs to know several specific things; it needs to know that something is a map, it needs to know the four corners of a map, the location where that map can be found and finally it is nice to know what type of map it is. More attributes are possible but this was considered the minimum for Wikidata.

The thought process about Commons was forward looking; it is going to be "Wikidatafied" and this will surely affect current practices. Information that is currently in templates will move into Wikidata and many of the galeries and categories will surely become redundant because queries will provide a more reliable and complete result.

For Wikis, current best practices were analysed and, it was found that information on a map exists in many layers. There is a base layer and on top of that you can show a contemporary or historic map. On top of it you may want to show the shapes of countries or districts. These may be sprinkled with pointers that reflect the result of a query. To finish it off, you may want to add even more that demonstrates a point made in a particular article.

All this information needs a place. It needs a special place because you may want to use a map several times. In Zurich we ended of a working example of a map that included all these complications by inserting information in a namespace. The next challenges are to make it robust and user friendly enough.
Thanks,
      GerardM

Sunday, May 11, 2014

#WMHack #Maps and #Wikidata

This hackathon and many maps put #Zurich on the map. When you consider maps and, particularly historic maps, they have four corners and a date. That is the minimal approach to a map.  You can add to this what a map intends to show, it can be a thematic map or a generic map.

When you add the four corners of a map as properties to a map, you can query for the maps that include Zurich.. When the maps are dated, you can show them in order..

It is really exciting that it has been decided what we need in a map on Wikidata.
Thanks,
     GerardM

Saturday, May 10, 2014

#WMHack - This is not a hack, we can share in the sum of available knowledge

The Wikimedia Foundation wants to share in the sum of all knowledge. What we can do now is generate text on the fly based on the knowledge available in Wikidata. In that way we can share in all available knowledge we languages on all subjects.

Wikidata may provide Wikipedia of services.When Wikidata was conceived, its first line of business was to replace all the "interlanguage links of Wikipedia. As a result it knows about more subjects than any Wikipedia. It knows about for instance more US-Americans than the English language Wikipedia. An other objective is to include statements for each item so that information can be centralised in Wikidata for use in any and all projects.

When the statements have labels in a language, it is possible to provide information in that language. It could be any language even English. The current thinking is very much: "we can serve the information boxes in articles from Wikidata". What Reasonator and WD-Search prove is that those articles do not need to exist. Most members of the South African National Assembly do not have articles in any language but information could be found in any language spoken in South Africa.

We can use machine translation to translate articles but we can also use similar algorithms to generate text based on the information we have. This has been done often in our wikiverse; they are the bot generated articles. In the Reasonator we generate text about humans in English and a few other languages. It is not rocket science to improve on what is there. In essence it is exactly what we do in our localisation functionality in translatewiki.net. It follows that we have some ability for at least 280+ languages.

This is possible with current technology, the software comes with a great pedigree. It is brought to you by the same human who started with MediaWiki.  He is a scientist and the functionality is for you to enjoy in so many ways.

The point is that we can. We can share in the sum all the knowledge that is available to us. We can do more than aspire, we can share much more of the wealth that is hidden on our servers.
Thanks,
     GerardM

Thursday, May 30, 2013

#WMhack - produce a list that shares a #Wikidata attribute

At the Amsterdam hackathon it became clear that Wikidata can be used as a powerful tool to improve Wikipedia. The idea of a hackathon is that you go home with new hacks and, I want to share a really nice one. It is a list. A list that indicates every known link within Wikidata from a given topic.

The cool thing is that it is the standard MediaWiki "what links here" functionality.

When you copy the "following pages" for this item, you can use the "text to columns" functionality to get something that you can use. With search and replace you can build a string that looks like this..
 {{#invoke:Available|link|Q48210}}
Many of such strings together produce a list when the Lua module Available is present on your Wiki.

When you see the Q numbers, there is no article about the subject. When you see a name in red, the label exists in Wikidata but there is no article registered for this subject. When you see a link in blue, there is a label and, there is an article.

This is a genuine hack that is really useful to complete articles on the same set of Wikidata items in any and all Wikipedias.
Thanks,
       GerardM

#WMhack - #SignWriting in #Wikimedia #Incubator

One visitor at the Amsterdam hackathon was Stephen E Slevinski Jr. He was a man with a mission. His mission was to get American Sign Language on the Incubator. As you can see in the picture below, he succeeded in his mission.

Several members of the language committee knew that it was possible for Stephen to succeed. We also knew that when this hurdle was taken, any and all sign languages can ask for their own Wikipedia. There have been requests for languages like Danish sign language in the past as well.

Now that we have the technical ability to show a sign language, the old reason not to express "eligibility" for these languages has gone. Any and all sign languages that have an ISO-639-3 code will find that there is nothing that will prevent them to work towards a Wikipedia or any other project in their language.


I want to thank a few people. First all the people at the Amsterdam Hackathon who helped Stephen make this dream come true. Secondly, I want to thank Stephen, Valerie and all the other people at the SignWriting Foundation for their continued belief that their languages and their culture deserve their own  Wikipedias.
Thanks,
       GerardM

Sunday, May 26, 2013

#WMhack - Dates for #Wikidata

At a hackathon you may preview what is about to happen. Dates for Wikidata is something that has been eagerly awaited. Given that Wikipedia has articles on many events, it is obvious that Wikidata is one place where assertions on these events should end up.

The most obvious dates are the date of birth or death for a person or the date a ruler started his rule end, the date it ended.

There are many issues that I can think off about how dates are to be used. But the fact that dates are finally being tested and are likely to arrive in a weeks time is a reason to be happy.
Thanks,
      GerardM


#WMhack - About #Gerrit, #GIT and #SVN

When there is still so much noise about GIT and GERRIT more than a year after the transition from SVN, you can wonder if the move from SVN was the right one to make.

At the Amsterdam hackathon there was expert help available for everyone who wanted/needed to learn more about using GIT and Gerrit and as I was curious to the answer, I asked the question.

The most important reason to move was because of Git. Using Git many new functionalities became available that made the MediaWiki developers more productive. Gerrit is something of a pain but it is usable and it is improving. So much so that the conversation of dropping Gerrit has subsided.

When you wonder about the question "was it worth it", you also have to consider the TCO or, the total cost of ownership. I came up with the question if the increased productivity had to be offset with the cost of one person supporting Gerrit. I learned that SVN also required a lot of tweaking. The CodeReview extension was written by the Wikimedia  staff.


A hackathon isn't a hackathon if it is not for showing off things that are in the works.. GitBlit is as I understand it one tool that is intended to make things easy.. More about GitBlit here.
Thanks,
      GerardM

Saturday, May 25, 2013

#WMhack - Historic maps .. more empires

Conferences are also places where you make friends. Fareh showed me an application where you can see how Islamic states evolved over time. It is really powerful as it visualises history I did not learn about in school, in my country.



For much of the background information it relies on the Arabic language Wikipedia. We discussed how Wikidata could provide information in other languages as well.. I for one do not understand enough Arabic. The user interface of the application might be translated at translatewiki.net as well..
Thanks,
     GerardM

#WMhack - Building empires

One demonstration that impressed me a lot is this animated map with border fortifications along the border of the Roman empire.
Thanks,
     GerardM


Monday, June 04, 2012

#wmdevdays - #accessibility

At the Berlin #hackathon 2012 many people were hacking on many subjects. Kai Nissen worked on the accessibility of MediaWiki by people with a visual impairment. At the end of the hackathon several bugs were squashed and ready for review in Gerrit.

It is wonderful when reports on defects are actionable and when something gets done.
Thanks,
     GerardM

How was the Berlin Hackathon 2012 for you
I participated in the Hackathon for the very first time and was quite amazed about so many people coming together and actually work productively on feature enhancements or bug fixes. I had a lot of talks with people who gave really helpful feedback about the project I'm currently working on.

You have been working on accessibility for the blind ... how did you get into this subject
I was pointed to an analysis report concerning accessibility in Wikipedia that was carried out by the Swiss initiative "Access for all". While reading this I realized that a lot of the mentioned issues were
quite easy to solve. A lot of the content available on the web seems to be designed without considering accessibility aspects, although a little tweak can always have a high impact.

How do you know what to focus on
The analysis report was quite thorough and included recommendations, so it ended up to be something like a task list.

You identified a number of issues to work on this weekend .. how did it go
The issues I was working on were quite easy to fix, whenever I had problems with something there was always somebody around to help out.

Did having all these other hackers make a difference ?
The gathering of all those experienced MediaWiki developers is a really helpful thing. That applies to having certain questions answered rightaway as well as just sharing experience in whatever topic might
come up.

Brion Vibber helped you with the parser tests ...
Brion figured out what the problems was in no time. There has been a language version related bug in another patch which he simply reverted.

Are there many more accessibility issues in MediaWiki people can help with
The accessibility analysis report mentions more issues that need to be fixed to make Wikipedia and all other projects based on MediaWiki more accessible. It is clearly written and points out lacks of accessibility very

How do you continually test for good accessibility of our software
Most of the time one seldomly notices lacks of accessibility when not being affected by disabilities. Whatever issue I fixed for improving accessibility I have to keep in mind to apply that again in a similar case.

Are there best practices for coding for accessibility
There are guidelines defined by the WAI, which should be considered when coding for accessibility.

Do you have thoughts on what the Visual Editor will do for accessibility ?
Since screen readers will read what is written on the screen it also reads the wikitext as is. That might be hard to understand, especially for newcomers. Reading out a headline as a headline instead of
"equals-equals-headline-equals-equals" can be very helpful to focus on the subject itself.
 --- Kai

Friday, June 01, 2012

#WMDEVDAYS - Redlinks in any language

In #Wikipedia, when you consider Berlin, the capitol of Germany is not the only Berlin in existence. Currently there are 205 Wikipedia articles about the German capitol with an interwiki link and as there are 285 Wikipedias, there are 80 articles either missing or they do not have a link.

For Berlin Connecticut, there are 10 Wikipedia articles. It is likely that the Berlin part is written exactly the same as the German Berlin. It follows that a label for both Berlins is exactly the same. There are many more cities called Berlin in the United States of America...

When a label with a description has been added to Wikidata, it means that the existence of a subject has been registered for that language. As a consequence Wikidata knows it has to disambiguate Berlin. It knows that it can show attributes stored for the subject in Wikidata like the seal shown here to the right. This may even be further refined by showing the attributes using the same template as used on the English Wikipedia.

What we do know for Berlin Connecticut is in what 10 languages we have an article. When one of those languages is a language you understand, you may even want to read it ...
Thanks,
      GerardM

#WMDEVDAYS - Using #Commons

Commons works best when you use known pictures. As it says on Commons, it is "a database of 12,959,488 freely usable media files to which anyone can contribute".  Anyone can and, it is becoming ever easier to contribute even more media files. The problem is not so much contributing files, it is finding them and using them. Many people I know prefer to find pictures elsewhere. I tried to find pictures of a bunch of keys on Commons for a recent blog post but after too many pictures of Alicia Keys, I gave up.

At the Berlin Hackathon 2012, it is the kind of thing that merits some shared consideration. The existing categories on Commons just do not help. When looking for keys, you want to choose from all keys and not navigate a structure. It makes more sense to have tags and possibly disambiguate those tags. Combine them with other tags and you have a result that will be more satisfying.

The value of a collection is in its use. 
Thanks,
     GerardM

#WMDEVDAYS - Single signon

One of the #Wikidata presentations posed a question: "We need a much improved single signon". For Wikidata it is important to be able to edit Wikidata itself while working at the same time on a Wikidata client. The presenter wanted to understand if this is an issue that needs to be addressed soon.

When you will be using Wikidata on one of the Wikimedia projects, you will typically use one user on all projects. This user is authenticated once when he signs on with his global user account and, this authentication serves him well when he works on other projects.

This will work well for Wikidata. The only issue left is that they also want to be usable and editable for users who use Wikidata from their own server. This however is an issue that they do not have to solve immediately.

There is existing functionality like OpenID that may provide a solution for this. It is great that the Wikidata people consider how the data can be used from outside the Wikimedia Foundation. It is wonderful that they provide a use case that makes a case for implementing OpenID.
Thanks,
     GerardM

Tuesday, April 03, 2012

#Chennai hackathon IV

Several of the Chennai hackathon projects were interesting because of the different approach they took to known problems. A hackathon is a perfect place to experiment; there are many people around and they often have their own ideas about how things should be done.

Wikiquotes via SMS
You send the name of a person and in reply you get quotes from that person. The idea makes sense but the problem is that the quotes in Wikiquote are not available in a structured way. When quotes are individually tagged, an application to send SMS messages becomes possible from the source. The approach of this project was to copy quotes into a database and use this.

When the Wikiquote communities start using templates for each quote, it will become possible to use Wikiquote itself.

Translation of Gadgets/UserScripts to tawiki
There is no doubt, the translation or localisation of software makes a hell of a difference to the usability of software. The standard approach is to localise at translatewiki.net but gadgets and user scripts are not yet supported in this way.
It is wonderful to learn that the ProvIt and the TwoColumn gadget are now available in Tamil. The challenge left is how to make them available in other languages and how to maintain them when the code needs changing.

Lightweight offline Wiki reader
Even though there are several off line readers like OkaWix and Kiwix, it was the considered opinion that there is room for another one, a reader that can be used when there is only a little room available. The Qvido project was revived at this hackathon and is now available with "build" instructions.

Open source projects exist as long as there is an interest in developing a project and as long as there are people who benefit from it. Being able to host MediaWiki content off line as widely as possible is certainly reason enough for this project to get attention.

Program to help record pronunciations for words in tawikt
When you learn a foreign language it is really hard to get the pronunciation of words right. A program that allows the recording of some 500 words in half an hour is really useful. However, getting it uploaded to Commons is equally important because this can be an enormous time-sink and this is one part of the puzzle that still needs solving.


WikiPronouncer
Another approach to recording pronunciations was to do this on an Android phone. Developing an app in a day is too much of a challenge.. What these two projects make clear is how much pronunciations is a feature that is very much in demand.

As soundfiles are used extensively on other wiktionaries, it does make sense to learn the best practices elsewhere. The least they need is a Tamil makeover eh, a localisation.
Thanks,
       Gerard

Saturday, March 31, 2012

#Chennai hackathon III

The biggest challenge after a #hackathon is probably to keep the hackers engaged. When they know that their effort is appreciated, they are more likely to remain involved in our projects.

One of the projects of the Chennai hackathon is the "Random Good WP India article tool" and it is really nice to learn that the tool is now available for your use. Have a look and see if a tool like this is something for your wiki.

If there is enough interest, a tool like this can become available for the projects in the Wikis themselves.
Thanks,
     GerardM

Friday, March 30, 2012

#Chennai Hackathon II

Several of the topics at the Chennai hackathon had to do with the manipulation of data.

Word lists
One project searched for a list of unique words in the Tamil Wikipedia. They used a dump and retrieved an initial list of 1.3 million unique words. Such a list is quite useful; once the list is filtered from words in other languages and other problematic strings. It can be used to build spell checkers, it can even be the basis for research into building a more effective "transliteration input method".  Currently the phonetic typing for Tamil is considered inefficient since it takes too many keystrokes for same text as opposed to the Tamil99 keyboard layout. It takes a big corpus to find the patterns that are more effective.

A project like this may be beneficial for other languages as well. Wikipedia often represents one of the largest corpora of the modern use of a language. Once this project is documented and when there is a set-up to run it repeatedly, it will stimulate the development of more applicable language technology.

Structured database search over Wikipedia
This project is vintage hacking; learning how to use semantic search using DBpedia and ending up with Wikipedia content is great stuff. The hackathon report has this to say:  "Amazing search tool that made it super easy to query information in a natural way". That makes it really interesting to have it hosted somewhere so that people can comment and experience the semantic web first hand.

Parsing Movie data into a database
Wikipedia is rich in information about movies. They typically include info boxes and when you extract everything Wikipedia has to offer together in a database, it becomes really awesome. It can be the beginning of an "IMDB" for the movies from India for instance. 

As this is also the approach taken by DBpedia, the skills learned can be applied to for instance the Tamil Wikipedia. Once a language is supported in DBpedia, it has a prominent entry in the Semantic web.

Random Good WP India article tool
Spreading the word about great articles about India is one way of enthusing people to write some more. Technically it may not be that hard but when you start without any knowledge of the MediaWiki API or JSON, it is quite a feat when a working prototype is produced in a day.

A tool like this can be used on any Wiki and by any project that wants to show of its quality content. You never know how pushing great contents will pull in more interest for our projects.
Thanks,
      GerardM

#Chennai Hackathon


The Chennai hackathon has come and gone. There has been a report on the India mailing list. It is a wonderful report, many people who should be interested will not read it because they are not subscribed to it.

The projects people worked on were very diverse:

  • Wikiquotes via SMS - @MadhuVishy and @YesKarthik
  • API to Rotate Images (Mediawiki Core Patch) - Vivek
  • Find list of unique Tamil words in tawiki - Shrinivasan T
  • Program to help record pronunciations for words in tawikt
  • Translation of Gadgets/UserScripts to tawiki - SuryaPrakash [[:ta:பயனர்:Surya_Prakash.S.A.]]
  • Structured database search over Wikipedia - Ashwanth
  • Photo upload to commons by Email - Ganesh
  • Lightweight offline Wiki reader - Feroze
  • Patches to AssessmentBar - gsathya
  • Parsing Movie data into a database - Arunmozhi (Tecoholic) and Lavanya
  • Random Good WP India article tool - Shakti and Sharath
  • Fix bugs on tawiki ShortURL gadget - Bharath
  • Add 'My Uploads' to top bar along with My Contributions, etc - SrikanthLogic
  • WikiPronouncer for Android -  Russel Nickson
  • Wiktionary cross lingual statistics - PranavRC
Most of these projects deserve attention of a larger public. They represent missing functionality or they have a different approach to something we are struggling with. They are all by people who have a keen interest in the projects of the Wikimedia Foundation and as such they represent our "latest generation". 

There is too much great stuff in this list to single out in this blog post. Then again, there is always the next blog post.
Thanks,
      GerardM

Wednesday, November 23, 2011

Narayam will look like this

The #India hackathon produced excellent results; one of the highlights was the online keyboard for Narayam. It will need some modifications but it at least allows you to SEE where these bleeding keys are on an International keyboard.

The day after the hackathon we tried to install the patch only to find that some files were sadly lacking. The good news is that after a few e-mails there is not only a screenshot but the missing files are now available to us as well. A big thank you to Abhijeet Pathak for his contribution and his kind support.
Thanks,
     GerardM