While the bug tracker be a sparkling evidence of the resolve and commitment of this here fine community, it is not equally clear in it's intrinsic do's and dont's.
So ... my questions are these:
1) Is there a project manager prioritising the bugs and assigning the fine programming resources from this community to each bug? Be this gentleman the mod compiler himself? Or be he 'not at all' and thus only a phantom born out of common sense amongst the contributers? (I truly trust that there is a lot of communications going on behind the scenes amongst the contributers).
2) I have been bold enough to report a bug on the bug tracker! Am I responsible for changing it's status when a build update solves the thing? Or is this a task for the person solving the bug? Or maybe a task for the head honcho whomever he be?
3) In short ... what are my responsibilities after having reported a bug on the buggar <img src="style_emoticons/<#EMO_DIR#>/type_1.gif" style="vertical-align:middle" emoid=":nk" border="0" alt="type_1.gif" />
All the best
Frans
So ... my questions are these:
1) Is there a project manager prioritising the bugs and assigning the fine programming resources from this community to each bug? Be this gentleman the mod compiler himself? Or be he 'not at all' and thus only a phantom born out of common sense amongst the contributers? (I truly trust that there is a lot of communications going on behind the scenes amongst the contributers).
2) I have been bold enough to report a bug on the bug tracker! Am I responsible for changing it's status when a build update solves the thing? Or is this a task for the person solving the bug? Or maybe a task for the head honcho whomever he be?
3) In short ... what are my responsibilities after having reported a bug on the buggar <img src="style_emoticons/<#EMO_DIR#>/type_1.gif" style="vertical-align:middle" emoid=":nk" border="0" alt="type_1.gif" />
All the best
Frans