The RMLL are a big free software event in France. Last year, GNOME-FR held a booth there and it was a really huge success (definitely one of the best booths we ever had). We'll most probably be here again, with rocking GNOME-FR people.

There's also some news for this year's event: there's a desktop track. I can't imagine having a great GNOME booth without having some excellent GNOME talks, so everyone who wants to visit France at the beginning of July and who is ready to talk about GNOME, from a technical point of view or from a user-oriented point of view should propose a talk. There are only 15 talk slots, and we'll share this with other projects, but I guess we should definitely aim at having at least 4 talks.

Did I mention France is really a country you should visit at least once? Contact me if you're interested.

J'utilisais depuis plusieurs années spamassassin, tout simplement parce que c'était le meilleur logiciel anti-spam à l'époque où j'ai commencé à en avoir besoin. Il était très efficace jusqu'à il y a quelques mois, où j'ai commencé à souffrir, avec une dizaine de spams par jour (bon, c'est relativement peu, mais quand on n'a plus l'habitude, c'est dur). J'avoue ne pas avoir essayé de chercher si je pouvais améliorer le filtrage, mais il faut dire que je n'avais pas vraiment envie de mettre les mains dans le cambouis.

Je suis donc passé à bogofilter puisque beaucoup de personnes en disent du bien. La grande difficulté de mon cas est que tous mes mails sont sur un serveur IMAP et qu'habituellement, bogofilter est utilisé au niveau du client mail (par exemple avec ce joli plugin pour evolution intégré dans dapper). Après une rapide recherche, je suis tombé sur ces instructions qui répondent presque totalement à mon problème.

Pour résumer :

• procmail est utilisé pour envoyer le mail à bogofilter, puis le placer dans le bon dossier ;
• l'utilisateur déplace les faux spams ou les spams non détectés dans des dossiers particuliers ;
• un script lancé régulièrement par cron visite ces dossiers et permet à bogofilter d'apprendre ces erreurs.

Quelques petites modifications ont été nécessaires, notamment pour traiter le cas où bogofilter n'est pas sûr de savoir si le mail est un spam ou non.

Après un premier essai totalement raté (il détectait tout comme spam, probablement à cause d'une erreur initiale dans le script lancé par cron), j'ai recommencé à zéro. Et depuis, c'est le bonheur. Je parlerais presque de liberté retrouvée ;-)

Weehee! GNOME Goal #1 was a big success, with lots of people helping. Right now, only six modules are marked as to do. Rock! Thanks to, in no particular order: Michael Terry, Ruben Vermeersch, Matthias Clasen, Luis Menina, Luca Cavalli, Tommi Vainikainen, Philip Van Hoof, Christian Persch, Sébastien Bacher, Thomas Thurman, Lucas Rocha, Thomas Andersen, Michael Plump, Christian Kirbach, Przemysław Grzegorczyk and a lot of other people (sorry, I'm sure I'm forgetting to mention someone here). Now GNOME is GOption-powered!

But let's continue. I originally thought it'd be great to have a goal based on features. But Behdad and Christian were great and wrote complete pages for some of the goals, which are some nice things we should really do. So, what's special about this second GNOME Goal? Well, it's a combo GNOME Goal: you get two goals for one. The first one is to install theme-friendly icons, because every application has the right to be correctly themed! The second goal is to help our translators, so they don't have to check out an entire module to add a translation. And it's really easy to do this since you only have to put a LINGUAS file, with some other small changes.

Like for the first GNOME Goal, the wiki pages contain all the informations that you need to complete the goals for a module. And everybody is, again, welcome to contribute! It's easy, so don't hesitate and join all the people patching GNOME!

It seems some people already started working on these goals, so you should definitely try to fix one or two modules as soon as possible, while it's still possible ;-)

It's cool to see Ars Technica relaying my call for pessulus co-maintainers. I got some replies and I hope to see some rocking patches during the 2.15 development cycle.

Michael worked a bit on pessulus and sabayon to offer some OOo lockdown. Great to see this! I still need to answer his mail, though. I guess we'll probably want to add more and more settings to lock down for various applications, and having all this hard-coded in pessulus will make it hard to maintain in the future. So one big feature I'd like to see in pessulus for 2.16 is making it extendable, so you can just drop a small file in a directory and it will automagically enable you to lockdown some features. Guess what? Rob Bradford is working on this. Isn't it fantastic to have contributors?

If you want to join the fun, take a look at the pessulus plans for 2.16 and profit! Err, have fun, I mean.