Introducing MEPHISTO (aka SWIM before)

Mandriva (Helios project partner) introduced us to SWIM, which was later renamed as MEPHISTO, a project for “Meshing People, Hardware and Software Together” during the Helios WP3 kick-off.

I’ve already blogged about it previously, so you may have already an idea of the pursued goal : adding more semantics to databases of facts about FLOSS projects.

Here are the slides presented by Stéphane Laurière (ODP), for those interested.

I’m looking forward to experimenting with it in the frame of HELIOS, mainly on bugs facts.

Update 2008/03/03 : the mephisto project is now open @Google code, if you’re interested in participating.

UDD, SWIM, Flossmetrics : facts databases about libre software distributions… going Semantic ?

I’ve attended the recent FOSDEM 2009 (great as always), where a number of presentations triggered a lot of my interest.

First @DebianRoom where Lucas presented UDD, the Universal Debian Database. This database groups facts about the Debian project, to ease the creation of queries on what’s happening in the Distribution. This is for instance very helpful for QA tasks, like counting bugs with certain characteristics, or comparing packages in various ways.
Note that a complementary presentation by Enrico was very interesting, on DDE : Debian Data Export (edit: see also his post on DDE), showing ways to offer services to query UDD.

Another presentation, @CrossDesktopRoom introduced the Flossmetrics database, which is collected out of many libre software projects, by extracting contents of the project data from the hosting forges. Very much interesting, in particular since the data becomes available, and a large number of projects allow researchers to compare them in many ways.

Maybe Flossmetrics could benefit from data coming from the Debian UDD… or vice versa ? I think contacts have been taken to think about potential future interchange between the 2.

A general criticism I could make on these two databases is that their schema (the tables & columns layout, as well as the eventual relations), and the code of the data “harvesters” is the only way to understand the real meaning of these data. There’s not so much semantics. Sometimes for known reasons, because, as explained by the UDD developers, there’s actually much incoherence in some of the Debian tools already, and it still it happens to deliver 😉

I’m thinking of a way to produce similar databases of facts (results of queries on these) with Semantic Web standards, to try and convey some bits of commonly agreed semantics, hence fostering interoperability of these databases, and maybe allow comparison of facts relating to different projects. Edit: actually, this idea has been in the air for a year, as readers of a provious post may remember. See in particular the paper by James Howison presented last year at WOPDASD 2008.

It happens that Mandriva, as a followup of the Nepomuk project is indeed trying to setup such a database (called SWIM at the moment. Edit: it has been renamed to MEPHISTO. See my other post on it.) with the use of RDF ontologies, to store facts and annotations about its distribution (more details here). In the HELIOS project, we’ll certainly try and investigate the use of such techniques to try and manipulate such data, like bugs for instance.

I’m thinking about providing an access to UDD with the use of a SWIM-like service, so maybe we can imagine things like more linking of facts about packages, people, bugs and such between Mandriva and Debian, for instance.

Note that at the FOSDEM there were also interesting presentations relating to these kinds of semantic techniques, both relating to outcomes of the Nepomuk project : one about the integration of KDE 4.2 in Debian, where tools like Soprano were mentioned, and another about Tracker in Gnome (which I haven’t attended) about the same kind of techno on the Gnome side.

The future seems semantic, somehow… and we have then a lot of work ahead of us. More to come.

Introduction to bts-link slides

bts-link is a very useful tool which helps keep track of bug status changes when a Debian bug has been marked as linked to another bug in an other (upstream) bugtracker.

I’ve prepared some slides of introduction for our partners in Helios to introduce them to that tool :

These slides can also be found on the helios site (ODP source).

Also, I’ve started contributing to bts-link in the frame of our work on Helios, and I’m glad my contributions have been integrated, although learning git in the way was kind of a pain 😉

More details about bts-link at : http://bts-link.alioth.debian.org/

Nous embauchons un ingénieur informaticien en CDD pour travailler sur la synchronisation entre bugtrackers

Nous embauchons un ingénieur informaticien en CDD (15 mois), pour travailler sur la synchronisation entre bugtrackers

( voir la version complète de cette annonce : ici — and the english version here.)

Nous recherchons un ingénieur informaticien pour travailler avec nous dans l’équipe PFTCR afin de compléter notre effort de R&D sur le projet HELIOS. Nous sommes responsables d’un de ses sous-projet visant à étudier et réaliser un dispositif s’intégrant à la plate-forme HELIOS, pour assurer la synchronisation entre bug-trackers.

Le lieu de travail serait Évry (France) pour une durée de 15 mois, en CDD (démarrage premier trimestre 2009). Les réalisations entreprises dans le cadre du projet seront reversées dans le patrimoine logiciel libre.

De solides compétences en développement logiciel, ainsi qu’un intérêt pour la recherche sont demandées aux candidats. De plus, une bonne connaissance technique des outils de développement libres ainsi que des dynamique des projets de développement dans le monde libre (distributions, packaging, QA) seront attendues. Une expérience de contribution sur un projet libre serait un must (type développeur Debian, par exemple). La maîtrise de l’anglais technique sera requise, vu l’objectif d’interaction avec des communautés de développement libre à l’international.

Si vous êtes intéressés et disponibles début 2009, il faut absolument qu’on se parle. Voir plus de détails dans la version complète de cette annonce.