Archive for June, 2012

GNOME.Asia summit over

Sunday, June 10th, 2012

GNOME.Asia summit ended five hours ago. A big thanks to our friendly and welcoming organizers for their great work and the good time that we had (and still have) here in Hong Kong, and to the companies that sponsored this conference. As sleep is a precious treasure I’m just posting five of the snapshots that I made and leave writing detailed posts to others.

OpeningAllan, Jon and Jakub's talkThunderstorms for free!Liansu's talkClosing

I’d like to thank the GNOME Foundation for their sponsorship! Sponsored by GNOME Foundation

GNOME.Asia summit, Hongkong

Thursday, June 7th, 2012

Today I arrived in Hong Kong (PRC) to attend this year’s edition of GNOME.Asia summit at the City University of Hong Kong. It takes place on Saturday and Sunday and you can should check out the schedule in case that you are around.


On Sunday I am going to explain how to write and improve GNOME user documentation, and maybe join Tobi to present how to triage bug reports.

While asia has so much manpower and emerging economies, GNOME’s development (and its dominant culture) still feels mostly US/Europe centric to me. Ever wondered how many maintainers in GNOME are based in India or China, to pick just two examples? I don’t know many unfortunately. So if attend GNOME.Asia and would like to talk about cultural differences in communities, user documentation, bug management, translation, release management, …, I’d be happy to talk to you!

Also, thank you GNOME Foundation for covering a large part of my expenses! Sponsored by GNOME Foundation

Wikimedia Hackathon, Berlin.

Saturday, June 2nd, 2012

I’m in sunny and windy Berlin (Germany) again this weekend to attend Wikimedia’s “Hackathon” (Wikimedia is the organization behind Wikipedia and some other projects and websites, in case you didn’t know). I’d like to thank Wikimedia Foundation for the invitation.

Apart from discussing bug management with people I spent most of the day looking at the situation in Wikimedia’s bugtracker a bit – checking the growth rates in the most popular products (where to triage reports more aggressively), gathering some statistical data, trying out funky queries to identify rotting reports (no NEEDINFO state or tag? Sigh, Mozilla Bugzilla makes the same mistake), adapting one of my Greasemonkey scripts to work, looking at existing Wikimedia bug management documentation and identifying missing and redundant information, and in the coffee breaks dreaming of a Natural Language Processing hook when submitting new tickets to analyze the quality of a report on the fly and make the reporter improve it (I know that there’s scientific papers about this topic but I still haven’t seen any implementation so far). Errm, yeah, that was a long sentence.