Planet Ensigogne

Vincent Untz: Du choix des villes organisatrices des RMLL

Vincent Untz — 2010-07-15T21:57:00+00:00

Cela a été annoncé pendant les RMLL 2010 (dont je viens de parler): les RMLL 2012 auront lieu à Liège. J'ai un petit grain de critique à ajouter à cette nouvelle... Mais je tiens à préciser dès à présent que je suis ravi que les RMLL quittent le territoire français (cela les rendra un peu plus mondiales) et que je ne doute pas un instant que le dossier de candidature réalisé par l'équipe de Liège était de grande qualité.

Après avoir discuté avec plusieurs personnes, je m'interroge sur la méthode de sélection de la ville qui accueille les RMLL : il n'y a pas eu, à ma connaissance, d'appel à candidatures et de manière générale, le processus décisionnel est quelque peu opaque. Cela me dérange un peu, donc autant en discuter. Et ayant participé à la sélection de villes organisatrices du GUADEC par le passé, je sais que ce n'est pas toujours facile de décider. On peut tout de même tenter d'améliorer la visibilité depuis l'extérieur :-)

Première étape : en farfouillant un peu (j'ai trouvé un lien sur cette page), je suis tombé sur le site du comité des RMLL, qui offre quelques informations, et notamment la composition du comité ainsi que quelques (maigres) informations en ligne sur comment candidater. C'est quelque chose d'un peu méconnu, je pense, donc allez lire tout cela si vous avez le temps (et que cela vous intéresse, évidemment ;-)).

Le manque d'appel à candidature est, à mon avis, le plus problématique : il semble dommage de ne pas en avoir, en particulier dans la mesure où au moins un groupe aurait aimé candidater. J'avoue avoir du mal à comprendre pourquoi il n'y en a pas eu, mais j'imagine qu'on a pu penser qu'il fallait décider pendant les RMLL, et qu'il n'y a pas eu le temps de réaliser cet appel avant. Était-ce cependant vraiment nécessaire de prendre une décision dès à présent ? Attendre deux ou trois mois aurait par exemple été possible, sans pour autant poser un problème à l'équipe organisatrice choisie. Peut-être y a-t-il une autre explication que je ne connais pas, mais j'avoue avoir du mal à imaginer qu'elle justifierait de sauter l'étape de l'appel à candidatures.

En ce qui concerne l'opacité du processus, le principal problème est qu'il n'y a aucune documentation sur les éventuels candidats, ni de réels critères permettant d'expliquer pourquoi une ville serait préférée à une autre. Par exemple, comment le choix est-il effectué si les dossiers sont tous de qualité ? Ou est-ce envisageable qu'une ville bénéficie d'une sorte de bonus afin d'aider au développement de la communauté dans la région ? Je ne demande évidemment pas que la décision soit prise en public — je peux concevoir sans problème que c'est le type de décision qu'on souhaite prendre en étant complètement à l'aise, sans avoir à se censurer sur ses propos. On peut aussi imaginer la possibilité de recueillir des commentaires auprès de la communauté sur les différentes candidatures, par exemple. Le fait est qu'ouvrir un peu le processus pourrait aider à améliorer les futures candidatures, sans pour autant nuire.

Pourquoi est-ce que je me pose ces questions et pourquoi est-ce que cela me dérange un peu ? Tout simplement parce que les RMLL sont un évènement important pour la communauté francophone, et que s'il est possible d'améliorer un peu une partie de l'organisation, cela ne peut que résulter en des rencontres encore plus utiles à tous :-)

Et vous, qu'en pensez-vous ?

Vincent Untz: Back from Bordeaux: RMLL 2010

Vincent Untz — 2010-07-15T13:50:00+00:00

At the end of last week (assuming it's okay to say that the end of the week starts on Wednesday ;-)), I went to Bordeaux for the RMLL 2010: this is simply the biggest community-oriented event in France. Since I've been traveling often lately and I'm going to leave for GUADEC later this month, I chose to not attend the whole event and to only be there for 3-4 days instead of the full 6 days experience.

Booths

The Mandriva people had a really great idea this year: they proposed to try to share a booth among distributions, and thanks to them, we were able to have an openSUSE presence on the first few days. So walking down the hall where all the booths were, you could see Debian, Fedora, Mandriva and openSUSE all together. Of course, we shared more than just the booths: we're all friendly people after all, so we chatted a lot and enjoyed being together. I really want to thank Michael from Mandriva for pushing me to make sure openSUSE would have a place here.

One funny tidbit is that we never requested a GNOME booth since all the GNOME people coming to the event knew they'd be busy with various other tasks (and I didn't feel I could handle both a GNOME and an openSUSE booth...). However, we still got one this way ;-) It was merged with the distributions booth, and I just put GNOME stickers all around to make sure our GNOME love gets distributed!

openSUSE Booth at the RMLL

The picture above shows the openSUSE booth during the week-end, which was much better organized than during the first few days! I don't think I have a picture of the first booth, so you can't really compare, but it's probably better this way ;-) Thanks to Michael (the openSUSE one) for sending us DVD, stickers and a few t-shirts: it helped make the booth more interesting!

Radio RMLL

A small group of volunteers was broadcasting a radio show during the whole event: Radio RMLL. And guess what? The world-famous Frédéric Péters was part of that team! The archives are online, and you can make fun of various distributions by listening to the distribution roundtable that Frédéric organized: hopefully, the fact that we knew each other made it not too boring!

Talks

Like for Linuxtag, I delivered two talks: one about GNOME 3.0, and the other about contributing to openSUSE. While both were in the Development track, I thought it'd be better to talk about GNOME 3.0 from the user perspective since that's what people were expecting; on the other hand, for openSUSE, I wanted to show that contributions to a project like openSUSE aren't necessarily technical contributions.

One thing that struck me (and the other GNOME people) is that we get much more excitement when we propose a talk about GNOME 3, than when we were trying to present the latest development in GNOME during the 2.x era. It's not the first time we noticed this (it happened in all previous events where we had some GNOME 3 bits too), but the contrast is so important that I'm now convinced the version number is much more important from a marketing perspective than from a technical one. Definitely something to keep in mind for our future roadmap, and for when we'll think about GNOME 4.

I also got interviewed for Linux Pratique about GNOME. During the discussion, I discovered the editors are based in Sélestat, which is a small city a few kilometers away from where my grand-mother lives. Small world.

The people

The best thing about an event like the RMLL is of course all the people you meet. It was good to see old friends (Didier, Frédéric, Michael, Alexandre, just to give a few names) as well as new faces! Being nasty people, we all made fun of each other's projects, but we also learnt the latest news about all those projects and their contributors. Oh, and we managed to bring someone living in London to an Irish pub in Bordeaux — is there a better place to enjoy food in France?

It was interesting to see that there were GNOME-friendly people (not just GNOME contributors) all around, although we weren't present with a real booth. And I was obviously glad to meet some members of the french-speaking openSUSE community: Guillaume, Julien, Jimmy and Jean-Luc. I think it's one of the first time (if not the first) where we managed to make openSUSE really visible during an event, and it was successful. It's a good step in making openSUSE-fr an even more vibrant group!

Come next year!

The event was not perfect, though: I think most people would agree that the wifi could have worked much better (it was down way too often), that having the event split between various building that weren't really close to each other was suboptimal, and that the weather was, well, way too hot ;-) But I'm sure the organizers did their best, and they even succeeded in getting a few drops of rain on Friday!

So not perfect, but it's still one of the two or three times in the year where you can connect with most of the free software community in France, and if only for this reason, that's a must-go event here. Oh, and next year, it'll be in Strasbourg: that's another reason everybody should come!

Vincent Untz: Question existentielle du jour

Vincent Untz — 2010-07-12T16:04:00+00:00

Quel est le plus grave :

le fait que j'aie la télé allumée sur Un dîner presque parfait ?

le fait que je reconnaisse immédiatement la musique de Retour vers le futur III jouée par ZZ Top qui passe 5 secondes dans l'émission citée ci-dessus ?

Je m'interroge sérieusement...

Alban Créquy: Play chess with your contacts on your N900

2010-07-09T14:40:42+00:00

Michael released Miniature 0.1.9-3 to Maemo extras-devel yesterday. With this version, you can play chess with a contact on your N900 without configuring any server thanks to Telepathy. There are still crashes, bugs and UI to polish, but it is demoable and you can already enjoy playing chess with your friends!

The protocol used by Miniature is based on the Forsyth-Edwards Notation. At the moment it sends the whole state of the board to the remote player at each move. Miniature only sends valid moves, but does not have any protections about possible unfriendly other implementations yet.

Miniature implements the standard Telepathy Client interface with the Telepathy-Qt4 library. This enables Miniature to be automatically started by Mission Control on your N900 when a contact invites you to play. Telepathy stream tubes care about the connectivity to the remote device. The Address Book API is used to to show your contacts in the same way as other applications on the platform (avatars, contacts are merged correctly, status).

Quick overview of the integration with Telepathy

Here is how to play chess step by step:

1. Choose “Join P2P Game” in the main menu

2. Select your contact in the contact selector

3. Wait your contact’s answer

4. Your contact is asked whether they want to join the chess game

5. If your contact accepts, you are ready to play!

Feel free to join the Miniature mailing list and IRC channel.

Laurent Goujon: planetyahoo is moving...

2010-07-08T22:05:00+00:00

planetyahoo is moving to a new server and also to a new software. As usual you should observe no disturbance but in case, don't hesitate to contact webmaster AT gobio2.net

Laurent

Laurent Goujon: Comment installer une ISO Ubuntu sur une clé USB... à l'aide d'un Mac

2010-07-07T23:13:00+00:00

Attention billet très technique et très geek : ami lecteur, éloigne toi si la ligne de commande te fait peur ! (Je pense notamment à toi, ami de facebook)

Bon, je possède un Mac avec Leopard installé dessus (et pas de dual boot), et j'ai voulu flasher une clé USB avec Ubuntu Netbook. Las, trois fois hélas, Ubuntu ne fournit plus des images prêtes pour utilisation mais uniquement des ISO à graver (contrairement à Moblin et Meego soit dit en passant).

Et bien qu'il y ait quelques instructions, rien qui ne marche vraiment sous mac !

Donc voici mes instructions pour Ubuntu 10.04 :

Récuperez l'ISO dont vous avez besoin
Récuperez l'image hd-media de la distribution correspondante, c'est à dire le fichier boot.img.gz : ici pour Ubuntu 10.04
Décompressez l'image : gzip boot.img.gz
Insérez votre clé usb (attention, elle sera effacée par la suite)
Vérifiez à quel périphérique elle correspond : diskutil list (elle doit apparaitre avec un périphérique /dev/diskX)
Démontez la clé (mais laissez la branchée) : diskutil unmountDisk /dev/diskX
Flashez l'image : dd if=boot.img of=/dev/rdiskX bs=1m (oui rdisk et pas disk, ca accélère beaucoup les choses)
Ejectez la clé : diskutil eject /dev/diskX
Débranchez et rebranchez la clé : elle doit apparaître sous le finder
Ouvrez l'ISO dans le finder
Copiez tous les fichiers de l'ISO dans la clé (qui doit aussi apparaitre dans le Finder)
Copiez les fichiers du répertoire isolinux (de l'ISO) à la racine de la clé (ca va écraser certains fichiers, c'est normal !)
Ejectez la clé, c'est prêt : il ne reste plus qu'à booter et au prompt, appuyer sur Return pour afficher le menu.

C'est sûr, c'est bien plus compliqué que sous Linux ou Windows...

Olivier Crête: Removing leftover Facebook Chat Jabber contacts on Maemo

2010-07-05T05:09:24+00:00

A couple months ago, Facebook announced announced that their chat system would also be available through XMPP. So it is possible to just configure it like any other Jabber server on a N900. And then to merge Facebook contacts with other contacts and it the address book will store it as a field of type « X-JABBER ». Since the PR1.2 version of Maemo5, Nokia has added a specific profile for Facebook to the N900 software. But instead of calling the address book field « X-JABBER », they created a « X-FACEBOOK » field (since Facebook Chat is not XMPP in the backend, it can not talk to other Jabber servers). So if you remove your old Jabber account and re-add it as a Facebook account and use Marco’s contact merger to merge back the contacts. You’re still stuck with a bunch of extra « X-JABBER » fields in your contacts. So to clean them up, I wrote a really simple program to remove them. It is based on Marco’s jid-to-email program. You can get the source code or a precompiled binary. You can just put the binary on your N900 and run it from the Terminal as « ~/MyDocs/remove-old-facebook » (if you put it in the N900’s documents root). Be warned that is is not a good example like Marco’s code, I stripped all error handling and it never frees anything. If you want a good example, look at Marco’s code.

Vincent Untz: The true Lennart

Vincent Untz — 2010-06-30T22:46:00+00:00

We all know Lennart. No need to mention his last name since there's only one (well, nobody can pronounce his last name anyway). As we all know, Lennart looks like this:

The Lennart we know (note his red t-shirt, did you ever see him with a non-red t-shirt?)

But at LinuxTag, I discovered he was trying to hide the truth, even though I still have no idea why. Yes, ladies and gentlemen, the Lennart we know is only an illusion! Yes, he was pretending all the time! And yes, to confuse all of us, he's sometimes hiding behind another picture! I know it will come as a shock to everyone, and I know it will be difficult to admit, but here is the true Lennart:

The true Lennart (yes, it's the same person: look at the t-shirt!)

Vincent Untz: LinuxTag 2010: Attack of the Geekos!

Vincent Untz — 2010-06-30T09:55:00+00:00

It's finally time to talk about LinuxTag 2010. It was my third time there, and this year was the best so far, at least for me! And that's most probably because of how amazing our openSUSE booth turned out to be! Or maybe it's because of the invasion of the Geekos?

openSUSE Booth

We certainly didn't have a big slot for out booth, but oh boy... it ended up big! Our booth was always filled with people, who, I guess, got attracted by the touchscreens we have. But attracting people is of no good if you can't get them interested. We did various demos on the touchscreens, but our small secret ingredient were the workshops: four times a day (and sometimes even more), people could sit down in our booth to participate in a session on various topics — those ranged from learning Inkscape, to creating your first package in the Build Service, via playing together with GNOME Shell. That really worked out well, especially at it helps getting the visitors more involved in the discussion.

The world-famous Geeko

Many thanks to Jan (who had to suffer my presence way too much, I'm sure!) and Michael for the organization of our booth!

GNOME Presence

As mentioned in my previous post, there was no GNOME booth at the event. And it didn't go unnoticed: I met various people wondering about this. So I surely hope the German community will make sure it doesn't happen again next year!

Even without a booth, we managed to get a relatively good presence during the event. Of course, it was easy to stumble upon some GNOME people — our friends from Openismus, of course, but also Stormy, Lennart, Tobias and more. Some of us were giving a GNOME-related talk, and Stormy and I participated in a RadioTux interview, so our footprint was present :-)

Talks

I didn't attend many talks. Actually, I think I only attended Stormy's one — Stormy is good at making you raise your hand to keep you connected to what she says — and Lennart's talk about Surround Sound.

The talk Johannes and I gave went quite well, with around 50 people in the room, which is quite good since it was not a keynote and it was in English. We had good questions from the audience, which at least means they were not totally asleep ;-) Generally speaking, I'm nearly always pleasantly surprised by the reaction of people when they get to see GNOME Shell for the first time: I somehow always expect that I have to carefully explain some of the design decisions, but it's apparently unneeded. Most of the persons I meet are glad we're doing something different and seem to be ready to try the change!

A wilder Geeko, built by yours truly

The live A-Z Guide to openSUSE Contribution was the second talk I was involved in, with Henne. With 26 letters in 30 minutes, you might think it's plenty of time. But we actually had to rush to talk about everything! The goal was really to show that there are tons of areas where people can contribute in openSUSE, while most people think it's just packaging. And 26 was our limit, but I'm sure we could have gone on and on for a long time: everyone can help (packaging, sure, but also presence at events, support, bug triage, helping with screencasts, contributing to a positive atmosphere inside the project, etc.). Most of our items were actually not specific to openSUSE and are common to most free software projects... I really like the format Henne found for the talk; that's something I'll keep in mind for future talks.

Meeting people

LinuxTag is also a great opportunity to sit down with a few people. We had both GNOME and KDE people (Stormy, Claudia, Frank and I) all sitting around a table to discuss the organization and the bids for Desktop Summit 2011. Thanks to our experience with GCDS, we have a good basis for the organization since we know what worked well and what didn't. We came out with an aggressive timeline to take a decision during this summer, which should help the organization team start the work early.

Johannes, Stormy and I also chatted about the GNOME developer tools and what we can do to improve our story there. That's something where the Foundation wants to help, but this can only happen if our community wants to improve them, of course. We wondered for a bit while our own developers don't use a tool like Anjuta. Is it just a matter of habits? Or is it missing some features? (I know that, in my case, I just can't live without vi-like keybindings...)

c-base

On Friday evening, the GNOME folks were invited to a barbecue organized by LXDE people at c-base. I had heard about c-base for quite some time, but it was a first for me. Lennart insisted that I should go through the main entrance to truly enjoy the experience, so Andre guided me there (okay, he nearly got lost ;-)). And indeed, I can only recommend that you do the same if you ever go to visit c-base. And I know for sure I'm human now!

The highlight of the evening was undoubtedly the learning of a new card game: skat. I watched people play, and it somehow felt a bit familiar; that's because it's somehow similar to belote (although it's also completely different, but well...). Tobias offered to teach me, and it all went well. I mean, it made sense. And then I was explained how the bidding works. I'm still trying to figure out why it works this way ;-) I understand how it works, but... it just feels totally arbitrary with no reason. I was glad that I managed to help Stormy and Kat learn it later on (well, Stormy had understood most of the rules already by watching the game). So we were three complete beginners playing skat at some point :-)

Attack of the Geekos

But the best thing about LinuxTag was the omnipresence of Geeko, the openSUSE chameleon. I must admit I enjoy Geeko, and that's something I sorely miss in GNOME: our GNOME foot is nice, but that's not the same. We should probably talk more about our beloved Rupert, I guess. (And I still don't have any Rupert at home, that's a tragedy for me!)

As seen in the pictures in this post, we had several versions of Geekos, and I managed to bring some of them home. One of the workshop we had everyday at the openSUSE booth consisted of creating your own Geeko-ified object: the wireframe Geeko was one of them, but people also had the opportunity to create a pin, a shopping bad and a magnet. You can recognize Henne's creative mind behind all this.

But that's not all, we had a balloon clown, who created tens of balloon Geekos:

Our amazing balloon clown by Thomas Schmidt (see more pictures)

And the balloon Geeko can survive a flight trip, here's mine a few days after the event:

A light Geeko

The stuffed Geekos we had were highly-demanded: everybody loves it! And I understand, really: how can you not love it? At some point, I took 3 or 4 of them and hid them in various places in the venue. Actually, they were not really hidden, but integrated: it just felt like they belonged there. And I'm sure it made some people smile ;-)

Yes, LinuxTag was big this year, and I'm happy that Novell let me go to the event! I hope you'll want to come next year, now :-)

Olivier Crête: N900 vs Nexus One: a comparison

2010-06-27T03:16:58+00:00

About a month and a half ago, I had a smallish bike accident, I did not have a single scratch, but I managed to fall right on my N900 and crack the LCD. So I’ve used a Nexus One as a replacement until I managed to fix the N900. That gave me a chance to compare them.

You should also know that I am entirely biaised as I was paid to make the VVoIP calling on Maemo incredibly awesome. I have no relationship with Google and they did not pay me to make their stuff awesome (so it is not awesome). The opinions stated here are mine and mine only. They are not approved by my employer Collabora, any of our clients or competitors, the Queen or anyone else than me.

I’m comparing both devices with the latest software version as delivered by their respective OTA update system. So it is Maemo 5 PR1.2 for the N900 and Android 2.1 (Eclair) for the Nexus One. I make no claim of fairness. This is not a guide to chose which phone to buy.

Browser:

Extensions: The N900 browser supports (badly) a few Firefox extensions (like Adblock Plus or Greasemonkey). That said, they’re already quite useful. Maemo +1
Windows: Maemo 5 also handles multiple windows as regular windows, while the Android browser has them hidden in a menu. I did not discover that menu until I had a « Too many windows open, can not open new window » pop up. Also, the way « popup windows » appear in Android is really annoying, especially the fact that they are hard (impossible?) to zoom. Maemo +1
Flash: It’s not really usable (more like really unusable). Flash video playback is really slow (since all decoding is done in software). Steve is right, Flash is a disaster on mobile devices. Maemo -1
Text column width cheating and reflowing: The Android browser has a nice feature where it scales the width of text columns to the screen width to be nicely readable. It tends to break the layout of some sites, but it’s well worth it. Opera Mobile seems to do the same thing. But the Maemo browser doesn’t. Newer Firefox Mobile builds seem to also lack that. This means it is also unusable in vertical mode. Android +1
Scrolling performance: The Maemo browser uses tiles for when scrolling, so if you scroll too fast, it has to work real hard to render the next tile. It was much smoother on Android. That said, I heard the Mozilla people are trying to fix this in Fennec 2. Android +1
Rotation: The vertical mode of the Android browser just works better than the half-baked rotation support in Maemo 5. And holding it in one hand is much easier if its vertical. Android +1

Browser totals: Maemo 1- Android 3

Contacts & IM:

IM protocols: Android only supports Google Talk out of the box, while Maemo supports Skype, SIP and XMPP (including Google Talk) right of out of the box. And it is easy to add 3rd party support for other protocols (MSN, Yahoo!, etc) and it integrates fully into the existing system. Maemo +2
SMS/IM integration: SMS and IM are entirely separate in Android, but they are the same app in Maemo. Maemo +1
Metacontacts: Both platforms have metacontacts. Sadly, they are both incomplete. Contacts in both platforms include the basics: name, nickname, phone, email. Maemo can also link contacts from all IM accounts together, while Android only does it for Google Talk. But Android applications can put their own info in the contacts, so you can link in Facebook and Twitter contacts easily. On Maemo, well you can do it with Hermes, but you still don’t get the phone number or email address from Facebook (blame them for it). Equal points
Synchronisation: Out of the box, Android only supports synchronization with Google’s servers. Maemo only supports SyncML over USB (not over http) or Mail for Exchange. No points.

Contacts & IM totals: Maemo 3 – Android 0

Calling:

Ringtone: The Nexus One ringtones are just not loud enough. I’ve missed many calls because I just didn’t hear it. My colleague complained it wasn’t loud enough to wake him up making it useless as an alarm clock. That’s a pretty big fault for a phone. Nexus One -2
Voice quality: I did not do any objective testing, but I feel that despite the active noise cancellation of the Nexus One (with a second microphone), I can still hear calls better on the N900. N900 +1
VoIP: Android only has Google Voice (only works in the US) built in. Skype is only available from select providers. And I could not get any of the 10 SIP apps in the Market to work with SipPhone.com (a Google service). So no VoIP on Android for me. On the other hand, the N900 has excellent VoIP support (I know its excellent, it uses Farsight2, my project!). Out of the box, it supports Skype, SIP as well as XMPP Jingle calls. That means Maemo support Google Talk compatible calls, but not Android. How ironic. Maemo +2
Video calls: There is no front-facing camera on the Nexus One. The N900 has awesome video calls, including GMail compatible calls (a mobile first)! As well as Skype compatible video calls (another mobile first). Maemo +1
Accepting calls: The « incoming call » screen on Android has slide buttons. On Maemo 5, it has push buttons. Combined that with the fact that is auto-unlocks the screen when it rings and with the resistive screen, it means that I sometimes accidentally hang up or answer in my pocket. Really annoying. Maemo -1

Calling totals: N900 3 (Maemo 2) – Nexus one -2

E-Mail:

Both devices have email clients supporting IMAP. Android also has a separate application for GMail. Since I don’t use GMail, I did not try it seriously.
Combined inbox: Android has a nice feature where the inboxes of all account are shown at once. Android +1
Searching: It’s a funny thing. The Android mail application does not have any search feature. At least, Modest (the Maemo email client) has gained minimal searching in PR1.2. Maemo +0.5
Performance: The android mail app just feels faster and doesn’t get stuck waiting for God knows what all the time. Android +2

E-Mail totals: Maemo 0.5 – Android 3

Maps:

Overall: The Ovi Maps application for Maemo is a disaster, Google Maps just works on Android. Android +1 Maemo -1 (I’m giving a -1 because Ovi maps is so disappointing, they should have released the device without it)
Network access: That said, Ovi Maps has one nice things, you can download maps, while Google Maps is just pre-rendered tiles, which means it always requires Internet Access. Maemo +1
Navigation: Google has free navigation (in select countries), Ovi Maps for Maemo does not have navigation. Android +1
Voice commands: Android has them (including search), Maemo does not. Android +1
Search: Google Maps has Google search.. Ovi Maps has some crappy search that fails half the time if you don’t spell the address exactly the way it expects it. Ovi Maps can not search for things that are not addresses (like a restaurant ou a gaz station). Android +2
Extras: Google Maps also does nice things like public transit. I wish they had bike routes in Canada. Android +1

Maps totals: Maemo 0 – Android 6

Camera & Photos:

Camera Hardware: Both devices have 5 mega pixel cameras and they seem to have more or less similar performance. That said, I did not do any serious comparison. Equal points
Photo browser: The Android Gallery has a bit more bling, but it is the only built-in app that I’ve seen crash on the Nexus One. But functionality-wise, they seem pretty similar. Equal points
Button: The N900 has a hardware camera button. On the Nexus One, it is an on screen button. Touching the on-screen button while holding the camera in the right direction is really hard. N900 +1

Camera & Photos total: N900 1 – Android 0

Hardware:

Size: The Nexus One is quite a bit thinner, the N900 is a pretty bulky device. Good thing I don’t like thigh pants. Nexus One +1
Keyboard: The N900 has one, the Nexus One doesn’t. I though it was a fatal flaw until I discovered Swype, which is really awesome… if you only write in one language. But I write in both French and English.. Sometimes I send one message in French and the next one in English.. Sometimes I mix languages in the same message. Swype only does one language at a time. That’s not a problem with the keyboard. So N900 +1
Screen resolution: The same. Equal points
Touch screen: The N900 has a resistive touch screen, the Nexus One has a capacitive screen. Everyone is saying that capacitive touchscreens are nicer… I’m unconvinced. Yes, you need more pressure on the N900.. But the Nexus One’s screen sometimes strangely fails to react. It is also much less precise. That said, resistive screens have the annoying habit of reacting to pockets (especially annoying when it rings). Equal points
Digital compass: The Nexus One has one, N900 doesn’t. Nexus One +0.5
Volume buttons: On Android, when not in the music app or in a call, the volume button control the ringer volume. That means it’s really easy to turn it even lower than it already is. This is especially annoying sine the Nexus One volume buttons are too easy to push. Nexus One -1
Included Flash memory: The N900 has 32 GB. The Nexus One has none. Both have a microSD slot. The Nexus One did come with a 4GB card. That’s just not enough, I have 7 GB just for music on my N900, and that replaced a full 30GB iPod. N900 +2
TV out: The N900 has TV-out, the Nexus One doesn’t. I though it was completely useless (its just analog low def). But it was really useful when I cracked the LCD. N900 +0.5
Bands: The Nexus One is available in both AT&T/Rogers/Bell/Telus (850/1900) and T-Mobile USA (900/1700) bands for 3G. The N900 is only sold for the T-Mobile USA band (900/1700). Which mean no 3G in Quebec until Videotron launches its network (and they are one year late already). Both phones support the European 2100 band. And they’re both quand-band for GSM/EDGE. Nexus One +1
FM transmitter/receiver: The N900 has a FM transmitter and a FM receiver. I’ve only used them briefly. N900 +0.5
Speakers: The build-in speaker of the Nexus One is terrible, the N900 has some of the best stereo speakers I’ve seen on this kind of device. N900 +1

Hardware totals: N900 5 – Nexus One 1.5

3rd Applications:

Availability: There are lots of apps on the Android store. There are TWO paid games on the Ovi store for the N900 as of today (when it is not down). That said, Maemo has a lot of ports of existing Open Source apps in Maemo Extras. That said, many of the apps in the Android Market are terrible… Android +1
Application installer: The Android Market (which also acts as an app installer) just works. The Maemo 5 application installer is a complete disaster. It is user hostile and developer hostile. Maemo -1
Developer story: Nokia decided to scrap most of the Maemo 5 platform and review everything with a brand new toolkit. They’re completely unable to get a straight story about developer APIs. I think that is in part because they also want people to do Symbian apps. Nokia please, please, just forget about Symbian apps, just use J2ME like on S40. Google has provided a stable Java API.. But not a stable C/C++ API. Maemo -2
Python: A lot of the Maemo apps are in Python and therefore are memory hungry (on a memory starved device). Maemo -1

3rd Application totals: Maemo -4 – Android 1

User experience:

Maemo’s greatest weakness is the out of memory handling. There is only 256 megs of RAM and 768 megs of swap. That means that as soon as you do too many things, it starts swapping and the performance becomes terrible. This is made even worst by the fact that application startup is really slow, so many applications are in pre-started. Nokia should put a lot more memory in the next device and seriously fix the application startup time. Android has a nice thing where apps can serialize their content and be shut down when the system in under memory pressure. This leads to a much better impression of performance. Android +4
CPU speed: The Nexus One has a 1Ghz Qualcomm Snapdragon CPU, much faster than the 600Mhz TI OMAP 3430 of the N900. Nexus One +1
The real « multitasking » is much nicer in Maemo5, Android just fakes multitasking by having applications save their state and restart at the same point. That means you can not load two web pages at the same time or anything like that. Maemo +1
Both have multiple desktops with applets. Sadly, when I load my N900 desktops with applets, the system becomes sluggish. Maemo -0.5

User experience totals: Maemo 0.5 – Nexus One 6 (Android 4)

Geek experience:

Maemo is the ultimate mobile Geek OS. Having an x-term built-in is just amazing. Maemo +3
Maemo is a real Linux desktop-like operating system. To anyone who knows Linux, it just feels right. Android is the Linux kernel + Android. It was done in secret in a corner and Google has not made any serious attempt to join the great community. They re-wrote everything from scratch all the way to writing their own libc. Maemo +2
The choice language on Android is Java (beurk!). On Maemo is it C (or C++). Maemo +1

Geek experience totals: Maemo 6 – Android 0

Other stuff:

Media player: I didn’t really try the Android media player since there isn’t enough space on the SD card to hold any significant amount of music.
Notes: Android does not seem to come with a built-in notes apps. The Maemo Notes app is just pretty bad. They could have just shipped ConBoy instead…
PDF reader: the PDF reader on Maemo 5 is terrible, the Android one seemed kind of ok (but not great either)
RSS Reader: Does Android have one? I use the web-based Google Reader anyway

Total: N900 16 (Maemo 9) – Nexus One 17.5 (Android 17)

The Nexus One is really being dragged down by its its hardware. Especially when it comes to the bad speaker quality and the low ringer volume.. Did I mention how much it annoyed me ? That said, Android is pretty good. Better IM integration would be a big plus. And some VoIP too.

Our Nokian friends have their work cut out for them. First, they need to fix the memory handling story on Meego. Running out of memory and swapping all the time is just annoying. An almost desktop-class operating system requires desktop-class amounts of RAM (that means more of it). Ovi Maps needs a lot of work, hopefully they can work a deal with Google to get decent search in there. The browser could get its share of small screen friendliness and a performance upgrade. If they fix these few problems, Meego (as the future of Maemo is called) could very well be a success.

Were it not for its high geek factor (built-in X Terminal!), the N900 would have lost badly. That said, it’s still my favorite phone ever (did I mention I was horribly biaised?)

Vincent Untz: Reminder: apply for the GNOME sysadmin job before Tuesday evening!

Vincent Untz — 2010-06-21T00:14:00+00:00

In case you missed the news, the GNOME Foundation is hiring a system administrator, and this is happening thanks to many individual donors and Canonical, Collabora, Google and Nokia! I covered all this in a previous post already, so go read it if you never heard of that before. But I'm sure you've heard of it ;-)

What's important today, though, is that the deadline to apply for the job is nearing fast! It's June 22nd. Yes, this Tuesday. Had you forgotten about it? I sure had... So make sure your resume is ready and send it to the board before this deadline! Sure, we've already received applications from various candidates and we've started looking at them, but it could well be that you are the one! Not this one (well, if you are, I have several questions for you), just the person who'll help tame the GNOME infrastructure.

And no, it doesn't mean that the current candidates we have are bad; it just means we want to make sure all candidates apply before the deadline :-)

Vincent Untz: Ich bin ein Berliner — LinuxTag 2010

Vincent Untz — 2010-06-08T22:57:00+00:00

Brandenburger Tor by Wolfgang Staudt (Creative Commons by)

It's slowly becoming a tradition for me, since it's the third year in a row: I'm in Berlin for LinuxTag. I'm sure there will be some great fun there!

The openSUSE presence will of course be amazing: just take a look at our wiki page. Many contributors will have a talk, but we'll also have workshops on the openSUSE booth (I recommend Robert's Learn Inkscape Vector KungFu) and various interviews on RadioTux. And of course, you can just come to the booth to meet us: we'll be happy to share our enthusiasm with you!

On the GNOME side, we apparently couldn't find enough volunteers in time to run a booth. That's a sad news, but we'll still have many people attending the event, and we'll have several talks in the Desktop track on Saturday. I know I won't miss Stormy's one :-)

Since I knew I was going to the event, I submitted talks, and I was happy to see them accepted. While I do enjoy speaking, I think that having more than one people on stage can make the talk much more entertaining for the audience. That's why I'm excited that I'm sharing those two talks with great people:

Johannes and I both submitted a GNOME 3.0 talk, and after some discussion, we decided to merge our talks in one: The Road to GNOME 3.0. It's a one-hour talk, and hopefully, that length will allow us to discuss most of the changes in 3.0 and I hope this will contribute to getting people excited about this release!

to boost openSUSE, Henne and I will have a live A-Z Guide to openSUSE Contribution. I can't wait for this one, since it'll be a fast-paced talk, in a format I'm not used to. That's where you want to be if you don't know how to contribute to openSUSE, or to any other free software project, since some of our points are in no way specific to openSUSE.

If you're attending LinuxTag and you're interested in chatting about GNOME, openSUSE, desktops or distributions in general, or if you want to challenge me with an ice cream contest, leave me a message or come to the openSUSE booth! You can just come and say hi too, obviously :-)

Lucas Nussbaum: #debian-ubuntu on OFTC

2010-06-06T11:09:26+00:00

If you are a Debian developer and need realtime interaction with an Ubuntu developer about the state of your packages in Ubuntu (or vice-versa), #debian-ubuntu on irc.oftc.net might be useful. I had forgotten about that channel, but it resurfaced during the discussions about improving communication between both projects.

Lucas Nussbaum: EtherPad: web-based collaborative editor

2010-06-06T11:00:03+00:00

I recently (during a UDS lightning talk) discovered EtherPad. It’s a collaborative editor (like gobby), but uses a browser instead of a standalone application. It’s free software (Google open sourced it after buying the company that was developing it), and there’s a free online instance at ietherpad.com. Setting up a new pad is as simple as going to http://ietherpad.com/foo and clicking Create Pad. It’s written in Java, and not packaged in Debian (yet).

Lucas Nussbaum: XMPP Video calls with Nokia N900

2010-06-04T09:50:55+00:00

So, this morning, I did my first video call over XMPP between two N900.

However, so far, I failed to do an XMPP video call from an N900 to something else. When I try to call pidgin on my laptop, pidgin simply crashes, but of course that’s not a serious bug if people can DOS your pidgin instance since, according to the Debian bug:

Assuming your XMPP settings require that users must authenticate with you before being able to send you messages, only your authenticated users would be able to freeze your client, assuming they knew you were actually affected by this bug.

The upstream pidgin bug hasn’t seen a lot of activity lately. :-(

Vincent Untz: Hiring a sysadmin for the GNOME infrastructure

Vincent Untz — 2010-06-01T23:23:00+00:00

Two months ago, the GNOME Foundation started a fundraising campaign to get money to hire a part-time system administrator. Actually, we started this effort much earlier, but we made it much more visible with this campaign. Thanks to all the donors and to Canonical, Collabora, Google and Nokia, we were able to reach our objective. It was actually too fast for me and I wasn't even able to blog about the campaign in time! Once we realized the money was there, we moved on to the next steps — actually, we had those steps ready in the past, so it was mainly a matter of making sure everything was still okay.

We asked around and confirmed three names to form a hiring committee: Bradley Kuhn, Jonathan Blandford and Brad Taylor. With their help, Paul updated the job description that Owen had written some time ago. And after some discussion to define the whole hiring process, Stormy announced the job today. I really love that there have been so many people involved in this, with everyone targeting the same goal.

So if you love GNOME and if system administration has no secret for you, then go read the job description and if you're interested in the job, make sure to send your resume to the board before June 22nd! It's worth mentioning that an important part of the job will be to lead the sysadmin team (which is made of volunteers) and empower the community to make sure our infrastructure gets even more amazing. As you might know, our infrastructure could certainly do with various improvements, and the person we'll hire will make a difference for our project!

On a personal note, this topic has been something that was on my radar for a long time: I looked in my mail archives and found out that I sent a first mail on this topic in September 2007. Yes, that's nearly three years ago! Of course, in the meantime, this idea was put on hold so we could hire Stormy (a very good decision) and until we managed to raise the money for it (launching the fundraising campaign took much more time than originally planned, unfortunately). Phew. And I still can't believe this is finally happening :-)

Éric Pignet: Neposync v0.2 released, with support of Amarok collections

2010-05-31T21:21:17+00:00

One month after initial release of Neposync, I've just released version 0.2.

In addition to bugfixes, this release brings two interesting features:

Ratings of MP3 files can be copied from Nepomuk to files metadata, and vice-versa (first version only supported image files).
Neposync can now connect to your Amarok collection, and synchronize Amarok ratings with files metadata.
Syntax is intuitive: type neposync --amarok-to-files to copy Amarok ratings to files, and neposync --files-to-amarok to do the opposite operation.

You can find strange for the tool to perform synchronization with Amarok, which is far from the original goal, but needs are similar: will you spend hours to rate your MP3 files in Amarok if you have no guarantee these ratings will be kept if you move your files ?

Moreover, the two features brought together allow to copy Amarok ratings to Nepomuk:

neposync --amarok-to-files
neposync --files-to-nepomuk

or to copy Nepomuk ratings to Amarok:

neposync --nepomuk-to-files
neposync --files-to-amarok

The only drawback is that neposync now needs libmysqlclient to compile.

Download

Neposync moved from gitorious to github, to benefit from its own bugtracker and downloads page. So if you had cloned the gitorious repository, please update your URL.

Neposync is a simple Qt C++ program, using KDE libs. At your choice, you can:

download the source tarfile
To compile, just type qmake && make
retrieve git sources: git clone git://github.com/ericpignet/neposync.git
install the ArchLinux package from AUR: just type yaourt neposync

Once again, please tell me if you use the tool, if you find bugs, or if you'd like to see a new feature. I'm also interested by packages for other Linux distributions.

Lucas Nussbaum: Ubuntu and Debian

2010-05-29T13:38:41+00:00

I recently noticed the new Ubuntu and Debian link on every page of http://www.ubuntu.com/. That is very nice, and much better than the previous situation. Debian is also mentioned on the pages about Easy administration and Security.

Canonical has clearly improved a lot in the way they communicate about how Ubuntu bases its development on Debian’s.

Olivier Crête: N900 Video calls (Skype too!)

2010-05-25T18:15:02+00:00

The PR1.2 update of the N900 firmware is now officially released. The big new feature is video calls. It is also the world’s first phone to offer Skype video calls as well as Google Talk compatible video calls! And all of this uses Farsight2, the GStreamer based voice and video calling library. The whole Farsight2 team is very proud to have been able to participate in this world first. And just like all other calls on Maemo, video calls use the Telepathy framework. We obviously also support Jingle (aka Jabber aka XMPP) and SIP just like the N800 and N810. But we also add H.264 support.

As a side note, my colleague Sjoerd (who now has a blog!) has made VP8 work with RTP. The Googlers are working hard to make some kind of standard. So hopefully, with Google’s clout, we’ll be able to have calls between a fully free platform and a hardware phone!

Lucas Nussbaum: Booting ISO or USB key images directly from Grub2?

2010-05-25T16:29:15+00:00

I’m playing with the idea of booting ISO images and USB key images stored in a disk partition directly from Grub2. That would allow to install Linux or test liveCDs without even using a USB key. It seems that Grub2 has everything needed for that (with a combination of drivemap and chainloader), but I can’t seem to get it working and, as usual with boot stuff, it’s a pain to understand what’s happening.

Has somebody recently tried that, or can point me to a howto?

Alban Créquy: Your contacts on a map with your N900

2010-05-21T12:21:45+00:00

Empathy, the GNOME Instant messaging program, can publish your location to your contacts and show their location on a map as explained on Pierre-Luc’s blog. Can you have the same on your N900? It should not be too much work since all the needed software is available on the platform: Telepathy with XEP-0080 (it works well on most Jabber servers including Ovi, but not Google’s), libchamplain, Azimuth and Map Buddy. But it still needed some integration.

Here it is! You just need to install two packages from maemo extras-devel:

Some screenshots:

Map Buddy with a few contacts

Azimuth configuration in the control panel

Click on a contact and you will be able to start a phone call or an IM conversation.

To debug it, I used the telepathy-ashes Jabber bot. I added the two commands “!setlocation” and “!unsetlocation” so you can see the contact marker moving on the map. You can try it by adding the bot echo@test.collabora.co.uk in your contacts.

If you want to help, join #maemo on Freenode, I am albanc.

Vincent Untz: De la publicité dans le bon contexte

Vincent Untz — 2010-05-21T09:32:00+00:00

Je travaillais tranquillement hier soir quand, soudain, le drame : paf, plus de connexion à Internet. Évidemment, dépendant comme je suis, je pense que c'est la fin du monde, l'apocalypse, le jugement dernier. J'imagine Eyjafjöll qui recouvre le monde entier de ses cendres. Je vois des crevasses s'ouvrir au milieu des villes, des Katrina détruisant les côtes, des raz-de-marée jusqu'au milieu du Canada, la lune qui s'écrase sur notre planète, l'invasion par une race extra-terrestre loin d'être amicale, l'effondrement de notre cher soleil, l'apparation soudaine d'un trou noir, voire le big crunch.

Mais après cet état de panique, je réalise qu'il s'agit simplement de la freebox qui ne semble plus vraiment connectée, même si elle affiche l'heure tranquillement. Naïf comme je suis, je me dit qu'il suffit de la redémarrer. Chenillard lent, chenillard rapide. Tout va bien, on est sur la bonne voie. Puit lent à nouveau, avant de redevenir rapide. Ouf, c'était chaud. Rectangle clignotant, rectangle fixe. Allez, ça va le faire, il y a peut-être juste une petite mise à jour de firmware. Mais... mais... non, rien, on reste sur le rectangle fixe. Convaincu qu'il ne s'agit que d'une erreur temporaire, je réessaie. Résultat identique. Je m'obstine. Sans succès. J'insiste. La petite boîte me nargue. J'envisage des solutions alternatives, créatives, innovantes. Un marteau, par exemple. Mais un bout de raison se réveille et met en doute l'efficacité de la méthode.

Je tombe à genou, j'implore les dieux de toutes les religions. Et à ce moment précis, à la télé, j'entends la publicité : "Il a Free, il a tout compris".

Épilogue: en allant me coucher, je me dis qu'ils ont pensé à gérer le cas où une freebox est bloquée sur ce rectangle fixe et que ça va se débloquer tout seul à un moment. Au réveil, aucun changement. Il fallait redémarrer encore une fois la freebox. Donc, quand cela arrive, soit on débranche la freebox et on doit la rebrancher, soit on la laisse branchée et on doit quand même la rebrancher. Bravo, clap clap clap.

Vincent Untz: GNOME Foundation Elections 2010

Vincent Untz — 2010-05-20T03:17:00+00:00

Next month, the GNOME Foundation membership will vote to elect a new board. It's that time of the year where we think about how the Foundation is doing, where it's going, and who should help run it. Yeah, we all have to plug our brains for a few weeks :-)

I first want to highlight two important points:

as many probably didn't notice, I want to remind everybody that the deadline to announce candidacies is May 23rd. That's next Sunday. You can see the full timeline in the announcement.
the Membership & Elections committee will again do an amazing job organizing the elections. So a big thank to them for their unsung actions!

If you're thinking of running for the elections, then stop thinking: this mere fact is an indicator that you should run. Else, well, think about it now :-) I've written about the job last year and Paul has written about his experience as a new board member. I can only tell you that it's an amazing position to be in if you care about GNOME: it gives you a different perspective on what's going in the project, you get to work with great minds and you can at least slightly influence the project (by working on new initiatives, or deciding how to allocate the money, among other examples). And you do feel rewarded for your work: you can see how it makes a difference.

If, after reading the previous paragraph and the linked posts, you still wonder whether you should submit your candidacy for the elections or not, I invite you to come talk to any past or current board member. And do the same if you have questions or need details about what it involves to be on the board (meeting over phone every two weeks, very active mailing list, action items to complete, etc.). I obviously can't talk for the others (although I strongly suspect they're like me), but I'll make time for you if you contact me about this. It'd be a shame if you don't run because you're in doubt!

As for me, I won't run this year. Although I decided this after the last elections, I actually had to repeat this to myself many times to make sure I really won't run — I have this bad habit of taking this exact decision and then changing my mind at the last minute (usually for a good reason). It's not an easy decision since I care deeply about the Foundation. But it's also because I care that it's the right decision. I've been on the board since January 2006, which is a long time; a long time that makes things feel too much like a daily routine, and that means a break is a good idea. It's also time to leave my seat to some new blood: putting aside the fact that the new board members can easily be pushed to do a lot of work ;-), there's my belief that we should have more different people involved at this level and knowing some of the internals of our community. Good reasons, but difficult decision; it's stupid, but unsubscribing from board-list won't be easy.

I feel the board has been doing a good job over the past few years, which hopefully means I've contributed to that. I could be worried of leaving, but I'm not: there will likely be some continuity thanks to some current board members running, and Stormy is rocking with her job, so the Foundation will most certainly be in good hands. I'll surely miss the constant flow of information (average of 97 mails a week), but on the other hand, it's also an opportunity to try to help the board from the outside, now that I know how things work.

Now, I'm just eager to see who's going to be elected. Aren't you?

Laurent Goujon: En bref...

2010-05-17T21:23:00+00:00

Maintenant que j'ai un compte sur facebook parce que, comme Stan, j'ai cédé à la pression sociale , (mais attention, facebook, c'est le mal, il vaut mieux quitter tant qu'on peut) et plein de nouveaux amis qui sont en fait des anciens amis qui le sont encore mais qui ne le savent pas forcément parce que je ne donne signe de vie qu'à chaque passage de la comète de Halley, il est peut être temps d'officialiser un peu les choses en ce qui concerne mon avenir professionnel et par ricochet mon avenir personnel, voici donc une brève annonce :

Après 5 ans passés dans mon petit village de campagne, où je me suis fait mes premiers amis en même temps que j'apprenais à lire Oui-Oui dans sa voiture jaune, à prendre mes premiers cours de clarinette au sein de l'Harmonie et mes premiers cours de judo qui me valurent tant d'orteils cassés,
Après 7 ans passés dans la sous-préfecture d'à côté (au lieu d'aller au collège de la fôret parce que je me distinguais déjà à l'époque), où d'autres amis ont rejoint les premiers, où j'ai débuté le badminton, j'ai eu mes premiers diplômes et mes premiers voyages à l'étranger (comme l'Allemagne - oui, en Lorraine, l'Allemagne et le Luxembourg, c'est un peu le département d'à côté, l'Italie, la Grèce, la Bretagne) qui sont peut être responsables de mon envie de bougeotte,
Après 3 ans passés à la préfecture (remarquez la progression géographique, à défaut de sociale :-) ), à subir les affres de la classe préparatoire (intenses, certes, mais pas si désagréables), à parfaire mes connaissances cinématographiques, et à découvrir la plus gratuite des bibliothèques privées de France,
Après 2 ans passés à Grenoble à enfin transformer ma passion de l'informatique en mon futur métier, à constituer ma bande de potes (oui, l'informatique, c'est relativement masculin malheureusement), à vouer un culte à la wrapette,
Après 1 an passé chez nos cousins québécois, parce que le sirop d'érable (et les cowboys fringants), c'est trop bon, et bien plus loin que l'université de Karlsruhe, parce qu'à présent je peux dire "Oui, j'ai fait Polytechnique" et "J'ai survécu par -30°C",
Après plus de 6 ans passés de nouveau à Grenoble pour commencer ma carrière professionnelle chez un site de comparaison de prix, puis chez un major d'Internet qui a décidé malheureusement de fermer son site de développement, à comprendre que les montagnes, ca peut servir à plein de choses différentes, à voyager à l'étranger et notamment au Japon, à tenter peut être de comprendre le sens de la vie,

Bref, après toutes ces années, si je continue mon aventure chez Yahoo!, j'ai décidé de quitter la France, de traverser un océan et d'aller m'installer près de San-Francisco en Californie, dans cette région que l'on nomme Silicon Valley. Pour l'instant, je ne sais pas encore quand je pars exactement (très certainement cet été), je n'ai aucune idée de combien de temps je vais y rester, tout juste ce que je vais y faire :) Je sais que je vais manquer pas mal de choses (parce que la distance physique n'est pas moins présente lorsqu'il existe un lien virtuel) mais bon, la vie (la mienne en tout cas) est ainsi faite, et je compte bien garder un œil sur ce qui se passe en France !

Pour les nouvelles, en plus du mail (soyez indulgents pour mes réponses tardives), du téléphone, de facebook (oui, c'est pour cela...), il y aura bien sûr ce blog pour des articles détaillés comparant les deux cultures...

Finalement ce n'est pas un au revoir, puisque nous ne nous quittons pas vraiment...

PS: Une tournée exceptionnelle avant mon départ sur l'autre continent avec plusieurs dates en province est bien prévue, don't worry...

Lucas Nussbaum: Receive Ubuntu bugs by mail with the Debian PTS

2010-05-14T15:00:23+00:00

It is now possible to subscribe to Ubuntu bugmail for the packages you care about, without having to use Launchpad (and subscribe on a per-package basis there). This is implemented as a new opt-in Package Tracking System keyword: derivatives-bugs.

To subscribe for all your packages, use keyword [email] + derivatives-bugs (as documented in the Developers Reference). You might also want to subscribe to derivatives (Ubuntu diff, etc. also opt-in).

Of course, if other derivative distributions are interested in providing such data, don’t hesitate to contact me or the Debian QA team.

Also, if you are like me and never remember about subscribing to packages you maintain, you can use that UDD script to check for missing subscriptions.

Vincent Untz: Marketing Hackfest: Day 1

Vincent Untz — 2010-05-05T10:18:00+00:00

It looks like I'm good at blogging about the first day of a hackfest and then not continuing that, so I'll continue this trend ;-) I just want to state publicly that I have a few GSettings-related posts in mind to write, though: schema, gconf backend, porting your application, etc., so now I'll have to deliver those posts about the results of this amazing GSettings hackfest!. But I am now in Zaragoza, attending the Marketing Hackfest, so let me write a bit about it.

Andreas hard at work by Licio Fonseca

Sumana wrote about the first day quite extensively, so I won't repeat here what she wrote: just go read her post! We're working on the plan and roadmap for the 3.0 launch, but we're not just about the high-level ideas: we're working on design and content (of websites, brochures, etc.), so we'll have results to show. And don't hesitate to send us feedback about what you're reading in blogs or on the wiki: you can leave a comment here, send us a mail, join #marketing on IRC — there are many ways to reach us!

It's exciting to see the whole plan and the many ideas, and here a few things I want to highlight (obviously, much more is worth highlighting!):

Marketing Roadmap: having a marketing plan is good and already makes me happy. Turning the plan into a roadmap is just the logical next step to make sure everything gets executed.

GNOME 3.0 Website: there'll be a specific GNOME 3.0 website to introduce this new version of GNOME, and get people excited about this new version. In the long term, the content will be moved to the main website, but we feel a separate website is the best way to build momentum for the 3.0 effort. The target audience is existing GNOME users and there is already a good sitemap. Work is ongoing for the exact content and design, and the hard work will be the creation of videos. If you're interested in helping there, raise your hand :-)

GNOME Ambassadors: we're preparing materials to help everyone talk about GNOME at events, or at a university, inside a company or just to friends. We've always said that anyone can help represent GNOME like this, but it's a hard task if you have to start from scratch. With talking points, slides, a template for new presentations, business cards, a great shirt for ambassadors, we want to lower the barrier here and help all GNOME enthusiasts share their love for the project.

Zaragoza is really a fantastic environment to do the hackfest, so a big thanks to all the organizations that are sponsoring this event: the Zaragoza Municipality, the Aragon Regional Government, the GNOME Foundation, the Technological Institute of Aragon, ASOLIF and CESLA. And a personal thank to the Foundation for sponsoring part of my travel and to Novell for letting me attend this event :-)

Time to go back to hackfest work! Oh, and again, send us feedback and join #marketing!

Lucas Nussbaum: “But why isn’t Debian using Launchpad?”

2010-05-03T18:49:59+00:00

Due to my work on Ultimate Debian Database, I’m sometimes asked why Debian isn’t using Launchpad.

First, “using Launchpad” can mean two different things.

The first possibility is using Canonical’s instance of Launchpad. That would mean creating a Debian project on launchpad.net, and using Canonical’s infrastructure. Well, that’s clearly not a good idea. We (Debian) do not want to depend on Canonical to fix bugs or make enhancements that we require to improve Debian. For example, Canonical imposes the use of the Bazaar Version Control System in Launchpad: you simply can’t use Git instead (git-bzr hacks don’t count). We want to stay in control of our infrastructure, for obvious reasons.

So the other possibility would be to setup our own instance of Launchpad, given that Launchpad is now Free Software. However, it is not clear if it is actually possible: I was told by a Launchpad developer that they didn’t know of any external (outside Canonical) installation of Launchpad.

Even if this was possible, it is not clear at all that the Ubuntu infrastructure is superior to the Debian infrastructure. The Debian infrastructure has many nice features that are missing in Launchpad, for example version-tracking in the Bug Tracking System, which allows to track (by parsing the changelog) the versions of a package where a bug has been fixed or not (example with iceweasel).

So, when switching to Launchpad, we would have to reimplement quite a lot of needed features in in, with no clear benefit: the Debian infrastructure works fine, and is actively maintained.

It’s also interesting to note that while the Ubuntu infrastructure is centered on Launchpad, there are quite a lot of external services that are not integrated in Launchpad: the Ubuntu popularity contest, merges.u.c, patches.u.c, the various services on qa.ubuntuwire.org and qa.u.c, etc. With the Debian model, it is very easy to add a new service and get it integrated with the various dashboard (Debian Developer’s Packages Overview, Packages Tracking System). Within Ubuntu, those external services are really second-class citizens. All in all, the infrastructures of the two projects reflect their organizations: bazaar model for Debian, with an emphasis on collaboration between the services, controlled by Canonical for Ubuntu.

Lucas Nussbaum: Castles in the air

2010-05-03T18:45:23+00:00

When people ask me why I’m so fond of “computers”, I already answer that it’s like being able to build very large buildings or bridges, super-fast cars, etc without having to care about buying the raw material needed, or about the consequences: computers are like a giant Lego box which is only limited by the programmer’s abilities.

What I discovered today is that there’s a quote from Frederick P. Brooks that says about the same thing:

“The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures.”

Éric Pignet: Neposync, to synchronize Nepomuk with files metadata

2010-04-29T22:13:40+00:00

UPDATE: project moved to github, links updated. Plus, new post about new features of neposync.

With KDE SC 4.4 and integration of Virtuoso in distributions, semantic desktop is no more a futuristic project but a reality: I tested tagging, rating, filters in Gwenview, searches in Dolphin, all works fine.

But before starting the long work of tagging my gigabytes of photos, I wanted to be sure the work would not be lost if I change my computer or my distribution. The problem is that there is no utility to backup/export the Nepomuk Virtuoso database at this time. ^[1] ^[2]

So I decided to write a simple tool to:

read tags/ratings from Nepomuk and store them in files metadata (same metadata used by Digikam)
read tags/ratings from files metadata and store them in Nepomuk

This is a command-line tool very easy to use. You just cd to a directory containing images tagged/rated via Dolphin or Gwenview and you type:

neposync --nepomuk-to-files

That's it: all tags/ratings for images in the current directory are now stored in files metadata and will never be lost. If you copy these images on another KDE powered computer, you just have to type:

neposync --files-to-nepomuk

to fill Nepomuk database with your valuable manual work.

The tool also allows you to display all tags/ratings stored in Nepomuk, or to clear them (see usage below).

Download

Neposync is a simple Qt C++ program, using KDE libs. At your choice, you can:

download the source tarfile: neposync-0.2.tar.gz
To compile, just type qmake && make
retrieve git sources: git clone git://github.com/ericpignet/neposync.git
install the ArchLinux package from AUR: just type yaourt neposync

That's all for now.

Please tell me if you use the tool !

Usage

The full usage of the tool is:

Common usage:
  neposync -nf OPTIONS.. DIRECTORY
  neposync -fn OPTIONS.. DIRECTORY
Actions:
  -nf, --nepomuk-to-files    Read tags/ratings from Nepomuk and store them in files metadata
  -fn, --files-to-nepomuk    Read tags/ratings from files metadata and store them in Nepomuk
  -dn, --display-nepomuk     Display all Nepomuk tags/ratings
  -cn, --clear-nepomuk       Clear all Nepomuk tags/ratings
Options:
  -r   --recursive           Recurse into sub-directories
  -f   --force               Copy tags/ratings even if empty on source side
  -V   --verbose             Display all nepomuk output (depending on KDebug settings)
  -h   --help                Display this usage information
DIRECTORY is optional, if absent the current directory is synchronized

Remark: neposync uses IPTC 'keyword' metadata to read/store tags in files (as Digikam)
        neposync uses XMP 'Rating' metadata to read/store ratings in files (as Digikam)

Notes

[1] I mean, nothing reliable. Save my soprano-virtuoso.db file is not option: nothing guarantees that if some files/configs are different on the new installation, nepomuk will not show an error at startup.

[2] There is a GSoc project, but who knows when something reliable is released.

Éric Pignet: Au revoir et merci Kubuntu, bonjour ArchLinux

2010-04-29T21:16:49+00:00

Voici près de 4 ans jour pour jour que j'ai écris mon dernier post sur ce blog, il concernait le futur de Kubuntu.

Je serai resté environ 5 ans sous Kubuntu en tout, et je dois avouer c'était un plaisir. Pas une seule réinstallation complète pendant ce temps, juste des mises à jour. J'ai fait beaucoup de choses pendant ces années et le plaisir justement, c'était de ne pas avoir à me soucier de mon système d'exploitation, de juste l'utiliser.

Cependant il y a quelques semaines une conjonction de faits m'a convaincu de donner sa chance à ArchLinux:

un nouveau disque dur avec plein de place dessus
quelques soucis mineurs sur Kubuntu (les vidéos Flash HD s'affichent... toutes roses!)
l'envie depuis toujours de tester une distribution en rolling release (toujours des logiciels à jours, et pas de mega-update risqué)
pas mal de bon commentaires concernant ArchLinux sur LinuxFR
le test très convainquant du LiveCD Chakra-project, basé sur ArchLinux

J'ai donc installé sans difficultés ArchLinux avec KDEMod, grâce aux wikis français et anglais. La configuration est manuelle mais c'est très relatif: quelques paquets à installer (X, alsa, UDev, HAL...) et deux trois fichiers de configurations... que de toutes façons j'avais aussi dû modifier sur Kubuntu.

Je ne vais pas faire une présentation d'Arch, c'est facile d'en trouver sur Internet. Mais ce qui m'a frappé une fois que j'avais mon bureau KDE configuré, c'est que... Nepomuk était parfaitement fonctionnel et rapide, ce qui n'avait jamais été le cas sur Kubuntu. Ca apporte vraiment un gros plus au bureau: que toutes les applications partagent les mêmes tags/notations de fichier, pour par exemple rechercher facilement toutes les photos de son chat depuis le gestionnaire de fichiers... La raison est simple: ArchLinux package le backend Virtuoso, fiable et rapide.

Si j'ai écrit ce billet, ce n'était pas à l'origine pour parler d'ArchLinux mais plutôt pour introduire le billet qui va suivre, concernant Neposync.

Vincent Untz: GSettings Hackfest: Day 1

Vincent Untz — 2010-04-13T13:27:00+00:00

Yesterday was the first day of the GSettings Hackfest! Ryan, Matthias, Colin, David and I were locked in a meeting room for the whole day (okay, we went out for lunch and Matthias had to leave afterwards) and we put our brains to good use. Or at least, that's the feeling I got ;-) But first, let me thank the various companies who are helping this hackfest: Novell is sponsoring and hosting it, and Red Hat and Codethink are sending folks here. This hackfest will most certainly make a difference on our road to GNOME 3.0, and the support of those companies is a great contribution! And obviously, without the Foundation support, the event wouldn't have been possible, so here's lots of love from the participants to the Foundation too :-)

We spent the morning planning and discussing various topics, and the afternoon was more like a coding session. Unfortunately, we didn't take any fancy picture, but we'll try to do a better job now. Matthias put some notes online, and here's my attempt to summarize the day (with probably a few errors here and there...).

Emma's Pizza by afagen (Creative Commons by-nc-sa)

Overview

Ryan gave a general overview of GVariant/GSettings/dconf. Here's a quick summary:

GVariant is the part that landed in glib 2.24 (released at the same time as GNOME 2.30). It's a datatype for values of a type that you specify, and which can be simple, or relatively complex (something with a mix of arrays, tuples, dictionaries, strings and integers, for example).
GSettings is an API to access settings. This is the main focus in this hackfest.
dconf is what will store the settings on the disk, and it's a backend for GSettings. So it's actually only an implementation detail; there's also a simple memory-based backend that makes it easy to test GSettings without dconf.
There's also a GObject serializer that exists in a branch, but it needs to be reviewed and it's not something that is blocking anything major.

So what's important in there for developers? The GSettings API is what you should care about, and it's relatively straight-forward:

/* Get settings associated with the org.gnome.hello schema. We now specify
 * directly which schema we want, instead of just a path like in gconf. */
settings = g_settings_new ("org.gnome.hello");
/* Fetch a tuple of integer that are stored together (instead of using two
 * distinct keys, like in gconf). */ 
g_settings_get (settings, "preferred_size", "(ii)", &width, &height);
/* Set a string-typed key. */
g_settings_set (settings, "username", "s", "Rupert");
/* Bind a setting to an object property. */
g_settings_bind (settings, "show_picture", image, "visible", G_SETTINGS_BIND_DEFAULT);

There are already two modules with a gsettings branches: devhelp and gedit. While they probably won't work straight away with the final GSettings, it certainly helps get a better view of what porting involves. Unfortunately, a few things need to be completed before GSettings is usable again, which makes it not really fun to do some port right now. But things should be better really soon now.

For distributors and sysadmins, knowing a bit about dconf will still be important since this is where the settings will be stored, and this is the part the will be used to implement non-schemas default values or mandatory values.

Timeline

We obviously discussed planning, and one explicit goal that was set is to merge GSettings in glib at the end of the week. We'll see how it goes, but that's definitely doable since it's not that big.

There's the question of whether all of GNOME can be ported to GSettings in time for GNOME 3. I do hope it will happen, but we'll certainly know more at the end of the week once we've started porting applications using gconf in interesting ways.

Schemas

While there's already support for schemas, it's not set in stone yet and it can be improved in various ways. Among the things we discussed:

The current format is a really simple format that is easy to write and parse for human eyes, but it's not flexible enough to do everything we need. So we worked on a complete XML format, which is still relatively intuitive. However, we expect to make it possible for developers to use the simple format and compile it to a XML file with a small utility during the build.

The schemas are compiled in a database, that will only contain the default values and potential constraints about the values for a key. So if an application wants to access the description of a key (which is the exception, not the usual case), it will have to parse the XML files for this.

Translations of the descriptions will be fetched with gettext, since they will already be in the .mo files and there's no need to duplicate this information.

How to handle localized default values. This is useful for various settings (clock format, default search engine, etc.), so it's definitely something we want to have. Application developers will have to explicitly mark a key as localizable. We're still debating whether all types of settings should be localizable, or if it's only strings. So don't hesitate to share with us good concrete example of non-string settings that should have a localized default value!

While there are still open questions, we made good progress on this, which will enable us to move to other topics quickly.

Configuration Migration

Migration of configuration is a tough topic, and we're unsure what's the best approach here. We quickly brainstormed about some possibilities:

An easy solution would be to just do nothing. It might look brutal at first, but the gconf schemas that are defined by applications today are often suboptimal in various ways, and maintainers wouldn't be unhappy to be able to change a few things here and there. Also moving to GNOME 3 can be seen as an opportunity to do a clean break. But we already know that this would be annoying for users.

The other extreme solution is to migrate all the gconf database at once. The issue with this, though, is that it assumes that applications stop using gconf at the same time, which is not going to happen: we don't have control over all the applications that are used by users. So a user might change the settings of an gconf-based application after the migration has been done, and those changes will never get migrated, even if the applications gets ported later.

An approach where it's up to each application to signal when to migrate its data (and maybe even which part of the data to migrate, with a file mapping gconf keys to GSettings keys) is a third alternative. It looks relatively attractive, but it also has a simple issue: what happens to the shared settings, like everything living under /desktop/gnome?

So no obvious magic solution (surprise!), and we clearly need to think more about it this week.

Best Practices

It's a topic that came up more than once. We certainly need to define some best practices on how to write schemas (how to name keys, what should be in the description, etc.) and as to when to use GSettings. For the schemas best practices, we can certainly look at what is recommended for gconf, although there are requests to change a few things (prefer dash to underscore, for example).

When to use GSettings is a fun topic: it's really something that should be used to store settings, and not state. So the position of a window, for example, would not be appropriate to store in GSettings. However, without a good API to store transient data, it's likely that GSettings will get abused for this like gconf is being abused. And it seems we don't all agree on what is a setting and what is transient data: having an expander open is an interesting case where Ryan and I are happy to disagree :-)

D-Bus discussion

Hrm, okay, I didn't listen too much to that part of the discussion, so I have nothing really interesting to write about it. But with Colin (who doesn't admit yet he maintains D-Bus) and David (who's writing gdbus) together, there was probably insightful opinions :-) The good news is that gdbus should be ready soon, and I heard some talks about porting gvfs to it...

Hacking

So as you can see, there were a good number of topics discussed. But we slowly turned to our editors after lunch: David focused on gdbus; Ryan worked on GHashFile, an API to store data on disk, which will be used by dconf; Colin progressed on GtkApplication; I did some stupid work to save GSettings stored in the memory backend to keyfiles.

So what happens today? We'll see when the hackfest begins, but it looks like we'll be able to use GSettings again, at least with the memory backend, which will make it easier to review the GSettings branch and start porting applications.

Lucas Nussbaum: Apply for the Google Summer of Code at Debian even if you are already a Debian Developer!

2010-04-05T07:02:44+00:00

The Debian GSOC admins have made it clear that it is possible for DDs to be selected as GSOC students (even if people who are not Debian contributors will be prioritized). So, if you are a student, a Debian Developer, and interested in getting paid to work on Debian during the summer, it’s a very good idea to apply! For the details, see this blog post.

Note: the goal of this post is not to start a flamewar, but to make sure that everybody is fully aware of the unrestricted selection process. Since we are going to accept DDs as students anyway, let’s at least try to get the best applications.

Alban Créquy: D-Bus debugging: how to use D-Feet on N900

2010-04-01T12:47:31+00:00

To debug problems related to D-Bus, I like to use dbus-monitor and graphical tools D-Feet and Bustle. But until now, I couldn’t use D-Feet on my computer and connect to the bus on my N900 because dbus-daemon only listen on UNIX socket and listening on TCP does not work. Bustle works around the problem by using two different tools: one on the N900 to save the D-Bus traffic in a file and another one on your computer to read the file and display diagrams.

I implemented dbus-daemon-proxy which redirects all the traffic through TCP. There is no authentication, so use this tool only on network you trust! dbus-daemon-proxy is meant to run on your N900 and connects to the local bus (either session or system) and listen on a TCP port. Then you can run D-Feet or dbus-monitor on your computer and let them connect to dbus-daemon-proxy using TCP.

Step by step:

Get the sources:

git clone git://git.collabora.co.uk/git/user/alban/dbus-daemon-proxy

Compile it in scratchbox and copy the binary to your N900
Run it on your N900:

./dbus-daemon-proxy --system

Start D-Feet on your computer, use the menu File->Connect to other bus and type something like “tcp:host=myphone,port=8080,family=ipv4″:

Enjoy D-Feet!

Vincent Untz: Enjoy GNOME 2.30!

Vincent Untz — 2010-03-31T21:19:00+00:00

Amazing banner for Two Thirty by Andreas Nilsson

It's out and it's good :-) Go read the release notes to get more details about 2.30! You know the drill now: this release is already included in the development branch of most distributions, and you'll see it in stable distributions released in the next few months.

I've thought hard about it and after careful consideration, I'm positive that my favorite change in this release is the redesigned Swell Foop (previously named Same Gnome). Sure, it's neither the most visible change nor the most useful one, but the new clutter-based engine for this simple game makes it really addictive!

If you use openSUSE Factory, GNOME 2.30 is already available from the GNOME:Factory project in the build service, and I pushed it to Factory today, so it'll be in the next milestone. But there's more! I really love the fact that we're able to easily ship the latest releases of various applications for our stable openSUSE release. Yes, that means that if you're an adventurous openSUSE 11.2 user, you can also play with it today! There are instructions for 11.2 users on the wiki, but please do read the warning at the top of the page :-) The GNOME team will work a bit on it to make sure it's all stable so that non-adventurous users can also enjoy it!

Many thanks to everyone involved in this release, especially to the various people who helped for this release in the last few days — there were more late tarballs than usual, for example, but we still managed to get 128 new tarballs compared to 2.29.92 (and I ended up rolling 30 tarballs myself, a new world record!). And my good friend Andreas saved my world again with his 2.30 banner :-)

Now let's have an ice cream party!

Vincent Untz: desktop-file-utils news, and an easy way to contribute

Vincent Untz — 2010-03-15T17:04:00+00:00

A few weeks ago, I migrated desktop-file-utils from CVS to git, but after pushing it, I realized I could have done the migration in a slightly better way. Ouch. Enters one hero, Tollef: he was kind enough to allow me to kill the old git repository and start from scratch. This means desktop-file-utils finally lives in git. Woohoo!

It enabled me to commit various patches I had done locally in the meantime (I really didn't want to use CVS again, so I was waiting for git ;-)), and then to release desktop-file-utils 0.16. It's the first release since February 2008! Two years without a tarball is quite bad, especially since there were fixes waiting in CVS. But everything is good again, and we should now be back on track, with more frequent releases.

There are a bunch of changes in this release, including improved checks when validating a .desktop file. Of course, there's always the risk that this will result in files that are now invalid while they used to be marked as valid, but the new future error type of warnings should mitigate this. The other good news is that there's only one enhancement request opened in bugzilla, and I'm not even sure there's something we can do about it. But I'm confident you've already find a bug, so don't forget to file it ;-)

It all looks perfect, doesn't it? Well, there's one big thing missing, though: a regression suite. I still can't believe that we're releasing a validator for .desktop files without a regression suite, and I'm convinced there have been regressions in the past (or even in this release) that went unnoticed. I'd really love to have a few people help create tons of .desktop files that would stress the validator and make sure it validates what the specification says. It's an easy way to contribute: it just requires free time and understanding of the specification. Please contact me if you want to give it a try!

Laurent Goujon: Encoding FAIL!

2010-03-15T11:03:00+00:00

Ami programmeur, sauras-tu trouver les deux erreurs d'encoding qui se cache dans cette image ?

Lucas Nussbaum: RC bugs of the week

2010-03-13T19:36:43+00:00

I just couldn’t resist… I joined the game, but did it the other way around.

I could only file 51 new FTBFS (Fail To Build From Source) bugs this time. Looks like Squeeze is getting closer!

I’ve also been doing rebuilds of Ubuntu lucid. There are currently 561 packages that fail to build from source in lucid/amd64, versus 430 in sid/amd64 (I will start rebuilding squeeze instead of sid after the freeze). Surprisingly, only 131 packages fail in both. I would have expected that number to be much higher.

Vincent Untz: Help GNOME be present at Idlelo, in Ghana!

Vincent Untz — 2010-03-08T23:20:00+00:00

A few weeks ago, the GNOME Foundation has been contacted by the organizers of the Idlelo conference in order to get a GNOME presence during the event. Quoting the website of the event:

IDLELO is one event for FOSS practitioners, developers and advocates as well as governments to showcase results, share experiences and challenges, review progress on the continent in diverse domains and chart a way forward for an African future grounded in true ownership of technology. IDLELO is therefore a premier international forum for the presentation of research results in Free and Open Source Software (FOSS) in Africa.

The event will occur in May, in Accra, Ghana.

There have been many discussions in the past about how to get more community involvement in Africa, and there's no magical solution. But a good first step is, for sure, to be present at events that are being organized on the african continent. We're already sending Luis de Bethencourt to FOSS Nigeria, and we want to be at Idlelo too.

If everything goes well, the amazing Fernando will go deliver training sessions before the conference itself; but we need one more person to man a booth during the conference. While this is not a hard requirement, we'd still like to have a GNOME Foundation member who feels empowered to talk in the name of the Foundation. If you're interested in representing GNOME at Idlelo, please get in touch with the board. I'm sure you'll enjoy it!

Vincent Untz: Tidbits from the Usability Hackfest

Vincent Untz — 2010-03-08T02:15:00+00:00

If you're still wondering what happened during the Usability hackfest, then you clearly missed a lot of blog posts. The good news is that you can catch up with all the links being collected on the Hackfests, or you can cheat and go read Máirín's coverage, since she did an amazing job writing about what was being discussed.

I was there only for the last two days; the original plan was to attend a bit more of the event, but the travel from France to London took an unexpected 12 hours. I still had some good and useful time there, that I mostly used to get a good overview of what people are working on, and how this can be integrated in a GNOME roadmap. Here are some highlights:

While I missed the discussion about nautilus, it seemed most people at the hackfest agreed on streamlining the nautilus user interface. I'd love to try the prototypes that were worked on: most of the proposed changes make sense to me. But getting rid of tabs and/or the split view will certainly trigger various reactions, and that's something that we cannot ignore...

Thomas je parle français couramment Wood was kind enough to let me use his laptop charger nearly all the time — I had one, but not for the right laptop...

Charline reported about a usability review of empathy, and this was definitely instructive. It's always fun to look at a user interface and finds what's wrong and what can be improved. In some way, it reminded me of some usability reviews that the usability team was doing for various applications a few years ago. That's an effort that we've been missing lately, and I'd love to see someone revive this!

The work on the new control center seems to be moving along nicely. We should see the results in the next development cycle; don't be afraid to help Thomas if you're interested in this!

While discussing preferences, and removing some of them that we think most (as in a huge percentage) people don't use, we mentioned the fact that when we remove some settings from the various configuration tools, a lot of people get unhappy, to say the least. This is understandable, but we also always pointed out that it should be easy to write a small tool to enable people to change those settings graphically again. That never happened, but we'd like to avoid further unhappiness. This is how the idea of GNOME Plumbing was born. And I foolishly proposed to implement this.

It was funny to see Garrett breaking his openSUSE installation. Except that it shouldn't break this way when using GNOME:Factory on 11.2. Oops.

I had a good chat with Jon about GNOME 3. There's so much we can deliver during the whole GNOME 3.x cycle... We're focusing on 3.0 right now, but we need to prepare the following releases too. It was motivating to get reminded of the various areas we should explore, and motivation is something that was most welcome :-)

It was good to catch up with Lucas, just a few days before Julia magically appeared :-) He's still one of my heroes.

On Friday morning, Bastien told to Mairin, Garrett, Jakub and Hylke: okay, you want tools for designers; we're a bunch of hackers here, but we need you to design the tools you need. This resulted in a good discussion. Except that now, we really need some people to sit down and implement this. I guess this could be an interesting Summer of Code project!

Seeing Willie get hopes for usable accessibility support in GNOME Shell was a real pleasure. It's been a hard topic for months, and knowing that there might be some light at the end of the tunnel is already good news.

Matthew invited me to a card sorting session about settings and how to group them. It was a new experience for me, and seeing someone struggle to organize settings was eye-opening: I got the feeling that even with just one person doing this seriously, we can improve the overall experience for many users. I'm intrigued how usability people deal with different people having conflicting behaviors, though.

Many thanks to Canonical and Google for sponsoring this hackfest, and also thanks to Klaas and Novell for letting me go on a short notice :-)

I have high hopes that putting all those designers and usability people in one room together during one week will also make the GNOME Usability team move forward again. Usability is an essential part of our DNA, but we've been slowing down our efforts there, instead of accelerating as we should have done. This hackfest should put us back on track!

Lucas Nussbaum: Ruby release blockers for Lucid and Squeeze

2010-03-07T09:58:19+00:00

For the first time since I got involved in Ruby maintenance in Debian & Ubuntu, we are seriously at risk of not being able to release working Ruby interpreters in both Ubuntu Lucid and Debian Squeeze, because of two pretty serious issues.

Ruby 1.8(.7.249) randomly hangs with eglibc 2.11

That issue was found by Google folks, because Puppet was hanging. After a lot of (quite heated) discussion, it was found that the problem is caused by something in eglibc 2.11: the problem can’t be reproduced in a Debian unstable chroot (with eglibc 2.10), but is reproducible if you just upgrade glibc to 2.11 (which is in Debian experimental).

It is not clear at all whether it is a glibc bug, or a ruby bug: Ruby has shown in the past that it was making some assumptions on the behaviour of pthread. It is possible that a valid change in glibc conflicts with an assumption made by Ruby.

Still, I wonder why Ubuntu chose to release with eglibc 2.11, while Debian still only has 2.10 in unstable, and Ubuntu doesn’t really have a lot of people with deep glibc knowledge. (Update: I assumed we would release squeeze with 2.10, but the eglibc maintainers plan to release 2.11 in squeeze.)

That issue is tracked in Launchpad as bug 520715 (which was reassigned to eglibc), and in Ruby’s redmine as bug 2739. Debian Squeeze isn’t affected by that issue, but we are likely to get bitten as well after Squeeze if a solution isn’t found by then.

As Ruby maintainers in Debian/Ubuntu, we can’t do much about this issue, because it requires either a lot of glibc knowledge, or a lot of understanding of the Ruby threading code.

Ruby 1.9(.1.37{6,8})’s test suite hangs on Sparc

The development branch of Ruby (declared stable by the interpreter developers, but not considered as such by the third-party libraries developers) also has interesting issues. Its test suite hangs on sparc, but only (apparently) on specific CPUs/kernel versions. Here again, it is not clear whether it is a Ruby issue, or a kernel issue, for the same reasons as above. It is also possible that it is fixed in Linux 2.6.32, but the Debian build daemons run the lenny kernel, so we can’t check that. This is tracked as Debian bug 565765, and is not tracked in Ruby’s redmine, because Sparc is not supported by the upstream Ruby developers.

This issue really requires Sparc knowledge (and access), so as Ruby maintainers, again, we can’t do much, besides coordinating and poking the various people that can help.

Lucas Nussbaum: Check your PTS subscriptions with UDD!

2010-03-01T21:21:24+00:00

The Debian Packages Tracking System has a great feature: you can subscribe to packages that matter to you, and be informed of all uploads, bugs, testing migrations, etc.

However, when (co-)maintaining a lot of packages, it is easy to forget to subscribe. And then you might miss important information about your packages (uploaders don’t receive bugmail by default, for example).

Since PTS subscriptions are now imported into Ultimate Debian Database, it is easy to find out if you missed some subscriptions. It’s just a matter of going to http://udd.debian.org/cgi-bin/pts-check.cgi and entering your email!

And for those concerned with privacy, it should be noted that the unauthenticated access to UDD only gives you the hash of the subscribers’ emails. You need to be a DD, and use the guestdd account to see the email addresses (which DDs can already see on master.d.o).

Lucas Nussbaum: Phone number change

2010-02-24T08:28:55+00:00

My phone number changed. If you have the old one, substract 25898392 from it and you will get my new one!

Vincent Untz: London, here I come!

Vincent Untz — 2010-02-24T05:31:00+00:00

I'm going to the Usability Hackfest in London today! Seeing the pictures on Máirín's post (more pictures) makes me feel it's already going quite well, and I'm eager to sit down and listen to clever people.

I'm saying I'm going, but I should probably say that I'm supposed to go: there's a strike in french airports and yesterday, I learnt that the airport where I'll take the flight to London is supposed to be closed. At least the flight wasn't cancelled. Yet. Oh well, I guess we'll see how it goes ;-)

Update: of course it happened. Flight got cancelled while I was on my way to the airport. After some challenging times (they had no computer working because of bugs), I'm now at another airport, waiting for a flight in the afternoon. But I'll make it :-)

Vincent Untz: Vincent's story about FOSDEM

Vincent Untz — 2010-02-23T22:06:00+00:00

I'm back from FOSDEM. Okay, I've been back since two weeks, but I still wanted to write a few words about the event.

In one sentence: it was a blast! Hardly a surprise, though, since it has always been a great event. But FOSDEM is not just about the conference: it's also about waffles and french fries (no beer for me, thanks ;-)). Oh, and people too: with my good friend Andreas, we went to the Belgian Comic Strip Center on Friday afternoon, where I learnt some cool facts about our beloved bandes dessinées; I had dinner with the GNOME french-speaking cabal on Friday (we all enjoyed the really good food), and with crazy openSUSE people on Saturday; I discussed about PhD thesis with Kris and Christian during the beer event; etc. I missed Lucas, though — but he had a good excuse to not come.

My experience of FOSDEM itself was different this year: I had planned to have meetings or chat with many different people, and it did happen. But I didn't realize that it'd make me that busy... Between GNOME Foundation-related meetings, a release team meeting, discussions about accessibility, translation infrastructure, GUADEC or GTK+, and the last-minute slide writing with Anne and Frédéric, I felt a bit short in time. And exhausted after one day.

GNOME

I loved our GNOME presence during the event. It was really amazing to see so many different people step up to help with the organization and the booth, even though we really could have organized the whole thing better. The t-shirts were nice and people seemed to like it, although a few people commented that the art was printed a bit too big. The stickers were also popular, and that's understandable; still, we had many stickers remaining at the end, but they'll go straight to an event in Nigeria. I sent a small report to foundation-list with more details about how it all went.

Footsteps in the hall ... by Itkovian (Creative Commons by-nc-sa)

Of course, Christophe tricked me into doing the opening of the GNOME devroom: he pretended he was stuck in some tramway, far away from the venue. But if you looked carefully, you could see him on the booth during the opening! Never trust french people ;-)

During a meeting on Saturday afternoon, Christophe called me to ask about the group photo. I look at the time and, hrm, well, it was supposed to happen at that exact moment. There was only this tiny issue that I was 5-10 minutes away from the venue. Apparently, everybody else had forgotten too; but still, I was supposed to be responsible for that. I guess you should really never trust french people! But I managed to sneak in the KDE group photo, though.

openSUSE

It was good to see the boosters again, although it was way too short. One thing I really liked about the openSUSE booth is that we had some nice big touchscreens. And they really help attract people: just put some nice game or something that looks good, and people will start playing with the computer.

The booth setup by Henne Vogelsang

For some reason, some people made fun of me because of my talks, which were interactive session. Because I was running everywhere to give the microphone to participants. However, the real person to blame there is Richard who deliberately chose to sit in the worst seat for me ;-)

The talks themselves went well. Anne and I expected to see more doubts raised about the collaboration between distribution for translation of package descriptions, but maybe we were a bit pessimistic? As for the GNOME upstream/downstream discussion, it made me realize how large the gap between upstream and downstream can be and I hope it also helped the downstream and upstream contributors feel this gap, which is the first step towards a better world. I was surprised to see some GNOME maintainers not knowing about distributor-list, for example.

It was really a busy week-end, and it's amazing how productive those two small days can be: I came home with new ideas, new plans and lots of motivation, which is always good!

Vincent Untz: A few words about cups-pk-helper...

Vincent Untz — 2010-02-19T16:52:00+00:00

It looks like I succeeded in never promoting cups-pk-helper... Let me try to fix this so that more distributions start to look at it :-)

One year and a half ago, for openSUSE 11.1, we wanted to make it easy to configure printers. So naturally, we integrated system-config-printer since it works well, is well-maintained, and is adopted by other distributions. However, the security team didn't want to make the default cups configuration too permissive (for good reasons), and it resulted in lots of root password prompts by default, which is not so cool for end-users. And we thought: So if we don't want to make the whole cups configuration permissive, maybe we could have a mechanism to have fine-grained privileges... There's this cool little project called PolicyKit that could help. This is how cups-pk-helper was born.

We could of course have tried to push this solution in cups itself, and to be honest, this is what would make most sense. However it would have required much more effort: nobody wants a patch that wouldn't get accepted by the cups team, and the cups team would certainly require this feature to work in a way that would make it implementable on other operating systems. And I didn't feel ready for such a battle.

So I went ahead with the small helper, and after a few hours of hacking in September 2008, there was already some working code and a patch to make system-config-printer use this. A few bugs later, it all went in openSUSE. At some point, Tim Waugh accepted the system-config-printer and Fedora also started using cups-pk-helper. This is also when Marek Kasik started working on cups-pk-helper, implementing some additional features.

Fast-forward to today. I've just released cups-pk-helper 0.1.0, and I'm hopeful that the code will move to git.freedesktop.org really soon now.

So what kind of fine-grained privileges do we offer? There are actions for editing local printers, remote printers, classes, jobs you own, or jobs you don't own, as well as simpler actions like the one to enable a printer (something you might want to allow without allowing the edition of a printer), or a low-level action that can be used to upload/download a file to/from the cups configuration. We're trying to be relatively flexible, while still limiting the actions to what we believe is really useful. What we have right now looks relatively reasonable, but it's certainly also wrong in some ways. We just need feedback to know how it's wrong ;-)

To make it easy to integrate cups-pk-helper in system-config-printer, the D-Bus API is based to a large extent on the pycups one. The good news is that the API makes sense, so it's no big deal; but we could possibly diverge a bit if needed. So if you're working on another tool to configure printers, don't hesitate to look at the D-Bus API and send comments on what is missing there for you.

Oh, and of course, in openSUSE, we still require the root password for all those fine-grained privileges, but at least this is easily configurable now :-)

Lucas Nussbaum: Debian Squeeze, Ubuntu Lucid and Ruby 1.9.2: NO!

2010-02-10T12:38:33+00:00

Apparently, there’s some hype in the Ubuntu community about Ruby 1.9.2, so let’s clarify: it would be totally irresponsible to try to ship Ruby 1.9.2 in Debian Squeeze or Ubuntu Lucid.

Ruby 1.9.2 has not been released yet:

June 2009: The release schedule for 1.9.2 was announced
mid-July 2009: Ruby 1.9.2 preview 1 was released
September 2009: 1.9.2 preview 2 was tagged in SVN, but not announced
September 2009: The release plans were cancelled
October 2009: A meeting was announced to discussed new release plans, but I don’t think that the outcome was made public
Ruby 1.9.2 has not been branched off trunk yet

That’s where we stand now. Even if surprises are possible, it’s very unlikely that Ruby 1.9.2 will be released before Lucid’s release (or, what the real requirement is, before Lucid’s freeze). So we are sticking with 1.8.7 and 1.9.1 (1.9.0 will go away before the release).

If you can point to specific commits that fix real bugs in 1.9.1, and could be backported to the Debian package, feel free to notify the Debian Ruby maintainers.

Lucas Nussbaum: Slides from my FOSDEM talk on Debian and Ubuntu

2010-02-09T16:52:11+00:00

I’ve just put the slides of my talk on Debian and Ubuntu online.

Don’t hesitate to post comments to ask for clarifications where needed (it might be difficult to understand some parts of the slides without being in the room).

Clarifications:

In slide 15, I wrote that Ubuntu had a newer X. During the presentation, I think I said that I wasn’t sure if it was still the case. Indeed, it’s no longer the case (and hasn’t been for a long time ; Ubuntu has been mostly following Debian for X). I apparently remembered a change a long time ago that was picked by Ubuntu from the Debian X svn/git (xlibs-dev removal, I think), and that caused a number of FTBFS in Ubuntu. However, clearly, the best example of such changes made first in Ubuntu are newer GCC versions.

Lucas Nussbaum: Going to FOSDEM

2010-02-05T12:49:09+00:00

Yes, I’m going to FOSDEM. And this year, I decided to innovate by starting the obligatory FOSDEM flu before leaving to FOSDEM.

I’m doing a talk on Sunday, on Debian and Ubuntu (Distributions room, H.1308, 13:45). It might not be on your schedule (but is on the printable schedule) since it was decided quite late.

Vincent Untz: Going to FOSDEM 2010

Vincent Untz — 2010-02-04T10:11:00+00:00

I'm happy to go to Brussels again this year: it's been a long time since I didn't eat some really good waffles! Of course, I had to pretend I would do something useful there, so I'm participating in two talks, both in the distributions devroom:

Working with GNOME upstream: this will really be an interactive session, where upstream and downstream people for GNOME can meet, and discuss what can be improved to make the life of both upstream contributors and downstream contributors. It will probably be a good opportunity to also clarify how GNOME 3 might affect distributors, and to get a first overview of how it will be handled downstream. I hope it will be useful for everybody. I certainly hope we'll have a bunch of upstream people attending, and that we'll have representatives for various distributions there (make sure to tell the GNOME people in your distribution to come!).

Translations of package descriptions: as you can see, I don't have my name attached to this session, so I can pretend I didn't know about it ;-) But I'm supposed to help Anne there as we've discussed this a bit in the past few months. Translating package descriptions has obvious benefits for the end users, but it's a huge amount of work. And therefore we can seriously wonder if it's really worth duplicating this effort in each distribution (hint: probably not). So this session aims to look at what we can do to work together on this, and what it implies.

I'm also eager to have some insightful discussions with the great people that will come to FOSDEM. The hallway meetings have always been productive there!

GNOME

GNOME will have some strong presence again this year. There's the GNOME devroom on Saturday, that will become CrossDesktop devroom on Sunday, and during the whole week-end, we'll have a booth. If you want to help, that's definitely the place where you should go: we need volunteers to run the booth (see Lionel's mail for more details).

The booth should look great again, thanks to the event box, lovely stickers (they'll be free again!) and, hopefully, t-shirts (we're unsure they'll be ready in time, but let's be optimistic ;-)). On Saturday, you'll also find there some information about what is becoming a tradition: the GNOME Beer Event that will occur on Saturday evening.

Oh, apparently, I was volunteered to organize the GNOME group photo on Saturday, at 15:30. So make sure to be around the devroom at that time!

openSUSE

There will also be a good number of openSUSE people, with the usual booth (looking for some openSUSE DVD or sticker? You'll find them there!). This year, there's no openSUSE devroom because there's one big distributions devroom instead; I believe it's a good thing, though: it should help get more collaboration happen, and it's also a nice opportunity to steal good ideas ;-)

I'm happy that most of the boosters team will also attend; I heard it's a great group of people to hang out with!

Lucas Nussbaum: Re: How free is the Nokia N900?

2010-01-26T17:02:06+00:00

Following my questions on the freeness of the Nokia N900, I received quite a lot of comments. I’m trying to summarize the most important points here.

Maemo is not 100% free software. There are some proprietary components. The Free Maemo wiki page lists them all, and there are some explanations on Why the closed packages.
The Mer project (install notes for N900) aims at providing a 100% free alternative to Maemo.
It’s possible to rebuild/upgrade the kernel, however the newest kernel build-depends on a fiasco-gen package that is not provided. It is being worked on.
Nokia is sponsoring someone to work on Maemo derivatives.

For all the details, see the comments and Tollef’s blog.

Lucas Nussbaum: How free is the Nokia N900?

2010-01-25T13:56:45+00:00

Dear readers,

So, I’ve been looking into buying a Nokia N900. However, what it provides regarding freedom is still not completely clear to me. And given that it is significantly more expensive than other smartphones, I’d like to make sure that it’s not a loss of money :-)

- Can I download the full source, recompile it, build a firmware from it and re-install my Nokia N900 from scratch? Is the process documented? It seems that you need to accept a EULA to download updated firmwares, and I couldn’t find the source for them. What exactly is available from firmware that is not available through normal repositories? (Are normal repositories only for “extras” apps, or is the base system also installable / upgradable from them?

- What’s the content of /etc/apt/sources.list? What exactly is http://repository.maemo.org/pool/maemo5.0/nokia-binaries/? What does Nokia need to hide? :-)

- Would it be possible to develop a Centos-like distribution, installing the Maemo firmware, but then upgrading everything to rebuilt versions using an unofficial repository? Are there some applications that are not packaged, or that would break if re-installed that way?

- Could I install Debian or Ubuntu on the N900? Is the process documented? Is it possible to dual-boot between, say, Maemo5 and Debian? (I’m not talking about setting up a chroot, of course)

- Besides the non-free telephony stack, are there any other “antifeatures” I should be aware of?

Thanks.

Lucas Nussbaum: Simpler GnuPG-encrypted password store

2010-01-22T22:49:52+00:00

Roland blogs about his GPG-encrypted password store.

When I read the title of his blog post, I thought he would be writing about the gnupg.vim Vim plugin. But he didn’t, so I’ll take care of that: The gnupg.vim plugin provides transparent editing of GPG-encrypted files. It’s as simple as vim foo.gpg, enter your GPG key if you are creating the file, and you are done.

Vincent Untz: Updated GNOME for openSUSE 11.2, and why it's good

Vincent Untz — 2010-01-22T11:04:00+00:00

Luis already unleashed the word: GNOME 2.28.2 will be released as an online update for openSUSE 11.2 (for reference, openSUSE 11.2 was initially released with 2.28.1). You can currently help testing that everything is fine with the packages by adding the 11.2-test repository and upgrading. Please go ahead and test it, and tell us if it breaks anything. Hopefully, it should work quite fine.

What is really exciting about this is of course not that we're delivering bug fixes to our users ;-) But with 11.2, openSUSE got a new maintenance team, with more community involvement. One of the amazing result is that it is (or at least, feels) much easier now to release online updates for packages, with a process that everybody can follow — it used to be restricted to Novell employees. Another welcome change is that we can finally release new upstream versions as updates, with some obvious restrictions: the new versions should only contain bug fixes, and should fix real important bugs for users.

And this is what enabled the release of GNOME 2.28.2 as an update for openSUSE 11.2: this version bump was lead by Dominique and Magnus. I must admit I'm really glad that I didn't have to do anything ;-) The GNOME policy to only do bug fixes (and updated translations, which is something we also care about!) on a stable branch, and the fact that we're doing a good job at being reliable on this upstream, certainly helped too.

But wait, there's more! If you're crazy about GNOME but still want a stable distribution, you can use GNOME 2.29 on openSUSE 11.2! The Build Service is really helping us here, making it easy to reuse our GNOME 2.29 packages that we have in Factory on 11.2, with nearly no work at all. We have some documentation on how to use GNOME 2.29 on openSUSE 11.2, and testers are welcome. It should work fine and not eat your computer. Testing Factory is also an option, and while it used to be hardly usable in the past, the community is now doing a good job at making sure it works fine most of the time, if not all the time.

Did I mention you can get the latest version of various applications on 11.2 by just adding the GNOME:Apps repository? No need to update the distribution. No need to update GNOME. This is getting insanely cool :-) And both for packagers (nearly no effort to backport packages) and users (latest versions of their preferred applications available on a stable distribution).

Romaric Guillier: Pour en finir avec Portland, OR

2010-01-05T20:43:17+00:00

Ca me fait un peu bizarre de dire ça, mais j'ai à peu près la même vision que Pénélope Jolicoeur en ce qui concerne Portland. Pleins de bars et de coins avec de la bonne musique dedans. Des forêts pleines de grands arbres sur les montagnes (moins sur les plaines qui ont été rasées pour faire pousser des vaches et du fromage de Tillamook), avec de la neige et du brouillard digne du Shining. Un poil d'océan déchainé, des grosses cascades et du vin trafiqué.

Pour finir, je tiens à remercier les gens du Grendel's Coffee House, une chouette coffee house où on squattait pour les petits déjeuners (sauf les jours où je suis allé écouter des vice-présidents des US of A.) et qui fait regretter que seul les Starbucks traversent l'Atlantique. Et puis aussi les gens du Report Lounge où on allait tester les bières locales et apprendre à prononcer le nom des vins comme des vrais petits américains. Tout ça sur Burnside East (si vous êtes sur Burnside West, ça veut dire qu'il faudra traverser toute la ville).

Laurent Goujon: Neige Neige Neige

2010-01-03T22:44:00+00:00

Ca y est, premières neiges de l'année 2010 et j'en ai bien profité ! Et surtout j'étais bien équipé :

J'en profite aussi pour vous souhaiter à tous une très bonne année 2010 !!!

(Merci à Pam et Seb pour la photo)

Laurent Goujon: L'astuce ultime : comment savoir si sa télécommande est en panne...

2009-12-27T09:00:00+00:00

Bon, un jour ou l'autre, on a tous une télécommande qui subitement ne marche plus (généralement au moment où l'on en avait le plus besoin, merci Murphy). Bon, la plupart du temps, changer les piles (pour peu qu'on en ait encore...) suffit mais parfois non. Et là, la question cruciale : est-ce la télécommande ou bien le récepteur qui est en panne ? ^[1]

Voilà le truc ^[2] : prenez un appareil photo numérique, ou bien une caméra, l'important étant d'avoir un mode "visée sur écran" (sur mon reflex, il faut passer en Live View), et avec la télécommande, visez l'objectif en appuyant sur le bouton : si la télécommande marche, une lumière apparait aussitôt ^[3]!

Notes

[1] Parce que si on pouvait s'éviter de racheter inutilement une télécommande ou bien de remplacer l'appareil

[2] qui ne marche que pour les télécommandes à infrarouges

[3] Ultime je vous dis

Lucas Nussbaum: Doctor Capello!

2009-12-22T21:22:55+00:00

He might too shy to tell everybody, but the world must know. Luca Capello successfully defended his PhD thesis today at Université de Genève, getting a “Très Bien” mention.

I must admit that my last biology lesson was 13 years ago, so I’m not sure I can really comment on his work on Vomeronasal Receptors: from Monogenic Expression to Axon Guidance. But I was very impressed by the quality of the experimental process, especially compared to what we do in computer science.

Debian was well represented at the defense, since Axel Beckert, Didier Raboud and the Debian kilt were also there.

Welcome to the list of Debian Developers holding PhD degrees, Luca!

Luca waiting at the door (again).

Luca ready to start.

Lucas Nussbaum: Debian’s KVM + Ubuntu karmic => bug?

2009-12-21T23:39:35+00:00

I’ve been playing with virtualization, and KVM in particular. However, I’m running into an interesting problem. Below is how Ubuntu Netbook Remix look inside my KVM (either using virt-viewer, virt-manager or directly KVM to display the VM). Note how the top panel is fine. I’m using KVM 88 from experimental (but I had the same problem with KVM 85 from unstable), the cirrus video driver inside the VM, and an up-to-date karmic VM.
Has someone ran into that problem already? If yes, where is it tracked? I’m been failing to find the correct search keywords so far.

Romaric Guillier: Al Gore et le Supercomputing

2009-12-09T22:12:31+00:00

Il y a une poignée de jours, j'ai eu l'occasion une nouvelle fois de partir aux Etats-Unis pour aller évangéliser les foules à la gloire et la toute puissance de l'INRIA dans le domaine de l'HPC (hey "HPC Expertise par excellence for 30 years", we're what you call "experts") et également d'assister aux "keynotes" de la conférence.

Un "keynote speech", c'est une présentation où un invité (généralement un GRAND nom du domaine) va exposer sa vision du futur de l'avenir, présenter les pistes de recherche qui vont donner les avancées les plus spectaculaires pour l'humanité, etc. Ca, c'est la théorie, parce que dans les faits, ça donne surtout des choses comme l'exposé du CTO d'Intel le premier jour où on a appris que l'avenir du web c'est le 3D interactif^[1], malgré les taquets que se sont pris tous les gens qui s'y sont frottés après que le soufflé se soit dégonflé. Mais c'est tout simplement que la technologie n'était pas prête. Ceux que veulent les gens, c'est des tissus drapés où on modélise le mouvement de chacune des molécules qui se baladent dans l'air. Malheureusement, pour l'instant, ça met des jours de calcul pour calculer un rendu de quelques minutes, mais heureusement, Mr Intel est là !

Parce que vient à la rescousse, Larrabee et ses huit coeurs, faisant trembler l'aiguille du benchmark jusqu'au Téraflops libérateur. Le Téraflops ! Le Téraflops !^[2] Et bizarrement on comprend les trois premiers slides de sa présentation où il trouvait que bon la croissance était pas assez soutenue dans le domaine des supercomputers et qu'il fallait trouver des applications pour générer plus de business^[3] (et leur acheter des CPU).

Le deuxième jour, c'était un poil plus sérieux avec Leroy Hood, un biologiste qui se lance (via une start-up) pour faire converger pleins de trucs: la médecine, la génétique, la biologie systèmique, la technologie et l'informatique moderne. Bref, faire de la médecine une science de l'information. Tout ceci via des mesures régulières de paramètres sanguins (via des Lab-on-a-Chip^[4]) pour avoir suffisamment de points de mesure et contrecarrer avant l'apparition des symptomes une maladie.Bon, evidemment, il ne parle pas du tout des dérives potentielles de ce système, parce que la santé, c'est important et bienvenue à GATTACA (et puis "Obama est nul, il a rien compris aux enjeux d'un système de santé").

Finalement, le troisième jour, c'était "Développement durable" et du coup ils ont invité Al Gore pour qu'il dise à quel point ce que les gros ordinateurs qui consomment plein d'electricité et de climatisation sont chouettes pour la planète. Bon, j'avoue, je n'ai pas pu voir Al Gore en vrai, parce que je me suis levé un poil trop tard$$ pour trouver de la place dans la grande salle (complètement barricadée par les agents de sécurité à l'heure), mais heureusement pour moi, c'était retransmis dans des petites salles un peu plus loin. J'ai donc pu essayer de suivre sa présentation un poil confuse puisqu'il utilisait la technique dite du "pas de slides, pas de plan, je remplis les cases de mon discours avec des examples situés dans le domaine des gens à qui je cause". Donc là, il a écrit un livre pour expliquer aux gens pourquoi c'était normal s'ils n'arrivaient pas à se rendre compte qu'il y avait des changements climatiques et que du coup les simulations de climat étaient intéressantes parce que du coup, ça montre aux gens qu'on tue des ours polaires.

Le tout entrecoupé de blagounettes de politiciens, à base de gens qui l'empêchent manger sa soupe parce qu'il ressemble quand même beaucoup à Al Gore en plus vieux, et de recoiffage intempestif de cheveux avec le plat de la main. Et surtout une grande tirade à la fin où il demande si les gens ont envie d'être des gens sur qui on jette des pierres dans 20 ans ("BOOOOO, t'as rien fait pour changer le monde") ou à qui on lancerait des fleurs avec admiration ("Wouhou, comme tu es trop un héros de t'être levé et d'avoir tapé du poing sur la table pour le futur de l'avenir"). Choisis ton camp, camarade !

Notes

[1] Pour paraphraser un collègue de bureau, si je vais sur un site de vente en ligne, c'est pas pour avoir à faire semblant de tourner les pages d'un catalogue en Flash.

[2] En disant "le million de million de flops", on comprend mieux la référence, mais c'est plus loin à dire

[3] James Ellroy nous dirait de cette conférence "Cherchez l'application.." (en français dans le texte)

[4] Nouveau! Des chips au goût laboratoire.

Laurent Goujon: Chaud les photos...

2009-12-08T09:14:00+00:00

Ca y est, elles sont enfin là, triées, nommées, géotagguées : ce sont bien sûr les photos du Japon

#flickr_badge_source_txt {padding:0; font: 11px Arial, Helvetica, Sans serif; color:#666666;} #flickr_badge_icon {display:block !important; margin:0 !important; border: 1px solid rgb(0, 0, 0) !important;} #flickr_icon_td {padding:0 5px 0 0 !important;} .flickr_badge_image {text-align:center !important;} .flickr_badge_image img {border: 1px solid black !important;} #flickr_www {display:block; padding:0 10px 0 10px !important; font: 11px Arial, Helvetica, Sans serif !important; color:#3993ff !important;} #flickr_badge_uber_wrapper a:hover, #flickr_badge_uber_wrapper a:link, #flickr_badge_uber_wrapper a:active, #flickr_badge_uber_wrapper a:visited {text-decoration:none !important; background:inherit !important;color:#3993ff;} #flickr_badge_wrapper {background-color:#ffffff;border: solid 1px #CCFF66} #flickr_badge_source {padding:0 !important; font: 11px Arial, Helvetica, Sans serif !important; color:#666666 !important;}

www.flickr.com

A retrouver directement sur flickr