>> The only remaining question are about who could spend his time in
>> evaluating the requests and whether he is allowed to close the requests
>> that seems to be wrong (or set them to pending status so that the
>> originator can response).
> I do it from time to time, and check bugs, assign them to the one or the
> other developers, etc... But a few more helpers from our community could
> be of help (I think I made a proposal in this direction a while ago).
> If there is an agreement on the principle, and if an admin is ready to
> give the necessary rights to the nominated users, I could drive this (or
> someone else, Ray?).
I have just had a long chat with Dan (8 pm - 10:30 pm) about different
qustions, and we have agreed that we could define a role responsible for
the initial bug analysis including
1. Evaluating of the bugs,
2. Rejecting (closing) of the non relevant stuff,
3. First level user support,
4. Assigning a priority,
5. Assigning of the bug to the developer.
The goal of this role is to make sure that all bug reports are read,
that they get priorities and that the important reports are assigned to
developers. I have understood Dan so that he has no objections again
giving the responsible person necessary rights in the tracker system,
and I could do so if it is becomes relevant. We have also agreed that
some time after the role is introduced, this decision can be reviewed
In this sense I would be very glad if Eric (or Ray) could coordinate
this important task or find a person who could do it.
The other issues we have discussed today were about
* Bugs in SimplyHTML,
* Memory consumption report,
* Beta 16 (I have built and uploaded the release today, but it still
should be tested and is currently hidden).
I shall write a short protocol of our chat next week as I come back home
(I am away at the week end).