Code

In my professional and personal activities, I contribute to some open-source projects. You’ll find a summary of all my contributions on my Ohloh profile.

Currently, I’m more or less involved in these open-source projects:

Live browser

  • Description: test web app based on CherryPy, Mako and MongoDB to play with Microsoft Live Messenger Connect API.
  • Role: sole author.
  • Source code: on GitHub.

openerp.buildout

  • Description: an attempt to automate an OpenERP server and web client.
  • Role: sole author.
  • Source code: on GitHub.

CherryPy + Mako + Formish + OOOP boilerplate

  • Description: boilerplate codebase to publishing some OpenERP content on the web.
  • Role: sole author.
  • Source code: on GitHub.

WebPing

  • Description: a tool to check availability of remote web pages.
  • Role: sole author.
  • Source code: on GitHub.

e107 Importer

  • Description: a WordPress plugin to import news, users, pages, images and forums from an e107 instance.
  • Role: sole author.
  • Source code: on GitHub (main repository) and in official WordPress Subversion (synced repository).

Feed Tracking Tool

  • Description: web-based RSS/Atom feed aggregator running on Ruby on Rails.
  • Role: co-author.
  • Source code: on GitHub.
  • Related articles: http://kevin.deldycke.com/tag/feed-tracking-tool/

Scripts

  • Description: a collection of utility scripts, patches and hacks.
  • Role: sole author.
  • Source code: on GitHub.

pbp.recipe.trac

  • Description: Python’s buildout recipe to ease management and deployment of multiple Trac instances.
  • Role: contributor.
  • Contributions: code.

Plone

QLC

WordPress

bbPress

  • Description: WordPress-based forums.
  • Role: contibutor.
  • Contributions: bug reports.

Kdenlive

  • Description: a non-linear video editor written in QT for KDE.
  • Role: contributor.
  • Contributions: feature requests.

nlconverter

  • Description: a Lotus Notes to Mailbox conversion tool written in Python.
  • Role: contributor.
  • Contributions: code.

On the status of my projects…

These projects are mostly one-time scripts, very old and very specific. I doubt you’ll be able to use them as-is. Until you update and tweak them to fit your needs. In this case, don’t hesitate to send me code and patches. Basically, that’s why all this code is hosted on GitHub: to ease fork and contributions.

The code here is generally poorly written. Either because my coding style has improved since I wrote them, or because I didn’t bother to make the code elegant after I finished my first working iteration.

All these projects are kept in a dormant state. That’s another way to say that they’re inactive, and I no longer maintain them. But I let me the possibility to reactivate them depending on my needs or external contributions.

Before reporting me bugs, make sure that you already read the famous “How to Report Bugs Effectively” document. Else, both you and me will waste precious time.

This mean that I refuse feature requests. Until you implement them and send me code. I only accept patches and contributions.