Here’s a quick link to the call for papers.

Voici la liste des interventions filmées :

• Migration à Git du projet GNOME, par Frédéric Peters (GNOME)
• Méthodes de vote : comment consulter les développeurs d’un projet sans fausser le résultat avant de poser la question, par Lucas Nussbaum (Debian)
• Développement Open Source : un retour des tranchées, le projet Jajuk, par Bertrand Florat (Jajuk)
• Comment les outils et l’esprit Open Source permettent de faire de meilleurs projets, par Erlé Le Gac, Bertrand Florat (Capgemini)

Le son n’est pas toujours top, mais c’est fait avec les moyens du bord, bénévolement

Vous trouverez les pointeurs vers les vidéos et les slides chez Free Electrons (en bas de liste).

Et n’oubliez pas : l’édition 2010 remet ça, avec un appel à contributions toujours ouvert.

Join us and discuss (in english) forge matters on discussions@planetforge.org, to try and improve communication, sharing, reuse and interoperability among various hosting platforms, and collaborative development tools.

You may prefer joining the PlanetForge RSS aggregator if you blog about forges (feel free to add it to your preferred RSS reader).

There are various use cases for this, like moving a project from one forge to another, but also as backup/restore feature for forge admins. More about the rationale here.

We’d like this format to be a standard some day, so it should have good properties so that it’s generic enough and at the same time easy to adopt. Thus it would be relatively easy to contribute new exporters or importers to an framework (for which we’ll implement basic core tools), while having a long-lasting format that can still be used in the future.

A lot of work ahead of us, and this is just a short notice in case you’re interested and you’d like to know more

Stay tuned, and if interested, join discussions@planetforge.org to discuss this topic.

P.S.: yes, it’s a rebirth of CoopX, somehow (see the coopx tag in my blog for more details)

The meeting was organised by the COCLICO partners and welcomed the first FusionForge meeting, as well as other interested forges developers and users from Codendi, novaforge, nforge, sourcesup, etc.

The generic content was a mix of informal discussions, and technical presentations (and debates) in order to try and improve collaboration and interoperability among these forges. A proposal that has emerged from the discussions is to try and use more than today the PlanetForge RSS agregator and wiki (and lists), as an open community gathering people from various forges, in order to improve shared knowledge, inform of ongoing developments and more generally favour collaboration of tools.

On FusionForge side, there were many more precise discussions on topics like roadmap, organization, release, quality process, governance, marketing, contributions, packaging, etc.

There will probably be more detailed reports, but I should express my thanks to all those who came (sometimes from abroad, like Korea and Germany) to make this a very fruitful meeting.

We intend to held such meetings every now and then, and maybe at the beginning of the summer, still under the umbrella of the COCLICO project, but probably organized more around PlanetForge.org.

I hope this will have a positive impact on the dynamics and collaboration between projects, and on the global forges ecosystem in the future. See you next time.

Among the tools offered by SF.net we will use a blog (wordpress), the wiki (mediawiki) and the SVN, for a start.

The project’s SVN repo will be populated with all components we have developed, as we progressively switch our SVN hosting. The first piece we have committed is the Mantis OSLC REST server module.

Pour plus de détails veuillez vous référer à l’annonce en anglais : FusionForge developers/users meeting coming up, notamment pour les détails sur le contact des organisateurs.

OSLC-CM is quite young and only so far implemented in proprietary tools (although elaborated in an open way) on the server side, and as we believe in FLOSS, we’ve started trying to implement basics of server side plugins for a few bugtrackers.
In addition to a demo server that’s simulating the behaviour of a bugtracker, we have started implementing a Mantis plugin and FusionForge and Codendi trackers add-ons (all PHP and based on Zend framework, see this project on picoforge). All are very basic, but we hope they will be the basis for future OSLC-CM compatible servers in these tools.

At the same time we’ve been experimenting with the code already published in Mylyn to support OSLC-CM on the client side. Not everything is public yet in Mylyn, as the elements that have been developped for some connectors of Tasktop to the proprietary tools are being ported to the open source code of Mylyn.
We have thus been able to use the Junit tests classes of Mylyn and tweak them in a way to connect to an instance of the demo server for Mantis (including handling some Basic auth), and be able to retrieve the first bugs descriptions

Now that this works, we’ll try and add some Java code (maybe reusing Mylyn client libs) to doc4 (being developped as part of Helios) in order to start linking doc4 and Mantis so that this can be used in the Helios platform. This may involve mixing code of XWiki and Mylyn… hmmm… well, we’ll see.

Next steps may be also to try and implement a connector in Python that might be used in tools like bts-link.

Then whichever Python or Java client libraries we have, will allow us to use them inside FetchBugs4.me to connect and harvest bugs of OSLC-CM compliant bugtrackers eventually.

Lots of interesting developments ahead. Stay tuned.

Biblio entry : DANG Quang Vu, BAC Christian, BERGER Olivier, VLASCEANU Valentin, Supporting situation awareness in FLOSS projects by semantical aggregation of tools feeds. The 5th International Conference on Signal Image Technology and Internet Based Systems (SITIS’09), 29 november – 04 december 2009, Marrakech, Morocco, 2009

At all good libraries soon

Here’s the abstract :

It is rather difficult to monitor or visualize what can be the contribution of a member in a collaboration project, especially when the project uses multiple tools to produce its results. This is the case for collaborative development of FLOSS software, that uses Wiki, bug tracker, mailing lists and source code management tools. This paper presents an approach to data collection by using aggregation of feeds published by the different tools of a software forge. To allow this aggregation, collected data is semantically reformatted into Semantic Web standards: RDF, DC, DOAP, FOAF and EvoOnt. Resulting data can then be processed, re-published or displayed to project members. We implemented this approach in a supervision module that has been integrated into the PicoForge platform. This module is able to draw a live graph of the social community out of the different sources of data, and in turn exports semantic feeds for other uses.

The package was not really maintained, and twiki’s maintenance still required some attention, as there were quite a lot security issues. So the removal is logical.

I had tried and help maintain it in good shape, but couldn’t do much recently, as we’ve moved a little bit away from its inegration in PicoForge, having other matters to care for in Helios and Coclico these days.

Maybe foswiki (the more open fork of twiki) will enter Debian some day. The ITP is there, and there are unofficial packages to be tested, for those that would need to transition from the previous installations of twiki on Debian. More details in the fowsiki ITP.

Anyway, thanks for all the good work to all those who spent time working on TWiki’s packages in Debian.

As for me, maybe some day, I’ll be interested in contributing some time to Foswiki, should we deploy it alongside FusionForge some day.