Earlier today (or, well, last night, since it's fairly late alrady) I uploaded pmw (about which I blogged previously). In preparation for that, I've also uploaded aspic, which is required to build pmw's documentation. While I'm quite fond of pmw already, and intend to maintain it inside Debian for quite some time, my interest in aspic is limited to the fact that I need it for pmw. So if anyone seems interested in adopting it... be my guest. But do talk to me, first. In my previous blog post, I've raved about how I like pmw much more than I do lilypond. I had two reasons for that, at the time:

• faster in processing
• better syntaxis

Now, I have a third:

wouter@celtic:~$ grep-available --eregex -FPackage -sInstalled-Size -sPackage '(pmw lilypond)'
Installed-Size: 1916
Package: pmw
Installed-Size: 7048
Package: lilypond-data
Installed-Size: 392344
Package: lilypond-doc
Installed-Size: 896
Package: pmw-doc
Installed-Size: 4184
Package: lilypond

Less than two megs for pmw, versus over ten for lilypond and lilypond-data combined; and less than a megabyte for complete documentation plus examples for pmw, versus several hundred megs for lilypond-doc. And it's not because pmw is less flexible, or has less features, or is less well documented, or anything of the sorts. It does have less output options; but then it's not like it's hard to convert PostScript into something else or anything.

As I've already written, SourceForge.Net has limited things which you can do on git/mercurial servers and one of the things they have prohibited is sending emails. This is one of few things which almost every projects uses so it has brought quite obvious reaction, people are reporting bugs that it stopped to working. The major reason for reporting bug is that this change was not at all communicated to users (nor users nor project admins), so it was just a surprise and every body expects bug and not this kind of reply. As I don't have way to reopen the ticket, I had to open another one, that the documentation is wrong and I hope the reply will be slightly better. SF.net, if you still don't believe people used this feature quite a lot, just look at number of bug reports you have in your tracker right now...

Filed under: English Phpmyadmin 0 comments Flattr this!

I just realized that the Debian Installer is ten years old! It actually got started ten years ago last summer, but now is also an apt anniversary -- ten years ago, I successfully booted d-i for the first time. It's amazing that d-i has been around as long as Debian Developers who have "been with the project longer than most". (Many of whom have been long-time contributors to d-i themselves.) Astonishing that my basic design has held up and remains relevant. And every time I boot up the Debian kFreeBSD installer, or run the graphical installer, or hear someone raving about how easy Ubuntu was for them to install (and know d-i was underneath), I'm amazed at the places people have taken d-i. The code has recently moved to git. As changes like ext4 by default start to flow in to d-i, with Wheezy development starting up, I hope to see more people enticed into working on d-i. Anyone can do like Matthew Palmer has done with netcfg -- pick a component of d-i that interests you, check out its git repository, and take it from being reasonably well team-maintained to awesomely you-maintained. In five or ten years Matthew will be able to look back at all the people who have used d-i to install over IPv6, and on WPA wireless, and with his other netcfg improvements. Trust me, it's a great feeling. Previously: d-i retrospective (better written than the above & well worth a re-read)

After recent attack on sf.net servers, some services have been unavailable for some time. Now things are returning to "normal" operations, CVS has been made available yesterday. But this has lead to other (quite unrelated) change, affecting all SCM services:

outbound email is not functional, so any script utilizing this will fail. If you need to send outbound email, a workaround would be to use curl and and external site or Project Web to send the email.

I think this is just wrong. If this is as a measure against spam, it will rather open dozens of other places where to send spam, because every project wanting commit notifications (or using CIA.vc), will need to deploy some script on web to send mail. And I guess it simply won't be much protected. Maybe it's time to consider changing service provider... PS: The bug I've reported on this topic is here.

Filed under: English Phpmyadmin 3 comments Flattr this!

We just learned about the Nokia and Microsoft strategic partnership today and many people are concerned. I think the agreement is worrying for Qt, but even more worrying for Nokia. I foresee an exodus of current developers and Nokia mobile device users. Many Windows developers will come. Hopefully? I really wonder who is actually benefited by this strategic partnership. Nokia already had many mobile devices with Symbian, one with Maemo (and there could have been many more with Maemo, but for some unknown reason there weren t) and Meego could have been adopted already (but again, for some reason, Nokia had not). On the other hand, Microsoft had an operating system but no users. Virtually nobody wanted Windows 7. It was either Android or your own solution (MeeGo, WebOS, Bada, etc). In my opinion, the next move we will see is Microsoft buying Nokia to be able to compete one-to-one with Apple and Google. I think it will not take too longer, probably they are just waiting for Nokia stock to fall a bit more. So what should have been the change of direction Nokia should have done a few years ago? In my opinion, when Nokia acquired TrollTech, they should have released at least 10 devices with Qtopia. Immediately. And dump Maemo. In parallel, they could have added more and more Maemo features to Qtopia. By doing that, they would have had a good mobile operating system and applications in no time. There was even an X11 compatibility layer for Qtopia back then. I did not understand why Nokia adopted Qt and went on with Maemo and Meego based on Gtk+, and tried to keep as much backwards compatibility (regarding to source compatibility, development methodology,e tc) with devices which barely had users (N770, N800 and N810). I think noone understood that move. From my point of view, that was a waste of time, money and effort, which ultimately led to Nokia s demise. PS: Yes, I still am a KDE on Windows developer and part of the Debian Qt-KDE team

After Debian Squeeze was released last weekend, development will speed up again.
Today I uploaded a new postfwd package which ships also the postfwd2 script, a prefork server version.
I also started to orphan packages I m not using anymore or having dead upstream. The first candidate was policyd-weight, fortunately Chris Butler took the package over.
I m happy to be the first uploader into squeeze-backports with . icinga.

Today we've got new submission for phpMyAdmin theme contest and I must say it really looks great. The new theme is called pmahomme after it's author Mike Homme: It's now also available on the demo server, so don't hesitate and try it there. Looking forward for other submissions to our contest.

Filed under: English Phpmyadmin 0 comments Flattr this!

Here comes the forth Debian XSF News issue! I usually try to keep the items sorted chronologically (but grouped by topic when possible), so if you re wondering about the current status of X in unstable, make sure you read the last entry.

• I prepared a reference documentation about dependency handling between the X server and the drivers. It describes both upstream and Debian sides, and documents the mechanisms to get the dependencies right. If you maintain an input or a video driver for X, you really should have a look into it.
• I also announced the changes on debian-boot@ since the Graphical Installer is also concerned.
• Since there are some drivers which aren t maintained by the X Strike Force, I mailed almost all maintainers (plus the ones I missed) to keep them posted. Further coordination will go through a mail alias (which means a little less overhead than running a mailing list; mail me if you want to be added).
• I prepared a great clean-up of the drivers, and published a status report 3 days later.
• In order to keep track of people working on X packages these days, I started pinging the Uploaders of X packages. Thanks again, folks!
• On the driver side, I moved the xserver-xorg-video-dove driver to the attic (where we move repositories of unmaintained packages), since it was only ever uploaded to Ubuntu, and not really maintained upstream. I also moved 7 drivers there, and requested their removal through RM bugs (each bug contains a link to the git repository in the attic in case someone wants to revive a driver): xserver-xorg-input-citron, xserver-xorg-input-evtouch, xserver-xorg-input-fpit, xserver-xorg-input-hyperpen, xserver-xorg-video-nv, xserver-xorg-video-radeonhd, xserver-xorg-video-v4l.
• Julien Cristau also requested the removal of xprint and xprint-utils. He also orphaned xresprobe since it s of no use as far as X is concerned, but still seems to be of some interest to DebianEdu folks.
• I requested an update of debian-x@ s description. We haven t been doing any Debian XFree86 packaging in a while.
• I requested help from GNU/kFreeBSD and GNU/Hurd folks, and got replies from Petr Salinger and Dave Airlie. Now mesa builds again on kfreebsd-amd64 (and kfreebsd-i386 once the remaining glitch is fixed).
• In the same mesa upload, I enabled the r600 Gallium driver, and cherry-picked a commit to fix the crash at X s start-up with r300 and UMS.
• I merged the xsf-docs.git repository (source for XSF documentation at http://pkg-xorg.alioth.debian.org/) into the xorg.git one, and moved the former to the attic. Starting with xorg/xserver-xorg 1:7.6+2, XSF documentation is shipped in the xserver-xorg package, in the /usr/share/doc/xorg directory, in HTML, PDF, and TXT formats.
• I also added a bug control file (as documented in reportbug s README.developers) to xorg, telling reportbug to also report information related to the xserver-xorg package. This means we get xserver-xorg-core s version, along with the drivers. I also made xorg depend on xserver-xorg with the same version, to make sure that upgrading xorg means upgrading xserver-xorg as well (and xserver-xorg-core ultimately, since xserver-xorg pulls a given version of the server).
• Julien also uploaded a few libraries and mesa-demos (new source package for mesa-utils) to unstable. I also uploaded the latest pixman to unstable.
• A few hours before squeeze got released, I prepared the big move of the X server from experimental to unstable. For the record that meant uploading libdrm, libxfont, and mesa as prerequisites. I then pushed the locally-built packages in a local archive to use from my sbuild chroot, to get xorg-server built. Subsequently, I built 45 drivers against it. The xorg metapackage was also prepared. All in all, that meant 200MB worth of Debian packages (including 130MB for mesa alone ), which sat on ravel.debian.org until the squeeze release announcement. Unfortunately, lintian s #612137 triggered an automated rejection of all drivers. Options seemed to be: adding build dependency noise to debian/control for all drivers; or adding lintian-overrides noise to all drivers; or waiting for some reaction from lintian s maintainers or from ftpmasters. I picked the last option for now, since I m very reluctant to do extra and pointless work on 45 packages to get them accepted when the reason for the rejection is buggy. Hopefully this will be sorted out soon, and I ll be able to upload the same packages again. If one feels the urge of installing X11R7.6, picking drivers from experimental will do the job.

As we're slowly heading towards phpMyAdmin 3.4, it is good time to look at current translations state. There are few which are already at 100%, so they are in best possible shape:

• Czech
• English (United Kingdom)
• French
• Slovenian
• Turkish

Some languages really miss just few messages, so they will hopefully get to 100% soon:

• Swedish
• Greek
• Chinese (China)
• Catalan

And there is huge progress in Russian, which will at this pace get to 100% this week. Was your language not listed? You can help it being better!

Filed under: English Phpmyadmin 0 comments Flattr this!

mythbustering a Debian release This is no news anymore, but in case you don't know yet: Debian 6.0 "Squeeze" has been released the past week-end. If you haven't yet downloaded Squeeze, stop reading this blog post right here and jump to: to choose your ISO; or check the release notes for upgrade instructions from Debian 5.0 "Lenny". Done?
Cool!
I hope you are now enjoying Squeeze as much as I've enjoyed being part of its development cycle which:

• has lasted 24 months from the Lenny release
• has been worked on by a volunteer Project of about 900 members and thousands of other volunteer contributors
• has closed 150'000 bugs
• has increased user freedom by delivering a Free Linux kernel
• has added 2 non-Linux ports (kfreefbsd 32/64 bits) to the already large family of Debian ports
• will continue the tradition of archive-wide long term security support (lasting about 3-3.5 years given current Debian release cadence)
• maintains, stubbornly, the tradition of a rock-solid Debian-quality system, made of packages which have been "tortured" by testing utils like piuparts, edos-debcheck, and frequent archive rebuilds (after all, what is Free Software for if you cannot recompile your programs?)
• has added 10'000 new (binary) packages
• has provided official backport service
• ... etc, you got the idea

I'm still shaked by the events, given the release happened in a sort of split context: the teams working on the final phases of the release (release team, ftp-masters, webmasters, cd, DSA, etc.) were "at home" hacking frantically on it, while many EU-based Debian people (including yours truly) were at FOSDEM representing Debian to the community with booth, talks, and answering the recurrent question so, have you released yet? . At FOSDEM, I've been personally submerged by congratulation messages that are not really for me, but rather for the Debian community at large. So: congratulations folks! People out there be them Debian users, users of some derivative, or Free Software enthusiasts in general seem to really love what we have achieved with Squeeze! The people that need to be thanked for this result are way too many, so I won't try to name names. Nonetheless, I've a few personal kudos to deliver to:

• The release team for the fantastic coordination and communication job over the past few months. They have also contributed to mythbustering #1: Debian cannot fix a release date (a bit) in advance.
• All the people who have worked on fixing RC bugs by sending patches, reviewing and testing them, preparing NMUs, etc. I'll never give up my belief that releasing is a shared responsibility and that we cannot scale without realizing that and changing our culture accordingly. All this people have contributed to move towards mythbustering #2: NMUs are bad.
• The publicity team which with release live blogging via @debian, blog posts, and press releases have contributed to mythbustering #3: Debian isn't able to communicate about the "cool" stuff they are doing.
• The webmaster team which has done an incredible job at mythbustering #4: Debian web presence sucks.

I'm overwhelmed by happiness about all that and I'll cherish it forever as a souvenir of what a community of volunteers, driven by common ideals, can achieve. Now let's party and then roll up our sleeves for Wheezy, which is already open for development.

---

PS I've talked again at FOSDEM about the relevance of Debian in the Free Software ecosystem. I've the impression the message is getting through: check out the very nice article Why Debian matters more than ever by Zonker.

In an article about gender issues among American atheists, Sharon Moss and Lyz Liddell give a list of things to consider to be better community, not just for women:

• Be a leader. Take responsibility for the tone of your group. If potential new members are being made to feel uncomfortable and aren t coming back, you re doing it wrong. As a leader, it is your job to prioritize the comfort of your attendees in programs, group dynamics, and communications. Try to put yourself in other members shoes and also ask for feedback.
• Promote a sense of community. Take the time to socialize and get to know each other. If you re group isn t primarily a social group, thinking about adding some social time. Go to breakfast before the protest, compose your letters to the editor over coffee, or grab a pizza and beer after that lecture. When you know each other, you have each others backs. Being a jerk isn t tolerated.
• Moderate discussions. Make sure everyone has the opportunity to participate- new people, quiet people, etc. Don t let conversation be dominated by one or two people who must win.
• Embrace and accept different ways of communicating. Whether someone is an aggressive debater or not, make sure they re still welcome. The other atheist in the room isn t your enemy.
• Encourage subgroups. Every event your group hosts doesn t need to appeal to your entire membership. Many women appreciate women-only space to express their nonbelief and to connect with other atheist women. Here at the Humanist Community of Central Ohio, we started a subgroup book club called Reasonable Women. When it grew to have about 25 regular members and was beginning to be a little too large and unwieldy to function as a book club, we created a second group, Heathen Chicks, which is just a social group that meets at a local cafe. It isn t just about creating women only space, for us, this has been a way to draw more women into other events our group hosts.
• Foster women in leadership. Groups with women in leadership positions tend to have more women. Encourage women in your group to be visible in leadership.

These should work pretty well for Debian as well. I mean for the project in general, for getting all kinds of new people in, and getting them to stay, not just women, even if the gender imbalance is perhaps the biggest glaring problem we have. As a concrete suggestion, maybe it would be a good idea to continue the Debian party line that Joey set up for the squeeze release. We already have IRC, but having an audio chat with your Debian peers might be a nice addition. Specifically a social one, instead of something intended to boost productivity.

Squeeze was released this weekend and it's time to slowly migrate servers to it. The first to upgrade came the ones backing up phpMyAdmin demo server. Reason for trying them first is they have mostly same setup as other, while definitely not being critical to run all the time. For simple reasons that users break them time to time as well :-). Everything went surprisingly smoothly, the only problematic thing being no availability of MariaDB packages for Squeeze right now. But it does not matter that much, as Lenny packages still work fine. There should be no visible changes on the servers, but in case there is something broken, please let me know. While having experience with upgrading database servers, I went to production database server and it is now running Squeeze as well. What still remains is the server doing virtualization, but I prefer to do this in time when I can quickly get to the housing, in case something goes wrong with the reboot.

Filed under: Debian English Phpmyadmin 0 comments Flattr this!

The last weeks before a Debian release are usually boring with respect to working on new stuff since unstable is pretty much closed to development. Now that the release is finished, this fun is back \o/ I have been in an upload frenzy since yesterday night and I have updated some packages in unstable: KOffice[1] and KOffice-l10n 2.3.1, yakuake, rsibreak and tintin++. Another of my packages, kid3, got magically updated itself in unstable before I had time to look at it, the magic of having active co-maintainers. [1] Thanks for the gentle push to update this, Pino :) I also emailed one of my upstream maintainers to ask him about the KDE 4 version of his application and he will likely make a release soon. One of the goals for wheezy is remove completely KDE 3 and Qt 3. If you are maintaining a KDE 3 or Qt 3 based application, we are about to start annoying you about this! See http://wiki.debian.org/kdelibs4c2aRemoval and http://wiki.debian.org/qt3-x11-freeRemoval The last 2 weeks before the release I had some fun watching how the Squeeze release countdown banner I published at http://news.debian.net spread to a lot of websites, personal blogs, community sites, forums to news portals.
The traffic has been increasing little by little through the 2 weeks the banner has been online and currently is still moderately high, since people keeps retweeting the news item about the Debian release. While writing these lines, the banner has been served 449575 times to a total of 244975 unique IP addresses!

Today, I've made available two new themes for phpMyAdmin on our demo server. First one is Toba theme which was contributed by Azhari Harahap: Second one is Graphite theme which I've started during Hackweek and finished during free time around FOSDEM: And we're still waiting for more contributions to our Theme contest. PS: Forgot to mention that new themes are only for 3.4 branch and won't work with others.

Filed under: English Phpmyadmin Suse 0 comments Flattr this!

Inspired by some chatter in IRC, and encouraged to post by Paul Wise, here are my personal goals (in no particular order) during the Wheezy development cycle:

• Keep my packages BugLess(TM). It should go without saying, given the piddling little packages I maintain, but I've been a bit slack about this in the past. I want to be more proactive in responding to newly reported bugs, and dealing with them (forwarding upstream, fixing, uploading, etc).
• No non-wontfix, non-help bugs in netcfg. Since nobody else is giving it any love, I've decided to step up and effectively "adopt" netcfg (the component in the Debian installer which handles the task of selecting and configuring a network interface for the install process). I've already uploaded 1.60 with a number of smaller bugfixes, and I have projects underway relating to IPv6 support and WPA support (help needed on that latter one; see the link for details), but I've set myself the somewhat ambitious goal of completely scrubbing it's bug list down to wontfix and help bugs. Let's see how that goes...
• Do something about ifupdown. This one has grown out of my netcfg work -- basically, it's bug list is terrifying, and it's missing support for a number of IPv6 features (most of which appear to be reported already). I don't know whether my "something" will involve just bug triage, or writing patches, or actually getting involved in maintaining the package on an ongoing basis, but I've committed myself (publically now, even) to doing something.

So, I've shown you mine, will you show me yours?

As you probably already know, Debian released Squeeze aka Debian 6.0 this week-end. It was a really great week-end. I saw quite a few release already, but none with so much online social activity. Alexander and Meike Schmehl live commented the release on the Debian identi.ca account and Joey Hess held his Debian Party Line. On top of this, the team in charge of the website rolled out a new design on quite a few online services during the week-end including www.debian.org, wiki.debian.org, planet.debian.org and more. Congratulations to all the people who made this happen (and the release team in particular). It s great to see Debian achieve all of this. Do you know that it s the third time in a row that we manage to release in the 18-24 months timeframe? 3.1: June 2005 4.0: April 2007 5.0: February 2009 6.0: February 2011. Yes, despite our size and the fact that we are all volunteers, we have managed to stick to a reasonable schedule for a stable distribution that is deployed on a large scale. Wheezy kicks off The best part of the release for us the developers is that wheezy is now open for development and we can work on new features for the next release. And it started quickly: according to UDD, wheezy already features 488 new source packages that are not in squeeze, 1713 updated source packages and among those 1246 are new upstream versions. I really look forward to the upcoming projects and related discussions.

Click here to subscribe to my free newsletter and get my monthly analysis on what s going on in Debian and Ubuntu. Or just follow along via the RSS feed, Identi.ca, Twitter or Facebook.

---

For the curious, here are the UDD queries I used:

# Updated packages in wheezy
select count(source) from sources_uniq as su where (select version from sources_uniq where release='squeeze' and distribution='debian' and source = su.source) < su.version and release='wheezy' and distribution='debian';
# Updated with a new upstream version
select count(source) from sources_uniq as su where debversion(regexp_replace((select version from sources_uniq where release='squeeze' and distribution='debian' and source = su.source), '-.*', '')) < debversion(regexp_replace(su.version, '-.*', '')) and release='wheezy' and distribution='debian';
# New package in wheezy
select count(source) from sources_uniq as su where source not in (select source from sources_uniq where release='squeeze' and distribution='debian' and source = su.source) and release='wheezy' and distribution='debian';

No comment Liked this article? Click here. My blog is Flattr-enabled.

Our baby was release just some moments ago. Many thanks to all who made this happen, I m very proud!
Also many thanks to the release team, ftpmaster, cd people, www-team, press folks and all who worked so hard today instead of having release party, to make it real.

So after quite a while I again had the opportunity to do the ftpmaster works of a Debian release. Not quite my first and hopefully not my last one, lets see. And, like last time, Mark joined to help with the work. Again, a few moments and not a detailed log (times in UTC):

• [08:30] I ll start the ftpmaster side by turning off all cronjobs, prepare some database backup, get myself sorted.
• [09:33] Got dak.git prepared with most of the changes we need for the release
• [10:02] Oldstable suite created, load the contents from stable into oldstable. Lenny is now oldstable
• [11:00] Load stable with the contents of testing. That is, stable now is squeeze.
• [11:35] Cleanup various dirs in dists/, like - old installers, some breakage from elsewhere, fixup READMEs.
• [11:52] Have Lenny Release file regenerated and signed
• [12:29] Have Squeeze Release file generated and signed
• [12:54] Push the cd builder machine so they can start building our CD/DVD images
• [13:00] Start a manual dinstall run to check through all the rest of the archive if it still works
• [13:43] Get a heart attack when clean-suites reports Cleaned 2543 files, 2500 MB , but then discover it is only the hppa removal that got in just late before the release. Puuh.
• [14:30] all of the manual dinstall run is done, everything fixed, the main archive looks nice. So lets start breaking security
• [15:40] Yay, security archive all done, waiting for the general release to push the world
• [17:30] After a short break I updated the backports.debian.org archive also, it is now ready to receive uploads targetting squeeze (but wait for a mail from the bpo team!), the lenny-backports suite is changed to need manual approval of uploads, all nice.

Right now (that is, 21:38 UTC) I am mosty waiting for the rest of the people working on the release (CD builders, press, website, ) to finish their task (building hundreds of images just takes ages). When that is done we can then do a coordinated push to the world. Last plans for that would mean in about an hour . Lets see, Mr. Murphy sure can be around. Thanks go out to everyone involved in preparing this release, be it in the past by fixing bugs, uploading packages, doing whatever was needed, as well as doing the work today. Update: If you miss us setting the new testing AKA wheezy to something inside there - there is no need to. It is simply the continutation of testing with just another name, which did not get changed contents, so nothing done for that. :)

pommed v1.36 is out and brings support for the MacBook7,1, along with a few fixes and updates. A typo in the pmac keyboard backlight has been fixed, so fading now works there too. Product IDs for the ANSI and JIS keyboard variants for pmac machines were also added. It s been like forever since I last touched that code; not a lot of people still use those (great) machines. This release also contains a small update that will make it compatible with future kernel releases as applesmc will no longer have a fixed a name and location in sysfs. Update: I just noticed a bug in 1.36, so 1.37 is out now. It also contains two patches that were submitted through Alioth.

The Mancoosi Team has recently published the details of a study we conducted analyzing different packages managers available in debian. The goal of this study was to compare MPM (the mancoosi package manager) to other legacy solvers and try to get a big picture regarding of the state of the art. A similar study was conduct during EDOS and the results are still available here. As I wrote few months ago, MPM is a proof of concept that we wrote to test the behavior of a number of solvers that have been developed for the MISC competition in a real world scenario. These results do not show anything new w.r.t. the experience of a lot of poeple dueling daily with their machines in order to install a new piece of software. In a nutshell, we have shown that apt-get, aptitude, smart and cupt perform pretty well when used only with one baseline (for example a stable release) : this conforms with the experience of the majority of users of debian based systems. However problems start to arise when a user start mixing more then one baseline putting a lot of stress on the solver in order to find a satisfying solution. This solution of course exists, but it is cleverly hidden in the dependency structure of more then 40K packages... MPM is not as fast as other package solvers (say 10 seconds for mpm, while apt-get is able to find a solution in 3 second), but is remarkably stable. It is always able to find a satisfying solution, even in the harder cases where all the other failed. In these experiments MPM uses the postdam solver aspcud. This solver uses only GPL components and it would be a good candidate for inclusion in debian (there are actually a couple of ITP already filled for clasp and gringo). The results (with a lot of details) are published on the mancoosi website (a more detailed report is in the works). Enjoy ! During fosdem the Mancoosi team that authored this work (Roberto, Ralf, Zack and Me) will be around, so, please stop us for a chat ! And don't miss Ralf's talk !!