COCLICO started : many interesting development in forges ahead of us in the 2 coming years

We have started the COCLICO project this friday, with a meeting grouping many actors coming from various french regions, that operate in the area of open source forges (around FusionForge, NovaForge, Codendi, Trac, PicoForge, etc.). It’s a “Pôle de Compétitivité” (french R&D clusters) project which is funded by french public agencies, under the frame of both the FLOSS thematic group of System@tic (Paris) and Minalogic (Grenoble).

COCLICO will last 2 years and will let us all collaborate on producing FLOSS components that should allow much more interoperability between the open source forges, and probably deliver interesting standards that should allow to integrate forges with more tools in order to support new uses. We have no website yet, but it will be setup next week.

Of course a collaboration project with many companies (with various profiles, from the single consultant to the very large corporations) and academics is always requiring some effort so that everyone collaborates, but we have a strong focus on producing code as first steps, and I’m quite confident we all believe that FLOSS is necessary to share the innovation efforts.

I hope it will be a great occasion to bring interesting new things in the FLOSS ecosystem, and that we’ll manage to let others participate even if they are not funded by COCLICO, since one of the goals of the project is to bring momentum in the general forges ecosystem.

As far as we’re concerned at Institut TELECOM, we’re leading two workpackages on interoperability and community/ecosystem.

I’m very excited about this project, which together with our running Helios project should allow us to contribute in a significant way to FLOSS development tools and to the general quality of the FLOSS development process.

Expect more spamming from me about forges in the future on this blog 😉

Update : we now have a website both with more details in french (including a description of the project’s work-packages) and in english (still empty at the moment, working on it).

First webcast of a demonstrator of our bug ontology’s use

We have setup, as part of our work in Helios, a very early demonstrator of a database of RDF facts about bugs in several distributions (currently Debian and Mandriva), in order to try and validate the Ontology describing bugs that we develop.

Here’s a pointer to the first webcast on fetchbugs4.me’s blog, with more details.

Very interesting presentations this morning at OWF about the future of the Semantic Desktop

I’ve attended this morning the OWF session on the future Semantic Desktops, with excellent presentations by Stefan Decker (DERI) on the concepts of the Semantic Web and the Social Semantic Desktop, by the Zeitgeist project guys (Seif Lofty and Alexander Gabriel), and finally by Sebastian Trüg demonstrating the Nepomuk semantic desktop components in KDE.

It was a good occasion to meet these people (together with Henry Story) and talk a little bit about our efforts in the area of bugtracking and Semantic Web, and to discuss the future of the Baetle ontology, and do more teasing for fetchbugs4.me.

I hope some day, we integrate the models and tools so that bugs filed on bugtrackers can be referenced and manipulated with Desktop tools through interoperable APIs and common ontologies. More work ahead of us in Helios 🙂

I’ll be speaking about bugs, Helios, fetchbugs4.me at OSDC.fr

I’ll be giving a speech on Saturday about our efforts in Helios to foster interoperability between bugtrackers and bugs modeling on the Semantic Web : Bugtracking sur le web sémantique. See you in La cité des Sciences in Paris Saturday at 14:00 (free entrance).

Convert OWLDoc generated HTML documentation of an ontology to single HTML file

For the needs of the Helios project, I’ve written a script which uses htmldoc to convert the multi-framed HTML documentation as generated by Protege’s OWLDoc plugin to a single HTML document.

Example : the Helios_BT ontology documentation generated by OWLDoc, and the result in one single HTML document.

The Python script is at : owldoc2htmldoc.py (see also the README).