That's always a good surprise, when coming back from week-end, to see that the project did not sleep during the last two days... at least, if we trust SourceForge project activity! It rose from 99.98% (when I left the office friday evening) to 99.99% when I came back this morning (monday) - having its best rank (#20) on saturday and sunday. I am thinking of telling the dev team to go on holiday for a while, maybe the project will then go on by itself... (ok, I suppose that SourceForge activity is computed not only for the previous day, but is an average of the past few days - but anyway, I always find this funny).

Speaking of the project activity, you may wonder how many people are involved in the project. There are not less than 24 members registered on SourceForge - but not all those people are actually developers (there are a lot of testers), and among the developers not everyone is working full time on the project. In fact the size of the dev team varies quite a lot - especially during summer, which is traditionaly a good period for vacation here in Europe. There are currently (I mean: today - tomorrow is another day) one project leader and four developers working on the project in France, and three developers in Poland. And there must be some testers doing the tests on the latest snapshot - I don't know the exact number as they work for different companies: DIaLOGIKa in Germany and AztecSoft in India.

We deliver two snapshots a week (monday and wednesday), what allows both the testers to have time to do their job and the community to follow the developments quite closely (but you can also get the current version by accessing the public SVN repository and compiling the sources by yourself). The bugs are reported on SourceForge Bugtracker (there are currently 77 bugs open). We don't use the forums internally, we prefer the mailing lists (we have public and private mailing lists) for the discussions. As SourceForge provides all those tools, it sounds like it was a good choice to host the project on it (we had other options: either an internal solution - based on OSS project TRAC - or Microsoft CodePlex - but we wanted to priviledge visibility and that's why we finally chose SourceForge).