Would India be interested? How do we put forth our interest? I'll be happy
---------- Forwarded message ----------
From: Tomasz Kozłowski <odder.wiki(a)gmail.com>
Subject: [Foundation-l] Wiki Loves Monuments 2012 -- global?
To: Wikimedia Foundation Mailing List <foundation-l(a)lists.wikimedia.org>
As you may have heard, a little while ago some organizers of Wiki Loves
Monuments 2011 came together in a rainy and cold Amsterdam to evaluate
the 2011 edition, and kick off documentation for 2012. We would like to
share some of the results of our meeting with you.
The first and most important information is:
* There is going to be a Wiki Loves Monuments in 2012 -- and if there is
interest, we are going global!
We would like to get a feeling of in how many countries there would be
people potentially interested in organizing a Wiki Loves Monuments
nationally; but firstly, let us start with the basics.
Wiki Loves Monuments is a photo contest organized in 2010 and 2011 in,
respectively, the Netherlands and in Europe. The contest asks the
general audience to upload pictures of monumental/historical sites and
buildings during September. It has a federal structure and is organised
separately in every participating country by the local people who know
how things work in their area; best photos from all countries are
nominated for an international contest.
In 2011 this contest was very successful, with more than 165.000 photos
of monuments in 18 participating countries submitted in total. This was
possible thanks to the hard work of hundreds of volunteers in those
countries who helped organise Wiki Loves Monuments in one way or
another. The winning pictures have been published on
<http://www.wikilovesmonuments.eu> and on Wikimedia Commons:
Besides the wonderful direct impact on the overall quality and coverage
of heritage and culture topics, Wiki Loves Monuments is a fantastic
opportunity to reach some of our important goals: we had a participation
of over 4.000 new users who created the first ever community-driven
contribution peak on Wikimedia Commons
have also helped in establishing cooperation between Wikimedia groups &
chapters and some of their local cultural institutions and organisations
in several countries.
Would you be interested in organizing a Wiki Loves Monuments in 2012 in
your country? Would you like to know more? Find all the details at
We have put together some information there for you -- and much more
will follow soon.
We would also like you to join our public mailing list where everyone is
welcome to ask any questions about the details on how to organise a Wiki
Loves Monuments in your country. This is a place where many organizers
of 2011 are already on and we will use that as our main channel for
communications and information dispersion in 2012. Be bold and sign up
for the list at
So, please speak up if you're interested!
Lodewijk, Maarten & Tomasz (on behalf of so many others)
foundation-l mailing list
How Pradeep uses email - http://goo.gl/6v1I9
Heya all. I just wanted to share this quick mail with you and get your
feedback. Over the past two years, I've actively been part of Wiki
outreach efforts. Thru meetups, volunteering for the Bangalore
Samskrit academy, trying to convince friends, classmates etc. I've had
a lot of negative experiences with people askin me- What's in it for
me? Mere liye kya hai? Ennaku enna kadaka porthu? I get laughed at
when I say I'm doing gu voluntarily. Infact recently, when I tried to
get a friend to contribute to our
Sathyamangalam-Gobichettipalayam Star Gazers Gang, Ukkadam, Coimbatore.
My Commons uploads, now exceeding 75.
We've added interwiki links to this release. Indic rendering support
on Android is pretty awful (or non-existant) but do give it a try
---------- Forwarded message ----------
From: Tomasz Finc <tfinc(a)wikimedia.org>
Date: Mon, Dec 19, 2011 at 2:50 PM
Subject: [WikimediaMobile] Second release candidate of Wikipedia Android app
To: mobile-l <mobile-l(a)lists.wikimedia.org>
After a furiously paced week I'm happy to release RC2 of the Wikipedia
Android application. Brion and Yuvi did a lot of stability cleanup,
caching fixes, and in general magician work to get this closer to
market release. Note that we've also changed 'bookmarks' to 'saved
pages'. Were pushing fast to get this ready to launch by January
For those that just want to get going
You can also find it attached to this email.
As before we need you to test this extensively and file bugs under
Key points to test (mostly same as before)
* Browse as you would normally do on WIFI, 2G, 3G, & no connectivity
* Save an article that your on and then load it as a saved page.
Delete that saved page.
** Go into airplane mode and load the saved article. Follow a link <== new
* Open your browsing history and load a previous page
* Tap 'near me' and browse articles. Move the map and tap 'redo search
in this area'
* Share a link with someone on twitter or facebook
* Changing your language preference in the Settings menu
* Use a phone that is in a non US local to test other languages like
Hebrew, Japanese, Arabic, etc
* .. and whatever else you may want try out
Items fixed or updated since RC1
* Updated Wikipedia App icon
* Remove 'example checkbox' from settings dialog before release
* Android back button troubles (history vs bookmarks?)
* Text in search box remains as you typed it even if you select
another search suggestion or move on to another page
* Add inter-wiki language links
* Flash of Unstyled Content when loading bookmarks in Android App
* Android bookmarks list should show most recent at top
* Links from bookmarked page sometimes open in full screen
* Wikipedia Android app uses internal path when sharing offline links
* Wikipedia Android app saves wrong article when on 'San Francisco'
* Offline page is now styled
* Search box doesn't always highlight
* Saving pages can be slow
Feedback page is still here @
As before there are bound to be bugs but don't think that someone will
file them for you. If you don't file it then chances are that we wont
know its an issue. If your not sure of wether its a bug or not then
come join us on #wikimedia-mobile (freenode) and we'll sort it out.
Mobile-l mailing list
Yuvi Panda T
Welcome YuviPanda! :)
---------- Forwarded message ----------
From: Tomasz Finc <tfinc(a)wikimedia.org>
Date: Mon, Dec 19, 2011 at 13:58
Subject: [Wikitech-l] Please Welcome Yuvaraj Pandian & Max Semink
To: wmfall(a)lists.wikimedia.org, Wikimedia developers <
The Mobile and Special Projects department is pleased to announce the
addition of two new contractors to the team: Yuvaraj Pandian and Max
Yuvaraj Pandian or Yuvi as we gotten to know him was one of our 2011
Google Summer of Code students. During GSoC he worked with Arthur
Richards on porting the Wikipedia 1.0 bot to a PHP extension named
Selection Sifter. This was in important offline project as it allowed
us to better support and extend our offline tool chains. Previous to
this he had been active in the busroutes.in community where users
@logic and @planemad motivated him to come on and help the Wikimedia
community. One of his early Wikimedia project memories includes the
tawiki community discussing the ShortUrl extension. He found the
entire channel so lively and helpful that he applied for GSoC.
Yuvi will be working for us remotely while on a six month sabbatical
from KCG College of Technology, India. He'll be extending the Android
app, enhancing MobileFrontend, and working with our various offline
efforts to further the reach of the projects. You can find him on irc
under the nick 'yuviapanda' .
Max Semink has been an active MediaWiki contributor since 2009. He's
recently been most involved in developing the API Sandbox for
MediaWiki. An extension that allows any user to easily create complex
API queries through a visual interface. When not hacking on MediaWiki,
Max has been busy developing C++ software for embedded systems in the
railroad industry. While train switching has captured the majority of
his recent developer cycles, he's super eager to change direction and
focus his full time efforts on MediaWiki.
Max will be continuing his interest in the API by helping us improve
and extend its use within mobile. He'll be adding a proper API to
MobileFrontend, extending support for GPS, and in general moving the
API forward for our mobile clients. Max will be working for us
remotely and can be found under the nick 'MaxSem' .
It's great to be able to see two active community members be able to
join us full time.
Please join me in (re)-welcoming Yuvi and Max!
Wikitech-l mailing list
Pardon my intrusion on this thread, but within reason*, if any college or
other educational institution chooses to be 'proprietary only' (never mind
antediluvian - IE6? really? or is that an XP issue?) FOSSers are prepared
to take it up 'officially' with them, reminding them of the nation's
commitment to education without strings attached. This is fyi to listers,
and I shan't mention it again, but please do consider notifying your
friendly neighbourhood FOSSer with details of the person to contact
(principal/director etc) for assistance and action. This in turn will get
reflected to a FOSS forum (fosscomm is one such) and will hopefully result
in notifying the institution concerned as well as the possibility of a
local FOSS-based firm offering upgrade services.
*ie FOSS as a movement is in continuous need of resources as well, but
education is a major priority
On Tue, Dec 13, 2011 at 9:44 PM, Srikanth Ramakrishnan <
> Also forgot to tell you. My college uses ONLY systems with Windows XP
> and Internet Explorer 6. Most students are from a Tamil background,
> and they read Tamil websites, Wikipedia very often.
> On 12/13/11, Srikanth Lakshmanan <srik.lak(a)gmail.com> wrote:
> > Hi all,
> > Pardon for a long mail, just unavoidable.
> > We have seen the WebFonts roll out last night to most Indic wikis
> > Malayalam and Tamil. We in Tamil Community felt WebFonts extension is
> > not ready for us. We would like to share on why we in Tamil community
> > chose webfonts and also what could work better in future for Indic
> > communities during technology adoption.
> > 1. *Unavailability of "Quality Free fonts"* :-
> > During the development, our request for not setting the default font as a
> > lower quality font was rejected citing "it will defeat the purpose of
> > extension". The available fonts had issues and deploying the extension
> > with those low quality fonts to everyone would not only defeat the
> > of extension, but also gives Tamil Wikipedia a bad image when people just
> > cant read the fonts even though they had better fonts in system. (Just
> > how i18n team says people who see boxes will just simply close the
> > we say giving these poor fonts will also lead to same thing and not help
> > the cause, instead will also hurt those who have better fonts.).
> > 2. *Quality of User Experience* :-
> > We are a smaller wiki, we have a smaller reader base, but still we are
> > ranked 7th most visited website in Tamil according to alexa. Just like
> > how no-nonsense / no-mediocrity is tolerated in any code that enters WMF
> > cluster, any change which will affect the site's look and feel, user
> > experience will have to be of highest standards and must be accepted by
> > community. WebFonts were just not ready to enter Wikipedia, since it
> > changes the UX for all the readers to help a potentially lower number of
> > users who dont have Tamil fonts than the current existing reader base.
> > *What we feel was wrong in WebFonts deployment*
> > We have also been seeing the wikis where they have been rolled out and
> > reporting issues. We ourselves are reporting issues inspite of not taking
> > WebFonts, with the hope software just gets better and some day we can
> > deploy them. Dont get us wrong, we are not against technology, we just
> > it in better form and are not in any urgency. (After all we at Ta wiki
> > initiated an RFC and asked Webfonts even before the announcement was
> > We would also like to mention some points which we feel i18n team could
> > have done better for a smoother launch.
> > 1. *Font Testing* :-
> > The point of language support team is that the people who are aware of
> > language give feedback to make any software better supported for the
> > language. We are not sure if Font-Testing was ever done at all for those
> > languages where the WebFonts were deployed. The hinting issue which was a
> > concern and made us raise against deployment in Tamil is also present in
> > Hindi,Sanskrit,Telugu(atleast till we saw) and gave the same worst
> > readability. The i18n team did font assessment, testing only 1 word to
> > test the font. Can any font be tested with just rendering of 4
> characters /
> > 1 word? For Tamil,we did a test in little more comprehensive way(We would
> > not say its complete). This should have been a *must* to see
> rendering /
> > font issues with chosen default font especially since the fonts are being
> > set default to every single user to the site. Sadly community was
> > the least, a note was posted in Village pumps and we dont think community
> > involved itself in any testing and poor quality was eventually pushed
> > without proper testing.
> > 2. *Real world testing* :-
> > Though cross browser testing was done, there was a severe lack of real
> > world testing and as a result we are seeing a host of issues being
> > discovered post launch. Average PC in India might have 1 GB RAM, Firefox
> > / 4, worse IE 5.5 / IE6 on 100 Kbps semi-broadband connection. We cannot
> > tell them move to latest or ignore them. More care should have been taken
> > especially since the webfonts is bound to set a default font.
> > With only a few hours of testing serious issues have been found - in IE
> > where webfonts might be rolled back , IE 7.0 (where webfonts dont
> >  , ubuntu + Firefox (fixed now)  and Win+Firefox 5.0, . We are
> > still testing for other browsers and usecases and dont know how many
> > we will discover. In short - This code is not ready to go live,
> > when it is being made default compulsorily for everyone. There are
> > performance issues for typical Indian internet connections as well.
> > 3. *Communication and Community Engagement* :-
> > Most of the above things could have solved earlier if there was more
> > communication and community engagement. We asked for more information,
> > engagement on this very list. There was no reply to the mail on
> > community engagement for i18n projects. Most communities know
> > is coming on Dec 12, didnt know what was coming, any further details.
> > Worse, Even Indic Consultant was not having clear information. Why this
> > lack of transparency? Community is more than willing to help, if only
> > are informed. Even though we did not take up WebFonts, we have spent time
> > to help making it better.
> > And the end users in the wikis dont know where to report and follow up
> > issues. (Not everyone is aware of and familiar with the Bugzilla
> > The request we raised to have a visible bug reporting link has not been
> > acted upon . There might be a lot of issues going unreported, because
> > people dont know whom to report to. When a change of this scale is being
> > done, Community admins must be advised to run Sitenotice campaigns to
> > inform the users about the change with some solid newbie oriented
> > documentation. Infact this must be done for RFC itself, so as to make an
> > informed decision. We did the same for RFC in Tamil.
> > *Proposal for Future i18n / any special deployments to Indic
> > The WebFonts deployment is a classic example of making deployment without
> > enough community engagement. Can this done in any of English / German /
> > Russian wikipedia which have a strong community? The fact that Tamil /
> > Malayalam resisted was because the community had concerns over the
> > solution. Till an hour before deployment yesterday, we did not know if Ta
> > wiki projects will get webfonts despite our objections. We had been
> > pursuing Siebrand and Gerard across forums - facebook, twitter, meta talk
> > pages, village pumps, gmail chat etc looking for answers. But till the
> > deployment happened, we had no clue what we would be getting. This method
> > of deploying in silence *must* stop ASAP. Any deployment to any Indic
> > must go through the community (language support teams) informed of the
> > change with Indic Consultant kept in loop. We suggest Shiju Alex to work
> > a policy and put it in place regarding this. If there is problem
> > identifying community members to help, we are sure Shiju will help
> > connecting.
> > Irrespective of that happening Tamil Wiki Projects will follow this
> > 1. Test any deployment on translatewiki
> > 2. File Bugs and verify in translatewiki till it reaches acceptable
> > 3. Language support team member will make a RFC page explaining the
> > / demerits of the technology in simple terms with use of screenshots /
> > external links
> > 4. Reverify / Ask for deployment in largely-inactive Wikiprojects like
> > WikiQuote / WikiBooks *post community concensus*
> > 5. Test again / File Bugs
> > 6. Reverify / Ask for deployment Wikiprojects next in line in terms of
> > activity ( Wiktionary / Wikinews/ Wikisource)
> > 7. Test again / File Bugs
> > 8. Only after ironing out all issues, any deployment will be allowed in
> > Tamil Wikipedia.
> > We had burnt our fingers during Narayam deployment already once and
> > community was so resistive of Narayam itself and was asking to go back to
> > bringing back Narayam on all Tamil Wikiprojects.
> > We suggest the other communities adopt something similar. We sincerely
> > that the community engagement is improved, not just before deployment,
> > from start of development.
> >  http://blog.wikimedia.org/2011/12/12/going-live-december-12-2011/
> >  https://bugzilla.wikimedia.org/30506
> >  http://www.alexa.com/topsites/category/Top/World/Tamil
> >  http://translatewiki.net/wiki/WebFonts_assessment
> >  http://translatewiki.net/wiki/User:Sodabottle/test1
> >  https://bugzilla.wikimedia.org/32775
> >  https://bugzilla.wikimedia.org/33024
> >  https://bugzilla.wikimedia.org/33025
> >  https://bugzilla.wikimedia.org/33018
> >  https://bugzilla.wikimedia.org/33027
> > 
> >  https://bugzilla.wikimedia.org/32942
> >  http://tawp.in/r/2r1f
> > --
> > Regards
> > Bala Jeyaraman & Srikanth.L
> Srikanth Ramakrishnan.
> Wikipedia Coimbatore Meetup on December 10th.
> Wikimediaindia-l mailing list
> To unsubscribe from the list / change mailing preferences visit
Fool On The Hill <http://communicall.wordpress.com>
[Was: Webfonts deployment on Indic Wikiprojects]
2011/12/14 Pradeep Mohandas <pradeep.mohandas(a)gmail.com>:
> Curious: Is anybody testing this for mobile web?
I am doing my best to test it in any mobile phone and tablet upon
which i come up, but we cannot systematically cover all the possible
devices and mobile OS versions. That's where the community comes in -
please test it in any device you can find and report bugs!
The WebFonts extension is deployed for all supported languages in
translatewiki.net and is updated several times a day with the newest
changes. Please feel free to create WebFonts testing pages there.
The short summary of my tests is that:
* WebFonts are just ignored in older versions of Android, in the
various Mobile Windows versions, in Symbian (Nokia) and in Blackberry.
* WebFonts may work on the newest Android versions, but i did very
little testing on that, and it changes between browsers.
* WebFonts are loaded on Apple devices like iPhone and iPad, but not
always rendered correctly.
* WebFonts work well in devices that run a real GNU/Linux OS, such as
Nokia N900. Very sadly, such devices are expensive and rare.
(<rant>It's just criminal how Nokia markets them so weakly.</rant>)
* <biased-opinion>My impression is that mobile Firefox (a.k.a Fennec),
in general, has better support for i18n, like web fonts, fonts in
general and right-to-left languages, but please test for yourself and
don't take my word for it.</biased-opinion> (Disclaimer: I'm a
volunteer Mozilla Rep.)
> I have started trying to read ml.wiki on my cell pointing my phone
> browser at ml.m.wikipedia.org and all I get are boxes right now. I'm
> using Opera Mini browser on a Nokia E63.
WebFonts are not currently deployed on Malayalam and Tamil Wikimedia
projects. These are probably the same squares you would see a week
WebFonts are deployed on translatewiki.net and on test.wikipedia.org,
so again - please test them there as much as possible. You can also
try testing in other languages of India.
Amir E. Aharoni
Wikimedia i18n team
*The Hindu : "Creative Commons: the licence to evolve"*
*A win-win scenario: The objective of the Creative Commons licence is to
encourage improvisation and remixing of content that everybody can benefit
from. Wikipedia is an example.*
*Cultures evolve gradually, and this cumulative process of evolution is, of
course, driven by various forms of human expression: art, literature,
music, photography and films, to mention a few. With the dawn of the
Internet age, these cultural vents have undergone a renaissance of sorts.*
*The concept of user-generated content, where users create blogs, music,
photographs and films for mass consumption, was unheard of before the
advent of the Internet. While the concept of ‘public domain', where
creative works are not bound by Intellectual Property Rights and laws was
prevalent even before the Internet, the full potential of this idea has
been manifested with the Internet.*
*The inherent difficulty with user-generated content is that because a
whole community owns it, it could again get entangled in the prohibitive
intellectual property laws. A plausible solution, which was proposed in
2005, is going really strong today; these are a certain gamut of licences:
Creative Commons. The objective of these licences is to encourage
improvisation and remixing of creative content to facilitate evolution of
*The meaning of copyright today is known to all, so are the restrictions
that come with it, which are often taken for granted. The tag ‘All rights
reserved' on creative works has an underlying threat: read ‘Full
*The idea of restricting creative works from evolving is, in effect,
allowing culture to stagnate. The copyright regime, with all its intentions
of keeping users mere consumers and not content generators, effectively
leads to this stagnation by suing and discouraging users who dare to create
based on a copyrighted work.*
*The enormous possibilities in creating content on the Internet has
encouraged a lot of users to put up their works in the form of blogs,
articles, videos, music and films on the Web. Most of them do it for
personal purposes without giving much importance to the licensing. But it
is essential to adhere to a licence that allows others to further remix,
improve and build upon the available content.*
*This is precisely is what Creative Commons licences aim at. Creative
Commons licences are copyright laws with the tag ‘Some rights reserved',
and in essence convey that licensees may copy, distribute, display and
perform the work and make derivative works based on it only if they give
the author the credit in the manner specified by the licence.*
*There are variants of this licence that provide flexibility to authors to
alter the parameters.*
*Vigneshwar Shankar, an undergraduate student and a photographer by hobby,
endorses the Creative Commons licences and believes that contributing to
the public domain with such licences is the best thing to do. “Enriching
content for the public domain is crucial. At some point, everyone's going
to be benefited by it. Look at what Wikipedia has become today,” he says.*
*A ‘read-write culture'*
*User-generated content with the carapace of the Creative Commons licence
will enrich the public domain.*
*Lawrence Lessig, one of the founders of the Creative Commons non-profit
organisation, which released the Creative Commons licence, puts it in a
nutshell. He calls the copyright regime based on Intellectual Property
Rights a ‘read-only' mode where the commons, or users, are only allowed to
‘read' the content. With Creative Commons, users will be able to read and
write; that is, users will be able to consume and create, leading to
Important Note : The publisher ( The Hindu ) of the above news article owns
the copyrights of the article / content. Request to kindly not reproduce or
circulate the content further. The information is only shared only with an
internal community who have been featured on this article. All copyrights
are duly acknowledged.