Gentoo Archives: gentoo-project

From: Roy Bamford <neddyseagoon@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] rfc: comrel changes
Date: Tue, 18 Feb 2020 22:54:13
Message-Id: JSDQLHYG.SFD54TUD.ZIBAFUSX@DQ7THBCL.5KQ6YGKS.WLTNKBF2
In Reply to: Re: [gentoo-project] rfc: comrel changes by Matt Turner
1 On 2020.02.18 22:06, Matt Turner wrote:
2 > On Tue, Feb 18, 2020 at 12:13 PM Alec Warner <antarus@g.o>
3 > wrote:
4 > >
5 > >
6 > >
7 > > On Mon, Feb 17, 2020 at 8:18 AM William Hubbs <williamh@g.o>
8 > wrote:
9 > >>
10 > >> All,
11 > >>
12 > >> I realize that comrel is a thankless job, but it is an important
13 > one
14 > >> that helps preserve the health of the community.
15 > >>
16 > >> To facilitate this, I think we need to have some changes in the way
17 > comrel
18 > >> operates, so I would like to propose them here to see what other
19 > folks think.
20 > >>
21 > >> Since comrel is a special TLP like QA, I think the comrel lead,
22 > like
23 > >> the qa lead, should be confirmed by the council.
24 > >>
25 > >> When an issue is filed with comrel, the issue should be addressed
26 > >> within a reasonable time frame. As someone who has filed issues, I
27 > have
28 > >> seen them sit for months with no action taken.
29 > >> With all respect to comrel, this is unacceptable. You have a
30 > published
31 > >> policy for how you will process issues, so follow it. If you don't,
32 > it
33 > >> is very upsetting for users/developers who reach out to you for
34 > >> assistance, weakens your credibility, and by extension negatively
35 > affects the
36 > >> reputation of the entire Gentoo community.
37 > >>
38 > >> To promote more transparency with comrel, I would like to
39 > >> require the comrel lead to send a report to the gentoo-project list
40 > monthly
41 > >> containing these statistics for the previous month:
42 > >>
43 > >> - number of bugs received
44 > >> - number of bugs pending (this is for bugs that are currently in
45 > process)
46 > >> - number of bugs resolved by actions (such as talking to
47 > >> developers or disciplinary action)
48 > >> - number of bugs closed without action
49 > >>
50 > >> - number of mediation requests received
51 > >> - number of mediation requests resolved
52 > >> - number of mediation requests escalated to bugs
53 > >> - number of mediation requests dismissed without action
54 > >>
55 > >> The comrel lead should be replaced if this report is not sent for
56 > three
57 > >> consecutive months.
58 > >>
59 > >> What do others think?
60 > >
61 > >
62 > > I'm a little bit concerned that this addresses the symptoms instead
63 > of the problem. Have you shared your concerns with comrel regarding
64 > their lack of timely communication on reported issues? Do they even
65 > share the same goals you enumerated?
66 > >
67 > > My strawperson argument is that:
68 > > - (0) The council will elect some lead.
69 > > - The lead will never write reports (or write them but stop.)
70 > > - The lead will get removed per policy.
71 > > - Council will elect a new lead.
72 > > - GOTO 0
73 > >
74 > > This isn't to say I dislike the concept of publishing transparency
75 > report (I do like it) but I'm not sure a report completely solves the
76 > problems that comrel actually faces today and I'd be interested to
77 > learn more about
78 > >
79 >
80 > I've discussed it with William (and am a member of ComRel). The hope
81 > is that transparency reports will dissuade ComRel from ignoring
82 > reports.
83 >
84 > I've heard from other ComRel members in favor as well, FWIW.
85 >
86 > I think we're entirely open to suggestions.
87 >
88 >
89
90 Metrics allow the current state to be measured and compared to
91 future states. They are the first step in gauging the magnatude of
92 a problem, if one exists.
93
94 Metrics won't help fix any problems though. Fixes require causes
95 to be established and addressed, which in turn requires that the
96 operation of comrel be looked into somehow.
97
98 --
99 Regards,
100
101 Roy Bamford
102 (Neddyseagoon) a member of
103 elections
104 gentoo-ops
105 forum-mods
106 arm64