1 |
All, |
2 |
|
3 |
I realize that comrel is a thankless job, but it is an important one |
4 |
that helps preserve the health of the community. |
5 |
|
6 |
To facilitate this, I think we need to have some changes in the way comrel |
7 |
operates, so I would like to propose them here to see what other folks think. |
8 |
|
9 |
Since comrel is a special TLP like QA, I think the comrel lead, like |
10 |
the qa lead, should be confirmed by the council. |
11 |
|
12 |
When an issue is filed with comrel, the issue should be addressed |
13 |
within a reasonable time frame. As someone who has filed issues, I have |
14 |
seen them sit for months with no action taken. |
15 |
With all respect to comrel, this is unacceptable. You have a published |
16 |
policy for how you will process issues, so follow it. If you don't, it |
17 |
is very upsetting for users/developers who reach out to you for |
18 |
assistance, weakens your credibility, and by extension negatively affects the |
19 |
reputation of the entire Gentoo community. |
20 |
|
21 |
To promote more transparency with comrel, I would like to |
22 |
require the comrel lead to send a report to the gentoo-project list monthly |
23 |
containing these statistics for the previous month: |
24 |
|
25 |
- number of bugs received |
26 |
- number of bugs pending (this is for bugs that are currently in process) |
27 |
- number of bugs resolved by actions (such as talking to |
28 |
developers or disciplinary action) |
29 |
- number of bugs closed without action |
30 |
|
31 |
- number of mediation requests received |
32 |
- number of mediation requests resolved |
33 |
- number of mediation requests escalated to bugs |
34 |
- number of mediation requests dismissed without action |
35 |
|
36 |
The comrel lead should be replaced if this report is not sent for three |
37 |
consecutive months. |
38 |
|
39 |
What do others think? |
40 |
|
41 |
Thanks, |
42 |
|
43 |
William |