Archive for September, 2008

GNOME 2.24 is out. Want to get involved?

Wednesday, September 24th, 2008
The GNOME 2.24 Splashscreen

Congrats everybody to 2.24.0! Been hard work sometimes, but always fun.

Now while you, dear user, are probably going to send zmrzlina, chocolate, cheese and kisses to your beloved favorite hackers*, you might also consider becoming involved. Here’s some offers I have in mind (unfortunately all unpaid positions). ;-) Not all of them require coding skills (I don’t code either, so “Why don’t you do it yourself?” comments are unrequired).

  • nautilus-actions is looking for a new maintainer, see the announcement. Interested in helping out? Or even fixing the most favourite bug? Feel free to contact the former maintainer if interested!
  • Update ancient project websites. We have lots of old projects sites in http://www.gnome.org/projects/. You don’t want to code but you know about HTML and a bit of CSS and your Wnglish is good. A list was provided by element3260 as part of his GHOP work, available here – this should be transfered to a wikipage at live.gnome.org first, see the Gnome Goals pages for an example how this could look like.
  • Push the Gnome Goals to clean up our stack for 3.0 by providing patches. There’s still enough to do. Also see GioPort and GtkPrintPort.
  • Take a look at bugs in Bugzilla with gnome-love keyword set. They are a good place to start working on the code of your favourite project.
  • Unrelated to this, worst translation issues will become blocker bugs for GNOME 2.26 too. Providing good applications definitely also includes a well-localized UI, and this is impossible when not fixing them.
    Some examples (not to blame developers, but to get a feeling what this means): Missing context, split sentences, english structures, broken plurals.
    Most (not all) translation issues are easy to fix and gnome-love bugs too. Just take a look at bugs with L10N keyword set.
  • Identify unmaintained modules. I’d love to have a small script that could run on my svn checkout and printing the date of the last svn commit (svn log –limit 1) that was not an updated .po file. But I don’t do code, so if anybody has too much time… *cough* Would make it easier to identify rotten modules in order to remove them from Bugzilla and the translation statistics, so nobody wastes time anymore on them.Another shameless request – I’d also love to have information on the language team pages about the date of their last commit for that language. Would make identifying non-active teams or maintainers easier.
  • Nothing in that list for you? Don’t want to code? For more ideas, visit JoinGnome.

(* “hackers” refers to developers, translators, artists, marketing folks, bugsquadders, doc writers, …)

Last week.

Tuesday, September 23rd, 2008

Private:

  • Finally been able to attend a concert of Vypsaná fixa at a festival. Feeling happy for the rest of the day (not only because of that one band).
  • Watched Prague’s local icehockey derby Slavia vs. Sparta (2:1). Could have been more exciting. Security checks like at an airport. Same as the food prices at the venue: Impressive, in a negative sense.
  • Bought two beers at night and gave one to the first person I met on the streets. Two street cleaners lucky about having a short break. Do that more often, it’s easy.
  • It’s that Burčák season again! Yummy.
  • Travelled to Maemo Summit with jbenc. One guy sitting next to us in the train heard that we were talking about linux and joined us. There’s really linux users out their in the wild, they exist, and they are not antisocial! :-P

Maemo:

  • Maemo Summit itself was awesome – most impressions have been already covered by the blog posts on Planet Maemo. Much more people than expected and a nice geeky venue. In general it also underlined my positive impression that Nokia’s opening and understanding Open Source better. My talk went well though there could have been more attendees. Most discussions (like always at conferences) happening outside of the talks or when having a beer at the evening, quite productive. Great Openismus party on Saturday, great company! ;-)

GNOME:

  • Now looking forward to the GNOME 2.24.0 release coming up this week. Hope we all (devs, translators, documentators, artists, bugsquadders and so on) did a good job and will get content users and good reviews.

Getting Nokia involved in Maemo Bugzilla?

Tuesday, September 2nd, 2008

Nokia

Thanks to Nokia I had the opportunity to spend a few days at Helsinki last week, having talks, discussions and meetings with several people, especially in Maemo error management.

As I interact with Nokia’s error management by discussing/forwarding bug reports, and as there have been some confusion and misunderstandings already (Karsten‘s and my work do not fit perfectly into Nokia’s current well-defined and not easily to change workflows), I gave a small presentation about what we are doing, the problems and expectations.
I see ourselves (the maemo.org bugmasters) as a kind of bridge between the Maemo community and Nokia’s product management. Being involved in Maemo and GNOME, we’re used to open source and understand its culture, but I can also understand managers being conservative when it comes to changes and when advantages aren’t obvious at first sight.
So at the beginning of my presentation I asked the audience (Nokians involved in error management) how many of them have ever dealt with open source community, culture and practices. It was less than 15%, something I had expected. My theory is that in general, professional error management in open source projects often simply does/did not exist, hence there can’t be that many people existing already used to it – definitely not Nokia’s “fault” or whatever. I explained that 3rd party developers, power users and fans can help any company leading an open source project in producing better software by helping in testing and providing patches and feedback, but they also have expectations and want to get something back for their efforts, e.g. becoming more involved and having more transparent processes. Or to quote a fine sentence by Jaffa that I also said while having my talk: “If Nokia aren’t seen to be committed to the community, why should the community be committed to Nokia?”
In my impression Nokia has already improved in understanding, but there’s still a long way to go. There have been “bad” examples, e.g. I was told that Nokia probably publishing updates more often now is already a sign of becoming more open (Sorry, this is an internal decision and has nothing to do with community involvement). But there also have been good examples. See, Nokia is a big company with lots of different opinions and people with different backgrounds and hence different definitions of “Openness”, and talking to each other helps to understand “the other point of view” better. Some Nokians involved in error management will be present at Maemo Summit. Looking forward to continuing discussions with community folks (and input) around.

A valid argument that I can second is that developers want to have one central place to track their bug reports. This is currently Nokia’s internal Bug tracking system. Some Nokia developers also comment in Maemo Bugzilla (mostly those coming from open source too, and in my impression this number has increased a bit in the last months), but quite often you don’t have the time to track two systems. Hence I waste spend a lot of time already on keeping reports in sync (been working lately on porting a script I use in GNOME Bugzilla to quickly insert comments on bug reports to save some time).
But I also do second that in the long run we should have those components that are completely open source in Maemo Bugzilla only. Now you might ask: Why not starting this immediately? So when examining on how hard it will be to open some parts of the existing internal infrastructure, I was often told that there are legal issues to resolve first. It’s not only about Nokia’s internal Bug tracking system, there’s much more that’s part of the long tail – information that a commercial company does not want to be accessed by its competitors, such as for example policy plans, product and hardware information, information about the internal testing infrastructure and especially copyright related issues. So it’s time to identify and check those blockers one by one. But there definitely IS slow change (maybe too slow for some Maemo folks that have been expecting more changes for the last two years), probably Nokia just needs more lawyers to handle all this more quickly. ;-)

maemo.org Bugzilla stuff

Apart from the ongoing triaging of new incoming bugs, syncing between the internal Bug tracker and Maemo Bugzilla and reorganizing some components in Maemo Bugzilla to fit better with Nokia’s internal development teams, we are going to remove the deprecated bug resolution RESOLVED LATER in the next two weeks. “LATER” either means WONTFIX, or the bug should just remain in open state. This requires “fixing” the existing bugs first. After that, LATER can be removed from the Bugzilla code. We have already removed the meaningless Target Milestone “Next” and retriaged all bugs RESOLVED REMIND that also needs to be removed from the code.
I have also disabled setting the Target milestone when filing a new bug, because Target Milestones are definitely not wishlists. Setting “Fremantle” or “Harmattan” as a target milestone for a bug should really mean that a developer works on it and plans to get the issue fixed by that release. We currently also discuss on switching to the “guided” bug entry template to make it easier to file valuable bug reports, but currently that template is way too crowded and noisy to be useful, so this will take some time and changes.