Gentoo Archives: gentoo-project

From: "Michał Górny" <mgorny@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] A GLEP for ComRel?
Date: Thu, 25 Apr 2019 16:34:06
Message-Id: 267af77554689b414b9606a2d3f0505b116b9481.camel@gentoo.org
In Reply to: Re: [gentoo-project] A GLEP for ComRel? by Matthew Thode
1 On Thu, 2019-04-25 at 11:24 -0500, Matthew Thode wrote:
2 > On 19-04-25 18:14:18, Michał Górny wrote:
3 > > On Thu, 2019-04-25 at 11:55 -0400, Alec Warner wrote:
4 > > > On Thu, Apr 25, 2019 at 10:02 AM Michał Górny <mgorny@g.o> wrote:
5 > > >
6 > > > > Hi,
7 > > > >
8 > > > > Given the amount of discussion GLEP 48 update brought, I'd like to
9 > > > > tackle a semi-related topic: wouldn't it be beneficial to have the role
10 > > > > and policies of ComRel solidified in a GLEP, and officially stamped
11 > > > > by the Council this way?
12 > > > >
13 > > >
14 > > > I'd be excited to see a GLEP to outline the purpose of the Comrel team and
15 > > > its role. I'm less happy to codify the policies in the GLEP. I'd argue that
16 > > > most policies should be decided at the team level (not the council level).
17 > > > GLEP48 itself is kind of a mix of "here is what we think the QA team should
18 > > > be doing" and policies "the QA team will fix typos, etc." I'd perhaps
19 > > > advocate for stronger guidance on separating these concerns.
20 > > >
21 > > > To use an example from our IRC conversation. Rich suggested the Comrel GLEP
22 > > > should contain some kind of wording for privacy expectations. I agree that
23 > > > it should, but I'm not sure it should exactly specify. It might be
24 > > > sufficient to say:
25 > > >
26 > > > [Proctors]
27 > > > You should have no privacy expectation for conversations with the Proctors
28 > > > team, assume all conversations are public.
29 > > >
30 > > > [Comrel]
31 > > > Conversations with Comrel are confidential, but may become non-confidential
32 > > > under (some circumstances){LINK_TO_POLICY_DOCUMENT}.
33 > > >
34 > > > Note that I don't intend for this to mean the council cannot have a say in
35 > > > team policies, but I think it should be more reactionary (users report bad
36 > > > policies, council investigates and takes action) and less proactive
37 > > > (council reviews and approves all policies.) I think if the latter was to
38 > > > happen, you'd need some faster way to get the a council to review and
39 > > > approve things. Like in Infra (another team where a charter might be
40 > > > worthwhile) I'm not sure the council approving our policies adds much.
41 > > >
42 > >
43 > > We could also go for more general 'disciplinary action' GLEP, and make
44 > > individual project (ComRel, Proctors, QA) policies adhere to that.
45 > >
46 >
47 > I'd like to avoid focusing too much on retribution (disciplinary action)
48 > and more on education. I'm sure there are times where action may be
49 > needed but what it sounds like is needed are more genral definitions of
50 > what the relationship between groups should be (how to hand off a high
51 > priority item for review/action).
52 >
53
54 I'd be happy to see ComRel focus more on educating, helping and cooling
55 down conflicts. To my experience, ComRel so far has mostly focused
56 on ignoring requests, threatening people and occasionally issuing
57 punishment.
58
59 --
60 Best regards,
61 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature