Gentoo Archives: gentoo-project

From: "Robin H. Johnson" <robbat2@g.o>
To: gentoo-project@l.g.o
Subject: [gentoo-project] Groups under the Council or Foundation: the structure & processes thereof
Date: Wed, 12 Oct 2016 23:30:31
Message-Id: robbat2-20161012T222256-006623850Z@orbis-terrarum.net
1 TL;DR: move comrel, infra, PR to Foundation. Have strict(er) application
2 of policies to them in line with their powers.
3
4 I've deliberately broken the thread, but also include some history in
5 the origins of the groups.
6
7 On Mon, Oct 10, 2016 at 11:05:39PM +0100, Roy Bamford wrote:
8 ...
9 > Council have an annual mandate from the body of Gentoo devs.
10 > Devrel had a mandate from council but that's not been renewed since
11 > 2007, unless I missed a vote somewhere.
12 ...
13 > On 2016.10.07 16:09, Rich Freeman wrote:
14 ...
15 > > I think it makes far more sense to have Comrel vetted by the Council.
16 > > If you don't trust somebody to be wielding that power, you shouldn't
17 > > put them on the Council.
18 > That addresses lots of concerns all in one go.
19 >
20 > Comrel get their annual mandate. The community know that council
21 > are peeking into comrel to see if its still alive and that its still
22 > operating as intended. Its more work for council to do the job
23 > properly.
24 >
25 > It also means that council members would see things that they
26 > don't usually see unless there was an appeal. Thus council can
27 > provide a general assurance to the community about all the good
28 > things comrel do that are currently privileged.
29 To make a radical suggestion, I'm wondering if it might be considered to
30 put some organizational group responsibilities under the Foundation
31 instead, while to establish others formally of the Council.
32 In some parlance, they might be considered as appointed/'hired' staff or
33 committee members of the management bodies, while the bodies themselves
34 remain elected.
35
36 I've used 'contributors' as a descriptor below, because the CoC should
37 be applies to both developers & users & non-users alike: all
38 participants in any Gentoo-associated media, mailing lists, IRC
39 channels, message boards etc.
40
41 I've also tried to avoid using our existing term 'project', because some
42 of the group responsibilities do not fit well into the project structure
43 of GLEP39.
44
45 I joined Gentoo in 2003, and a lot of the groups were already in
46 existence, whilst only a few came later.
47 - PR, Devrel, Infra are some of the oldest groups inside Gentoo:
48 they were listed in GLEP-4 as of 2003/06/30, as pre-existing entities
49 within the distribution. GLEP-4 made the groups them into
50 top-level-projects.
51 -- Recruiters were an offshoot from the original Devrel:Newdev sub-project
52 -- QA is also present in that document, but bears little resemblance to
53 the original group.
54 - Foundation's origins (2004, 2007 all-new) are in ensuring that the
55 distribution is organizationally (legally & financial) sound.
56 - Council's origins (2006, GLEP39) are in handling global issues and
57 those that cross GLEP39-project boundaries, both to ensure that the
58 distribution is technically sound.
59
60 The establishment of the Council & GLEP39 mostly placed all of the
61 existing groups as reporting to the Council, and therein problems have
62 ultimately arisen. As noted by the fact that Devrel's mandate wasn't
63 formally renewed.
64
65 The responsibilities of some of the older groups can & do cross the
66 technical/organizational boundaries, whilst others fall clearly into one
67 side.
68 - Infra gets sponsorship & Foundation funds to ensure hosting & services
69 keep running for the distribution's needs. Legal compliance that what
70 we run complies with laws.
71 - PR promotes the distribution (via the banners for conferences,
72 merchandise), trademark usage questions often come here.
73 - QA is a technical function, and clearly belongs to the Council.
74 However it's enforcement powers suggest that it might not be just a
75 GLEP39-project.
76 - ComRel falls more into the side of organizational than technical:
77 -- CoC issues with contributors
78 - Recruiters have historically functioned mostly to ensure that new
79 contributors seeking to become developers are technically sound, and
80 to a lesser degree that they are a social fit for the distribution.
81
82 So how do we improve things?
83 1. Move some of the groups, to the Foundation.
84 2. Clearly define&change their rules of group formation.
85 3. By accepting roles/responsibilities in these groups, a contributor
86 MUST agree to uphold strong principles (eg, rules for employees in an
87 organization are stricter/more-binding than those of customers, and
88 strongly derived from federal/state laws & regulations).
89
90 Anybody should be able to apply to join the groups, but their joining
91 should be vetted by some level: The council members (possibly in
92 collaboration with the Foundation trustees) might wish to appoint, for
93 limited terms, group leaders and/or members. It's also possible the
94 group leaders in themselves might have a role in suggesting new members
95 to Council or the Foundation for approval.
96
97 --
98 Robin Hugh Johnson
99 Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer
100 E-Mail : robbat2@g.o
101 GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
102 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

Replies