Showing posts with label Open Source. Show all posts
Showing posts with label Open Source. Show all posts
Tuesday, February 04, 2014
#Timelines - not invented here and, it is good
The best #software is used. The new timelines in #Reasonator are available and, it is wonderful. It is yet another way of showing of the data that exists in Wikidata. It is also one area where more data will lead to more interesting information.
This timeline software by the knight lab is open source and, even though it is great, there is room to make it even better. Just try it in Arabic. You would expect the data to go from left to right. It makes sense because the labels do show up in Arabic in the timeline.
What makes this implementation so nice is that all kinds of information relating to a person are included. The Reasonator reasons; it includes even the dates children are born.
Thanks,
GerardM
Wednesday, November 14, 2012
A #font for people with #dyslexia II
The good news is: the Open-Dyslexic font will be part of the initial roll out of the "universal language selector". The font is already available for some 25 languages on Wikidata and translatewiki.net where the "universal language selector" is already deployed. These languages are listed below.
- en - English,
- af - Afrikaans
- ca - Catalan
- cy - Welsh
- da - Danish
- de - German
- es - Spanish
- et - Estonian
- fi - Finnish
- fo - Faerours
- fr - French
- ga - Irish
- gd - Scottish Gaelic
- hu - Hungarian
- is - Icelandic
- it - Italian
- lb - Luxembourgisch
- mi - Maori
- ms - Malay
- oc - Occitan
- pt - Portuguese
- sq - Albanian
- sv - Swedish
- sw - Swahili
- tr - Turkish
- wa - Walonian
When you consider that languages with special characters like Icelandic and French are in this list it is obvious that many more languages are already supported by this font. When you consider that the WMF has good relations with the creator of the font it is more than likely that missing characters for your language can be added to the font.
So check out first if all the characters used in your language are supported by the Open-Dyslexic font. If it is, ask for it to be enabled either by making the request on the support page of translatewiki.net or by requesting them on bugzilla. You can also send a mail with this happy news to all the teachers you know. When it is not, identify the missing characters and, ask nicely for them to be added.
Open Source is such a wonderful enabler. Consider; not only is this font available to all the teachers and the sufferers of dyslexia, it is also available for use on websites like Wikipedia. Given that our aim is to share in the sum of all knowledge this is an important step in the right direction.
Open Source is such a wonderful enabler. Consider; not only is this font available to all the teachers and the sufferers of dyslexia, it is also available for use on websites like Wikipedia. Given that our aim is to share in the sum of all knowledge this is an important step in the right direction.
Thanks,
GerardM
Tuesday, May 15, 2012
Legacy projects II
When tools are no longer maintained, when they are no longer promoted, they die. The good news is that the tools created for the Myanmar language created by Keith Stribley have found a new home.
The question is to what extend are they salvageable and is it worth the effort. For software there are two primary considerations; copyright and licensing and, the source code.
Without source code the first question is less relevant and, the reference to the mercurial repositories is a reference to Keith's old website. This old website is gone. There are references to the CC-by-sa license on some pages but for software such a license is not really appropriate.
When you look at the subjects Keith covered, they are still very much relevant and impressive. At the Myanmar Wikipedia two out of three webfonts do not work for me. We do not have an input method yet. It will be great when we find that the tools Keith created can find another use.
The result of my previous post is this update. I hope that there will be a future update to this post bringing you more positive news.
Thanks,
GerardM
The question is to what extend are they salvageable and is it worth the effort. For software there are two primary considerations; copyright and licensing and, the source code.
Without source code the first question is less relevant and, the reference to the mercurial repositories is a reference to Keith's old website. This old website is gone. There are references to the CC-by-sa license on some pages but for software such a license is not really appropriate.
When you look at the subjects Keith covered, they are still very much relevant and impressive. At the Myanmar Wikipedia two out of three webfonts do not work for me. We do not have an input method yet. It will be great when we find that the tools Keith created can find another use.
The result of my previous post is this update. I hope that there will be a future update to this post bringing you more positive news.
Thanks,
GerardM
Monday, May 14, 2012
Legacy projects
Last year, I reported the death of Keith Stribley. Keith was well known for the support he provided for the Myanmar language. Keith used his own website where people could download the tools that he had written.
Today, I tried to visit his website. It was gone. I googled for some of his projects, I did not find them. It is truly sad when there is little to find of the good and relevant work that Keith did.
I am sure that Keith's projects are not the only relevant projects that came to an all too abrupt halt. I can only hope that someone will prove me wrong with regards to Keith's projects.
Thanks,
GerardM
Today, I tried to visit his website. It was gone. I googled for some of his projects, I did not find them. It is truly sad when there is little to find of the good and relevant work that Keith did.
I am sure that Keith's projects are not the only relevant projects that came to an all too abrupt halt. I can only hope that someone will prove me wrong with regards to Keith's projects.
Thanks,
GerardM
Tuesday, March 13, 2012
#Wikimedia #Mobile Frontend is opening up
The mobile frontend of #Wikipedia achieved 9.5% of the total traffic. It is growing rapidly. Having a strategy to support your wiki on mobile platforms is really important. There was a bit of good news on the Wikitech mailing list:
Thanks,
GerardM
[Wikitech-l] First steps at making MobileFron tend usable beyond the WMF infrastruc ture
Over the last couple of weeks, I've taken a few steps to remove some of theWMF-specific bits of the MobileFrontend code base:https://bugzilla.wikimedia.org/show_bug.cgi?id=34144https://bugzilla.wikimedia. org/show_bug.cgi?id=34145
Also, now if you view an article with "useformat=mobile" in the URL's querystring, MobileFrontend will keep the mobile view enabled as you browse pageto page until you explicitly exit the mobile view.
While MobileFrontend has now been generalized enough to be used beyond theWMF cluster, there are still quit a few things that could be done toimprove the ease of out-of-the-box usage. For instance, adding configurableWURFL support (which I believe should be fairly straightforward - this isout of date but the same idea should still work:http://lists.wikimedia.org/pipermail/wikitech-l/2012- January/057478.html)or making it possible to use path-based modifiers to signify mobile view(eg http://mywiki.com/wiki/Article -> http://mywiki.com/wiki/m/ Article -https://bugzilla.wikimedia. org/show_bug.cgi?id=35178).
It would be great if anyone can help test/provide feedback for the changesthat have been made, and especially if anyone wants to help add thefeatures mentioned above!There are many organisations large and small who use MediaWiki. Many of them stand to gain a lot of traffic with out of the box support for mobile devices. The great thing of this effort is that the MobileFrontend will be supported in the next releases; it is what the WMF uses itself.
Thanks,
GerardM
Monday, May 02, 2011
What is technically wrong with the #Wikia #WYSIWYG
The question was precise and, it was asked by Tim Starling.. Technically means that Tim is asking for bugs, performance issues things that are technical in nature.
Both the Wikia software and the Wikimedia Foundation software are open source and this allows for the use of the Wikia software by the Wikimedia Foundation.
Tim's question is timely as well as opportune: Brion is back and he is tasked with revamping the parser and implementing WYSIWYG for MediaWiki. It would be stupid to develop something new when there is already something that is already adequate.
There are important advantages:
Thanks,
GerardM
Both the Wikia software and the Wikimedia Foundation software are open source and this allows for the use of the Wikia software by the Wikimedia Foundation.
Tim's question is timely as well as opportune: Brion is back and he is tasked with revamping the parser and implementing WYSIWYG for MediaWiki. It would be stupid to develop something new when there is already something that is already adequate.
There are important advantages:
- the software is already in production at Wikia
- the software is being localised at translatewiki.net
- this is experience how WYSIWYG affects MediaWiki newbies and oldies alike
Thanks,
GerardM
Friday, April 15, 2011
A #Toolserver heaven
When God created his first code, he created it in his image. He put in his own repository, called it Open Source, announced it to the world and walked away to do another creation.
Many of the Toolserver tools are abandon ware. They have been thankfully received by the mere mortals who pay daily homage to the Gods by evoking the code in a quest for reaching the heaven of enhanced and divine effectiveness.
As more mere mortals scaled the heights of tool proficiency, their understanding became fractured as more of them started to talk in different tongues. The code lived on and everyone was still expected to continue building the tower that brings knowledge to all of humankind.
The Gods did send their sons to update much of the code; even though the code was in many books, the revelations could be extracted into a single source that would be delivered to the mere mortals. As these new levels of understanding descended on the faithful, the code itself remained a testament to the original structures and coding practices.
The promise of new coding practices descended on the disciples, they theorised and promised an afterlife where all the code will work to its full potential. Code enshrined for all to see and improve upon.
Thanks,
GerardM
Thursday, May 20, 2010
#iPad, iDodo and #Android
First there were e-readers, they were closed but cheap and did one thing well. Then there was the iPad it did took over the attention from the e-readers and is a closed, expensive but more capable tool.
Adroid is different, its website talks about "what is new". You are expected to know that it is an operating system for ... eh ... Its logo is available under a CC-by license ...This operating system is available to any manufacturer and Android phones outsell the iPhone.
Understanding the i-thingies is easy because there is little to choose from. There is only one supplier. Choosing for Android is easy but then you still have to choose the hardware that serves your need best.
I have not really been paying attention.. is there already something sizeable running Android that competes with the iPad ?? Who is manufacturing it, who is selling it in my market ? Do I have to wait like Apple has me wait ??
Did I say that it is your choice what you do with your Android, did I say that it is open source, did I say choice.. your choice?
Thanks,
GerardM
Adroid is different, its website talks about "what is new". You are expected to know that it is an operating system for ... eh ... Its logo is available under a CC-by license ...This operating system is available to any manufacturer and Android phones outsell the iPhone.
Understanding the i-thingies is easy because there is little to choose from. There is only one supplier. Choosing for Android is easy but then you still have to choose the hardware that serves your need best.
I have not really been paying attention.. is there already something sizeable running Android that competes with the iPad ?? Who is manufacturing it, who is selling it in my market ? Do I have to wait like Apple has me wait ??
Did I say that it is your choice what you do with your Android, did I say that it is open source, did I say choice.. your choice?
Thanks,
GerardM
Monday, April 19, 2010
#StatusNet is nice, it is getting awesome
When you consider your own microblogging service, you want to know what StatusNet already provides and, what it is working on. When you want to experience the functionality first hand, identi.ca is the place to be.
So what is on offer;
Thanks,
GerardM
So what is on offer;
- your server does not suffer from the Twitter fail whale
- the software is available under the GNU Affero General Public License
- consequently interoperability will not be revoked because of corporate interests
- #sntrans is the identi.ca group with status updates for the localisation
- StatusNet has excellent localisation in 14 languages. Decent #L10n in another 15 languages
- the core software is localised at translatewiki.net and, you are welcome to make a difference for your langugage ...
- Bi-directional text support is being tested !!
- preparations are made to localise extensions as well
Thanks,
GerardM
Wednesday, December 19, 2007
WOSI, a really cool Open Source/Standards project
WOSI is a project of a Dutch school, the HVA, working on a software environment for "woningcorporaties". A woningcorporatie is an organisation that is involved in public housing. As an organisation they are genuinely capital intensive, their IT requirements are complex and evolving.
The objective of the school is to provide an environment for their students that will give them a real feel for what it is like to work in the ICT business and teach them Open Source and Open Standards. Students that are part of this project will experience that a project does not start from scratch, there is always something to build upon, there are always conflicting requirements, there is always the need to ensure interoperability because the use of Open Standards is a precondition.
The WOSI project is in its second year and, it is growing in size. Students from other disciplines are getting involved as there is overlap with other specialties like communications and marketing. More woningbouwcorporaties are interested in the project as well as other schools. The great thing is that as Open Source and Open Standards are key to this curriculum, professionals will be released to the job market that know how to apply these notions in real world scenarios. This is likely to prove the biggest boon to this really cool project.
Thanks,
GerardM
The objective of the school is to provide an environment for their students that will give them a real feel for what it is like to work in the ICT business and teach them Open Source and Open Standards. Students that are part of this project will experience that a project does not start from scratch, there is always something to build upon, there are always conflicting requirements, there is always the need to ensure interoperability because the use of Open Standards is a precondition.
The WOSI project is in its second year and, it is growing in size. Students from other disciplines are getting involved as there is overlap with other specialties like communications and marketing. More woningbouwcorporaties are interested in the project as well as other schools. The great thing is that as Open Source and Open Standards are key to this curriculum, professionals will be released to the job market that know how to apply these notions in real world scenarios. This is likely to prove the biggest boon to this really cool project.
Thanks,
GerardM
Subscribe to:
Posts (Atom)








