Tag: bugtracker

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.

We’re hiring a FLOSS developper to work on bugtrackers synchronisation

We’re hiring a software engineer, for 15 months, to work on bugtrackers synchronisation

(see full version of the offered job description here — et une version en français également : ici)

We’re looking for a software engineer to join our PFTCR team, in order to complement our R&D manpower on the HELIOS project. We’re responsible for a work package whose goal is to study and implement a system which would fit in the HELIOS platform, to ensure synchonisation between bug-trackers.

The workplace would be here in Evry (France, Paris area) for a duration of 15 months, under a french CDD contract (starting first quarter of 2009). The development done during the work on this project will be contributed back to FLOSS projects.

Strong know-how in software development as well as interest for research issues are expected from the candidates. Also, a good knowledge of the open source development tools, and of the dynamics of the libre software development communities is expected (distributions, packaging, QA). A practical experience of contribution on an open source project would be a plus (typically as Debian developper, for instance).. Technical english skills will be required (as well as notions of french, considering the french nature of the environment).

If you’re interested and available early 2009, I definitely want to hear from you.
See more details in full version of the offered job description.

Adding GForge bugtracker support in bts-link

Part of our work in the Helios project will be on bugtrackers synchronisation.

I happened to notice that bts-link‘s maintainer called for help, which triggered more interest in that tool.

I’ve started working on bts-link to see how it works (cool, it’s Python 😉 and if it can be useful for Helios, and started implementing GForge tracker support in bts-link. That should help keep track of Debian bugs wrt upstream bugs for projects hosted in GForge forges (like Sympa, for instance, whose bugtracker is hosted in SourceSup).

You may find my git repo at http://www-public.it-sudparis.eu/~berger_o/git/bts-link.git which hopefull contains my proposed changes (I’m new to git, so I hope I did everything right…).

Introducing project HELIOS

We’ve been setting-up the codename HELIOS project, together with other partners (lead by Thales), which got funded recently, as part of the pôle de compétitivité System@tic (libre software thematics).

That means that our PFTCR team at Institut TELECOM will be able to do more research around infrastructure and process of production for libre software projects.

Among the things we’ll focus in particular in this 2 year project, is the topic of traceability between bugtrackers (WP3). This topic seems quite interesting to many people I’m talking to at the moment in libre software projects (as discussed recently at RMLL/LSM) : good 😉

I hope we’ll be able to help improve the current state of the art where lots of manual synchroniation is done in libre software (between upstream bugtrackers and distributions’ ones, for instance), and deliver useful tool to the communities.

We’ll keep you posted as the project moves on (scheduled kickstart september 2008).

For more details (in french), you may see the brochure (page 4) at System@tic’s site.

Update 2008/09/17 : here’s the official description of the project we’ve just drafted :

HELIOS is a project related to the System@tic research cluster. The aim of the project is to provide an Open Source ALM (Application Lifecycle Management) portal allowing to test, integrate, configure and maintain the many components of an application. HELIOS must be flexible and extensible enough to adapt to any tool with limited developpements in order for the users to keep on using their own tools. In the same way, flexibility and extensibility should allow services providers to build commercial offer. Most of existing ALM tools are specialised into one particular field (requirements management, qualification, project management, …) but the HELIOS project will aim at providing a complete platform covering activities from qualification to maintenance.

Report from LSM/RMLL 2008 on communautary development track

There’s probably much more to say than I’ll remember, but here’s an attempt at reporting from the excellent edition of RMLL/LSM which was held in Mont-de-Marsan (France) early july.

I’ve been chairing one of the tracks, on Communautary development, where I’ve had the pleasure to chair and attend excellent presentations. The rest of the LSM/RMLL was very good too, but being stuck in a room, I couldn’t attend much of it 😉

To summ-up, there have been very interesting talks and discussions on the following subjects (links to descriptions of talks and their slides included) :

  • translations : Claude Paroz has presented the classical process of translation in libre software (gettext, etc.) and organized a practical workshop to help get contributors started. But just before his talk, Marc Laporte (aka the man paying free beers at night) presented a system which was implemented in a wiki to handle multilingual content, which seems very smart, in helping synchronize multilingual content in wikis (where individual translations may change in a non-coordinated way). I think that both talks were very complementary : great to have had both speakers there… and by the way, they proved the international nature of the RMLL (Switzerland and Quebec/Canada) 😉
  • forges : another topic was the forges, or the development environments in (potentially) large projects, with the presentation of the forges genealogy and the GForge project made by Roland Mas. It was interesting to get feedback from the audiance where people reported from their switch to GForge AS, for instance. Also a presentation by Quang-Vu Dang about the use of semantic web standards to monitor activity in forges. We also discussed the semantic web standards and interoperability after other presentations about bug-tracking or packages (more bellow). Lucas Nussbaum also presented the infrastructure of the Debian project which loosely integrates different tools which are used to monitor the activity and do the QA work in the project. Lucas’ presentation was too short unfortunately, for such a complex project in-depth review (and trolls popped-up also ;).
  • packaging : Lucas also presented interesting starting elements for attracting volunteers contributions to Debian, by describing the packaging of applications in Debian (and Ubuntu, sort of ;-). Complementary were the presentations by Vincent Untz and Bruno Cornec, resp. on the OpenSUSE build service, and Project Builder, which both more or less manage the generation of packages for various distributions. Their philosophical approch seem different, which lead to interesting discussions : is upstream supposed to get interested in specifics of package contruction in various distributions, or should it be handled independently ? Great debate. There were also intersting talks about convergence in package description formats, which would need more detailed discussions (I welcome any links).
  • Release process : we had three talks which addressed this topic : first the excellent (and crowded, although very early in the morning : 9:00 😉 ) presentation by Thomas Petazzoni on the Linux project process. Next Lucas’ presentations on Debian (comparing release strategies between Debian and Ubuntu, for instance). And finally Vincent Untz’s other presentation on the 6 month paced release process in Gnome. Very complementary and interesting talks, IMHO.
  • Bug tracking : Of course this was the topic addressed by Emmanuel Seyman in his very interesting talk about Bugzilla. But we also discussed the subject of bug trackers in Lucas’ presentation, for instance (with the Debian BTS), or when we discussed the problem of synchronisation of the bugs lists between upstream and distributions (which will be one of the topics of our forecoming HELIOS project : more blogging ahead). Definitely something where the contacts were very valuable amond people attending and presenting.
  • Other topics : well, that wasn’t all with this track at LSM/RMLL, but I wasn’t as much interested in these others I guess. You’ll find more details on the conference’s site.

I hope the content was enjoyable to the audiance too (although I disturbed the presentations with my silly jokes or my facist approach to schedules ;).

See you in next edition.