Tasks and project management

The project follows this process to make sure the necessary tasks are completed:
 * 1) The list of pending tasks that need to be assigned are posted on the mailing-list (this can be done by hand at first, but we'll probably want to automate it), to give everyone a chance to take care of one of those tasks
 * 2) During weekly meetings, we look at the tasks that remain to be assigned, to attribute them among the people who are present at the meeting, but also to propose them to people who are not there but could be good at it (the tasks are assigned in the bugtracker, but the person can of course refuse!)
 * 3) The person who gets the task chooses the deadline, but it can be challenged by anyone in the tracker (this doesn't necessarily happen during the meetings).

We could even improve this later on, by building a database of competencies, and only emailing contributors with a set of task corresponding to those competencies.

It also means that the tasks must always be described in a way that allows someone without the context to understand what needs to be done precisely.