Gentoo Archives: gentoo-nfp

From: Roy Bamford <neddyseagoon@g.o>
To: gentoo-nfp@l.g.o
Subject: Re: [gentoo-nfp] [RFC] Alternative methods for determining 'interest in Foundation affairs'
Date: Fri, 06 Sep 2019 23:26:06
Message-Id: 2VJ5WFOZ.E6ENNR3W.TVHMCN6U@REM4A725.4CEEVXEI.UOMJ6HVZ
In Reply to: [gentoo-nfp] [RFC] Alternative methods for determining 'interest in Foundation affairs' by Michael Everitt
1 On 2019.09.06 17:48, Michael Everitt wrote:
2 > On 06/09/19 15:36, Robin H. Johnson wrote:
3 > > On Thu, Sep 05, 2019 at 06:51:00PM -0400, Rich Freeman wrote:
4 > >> On Thu, Sep 5, 2019 at 6:42 PM Robin H. Johnson
5 > <robbat2@g.o> wrote:
6 > >>> On Thu, Sep 05, 2019 at 01:45:25PM -0700, Alec Warner wrote:
7 > >>>>> 3. It is really meaningless. Casting a vote does not really
8 > indicate
9 > >>>>> any interest in GF. It only indicates that someone has done the
10 > minimal
11 > >>>>> effort to avoid being kicked. There is no reason to conflate
12 > the two.
13 > >>>> I'm certainly interested in other avenues of interest, but I
14 > don't see very
15 > >>>> many in this thread other than "AGM attendance" and "asking
16 > people if they
17 > >>>> are interested[0]"
18 > >>> - Does involvement on mailing lists count?
19 > >>> - What other ways outside development might somebody be involved
20 > in
21 > >>> Gentoo? Not everybody is a developer, let alone an ebuild
22 > developer.
23 > >>> What if we wound up with PR people who weren't devs at all, but
24 > loved
25 > >>> to talk about Gentoo?
26 > >> Gentoo developers do not have to have commit access. If somebody
27 > is
28 > >> doing significant PR work for Gentoo then they should be made a
29 > >> developer. Developers do not need to pass the ebuild quiz.
30 > > I meant "developer" as the generic "one who develops software".
31 > > Ebuilds are not the only code-like activity, there's multiple other
32 > > software packages that Gentoo relies on: openrc, netifrc, genkernel,
33 > > catalyst, eselect are some of them.
34 > > They may have commit access to those packages, and not to ebuilds.
35 > >
36 > > I need to distinguish between:
37 > > - ebuild coding contribution
38 > > - non-ebuild-coding contribution
39 > > - non-coding contribution
40 > >
41 > >> Anybody with an @g.o email address is a developer.
42 > >>
43 > >> We used to use the term "staff" but anybody who used to be
44 > considered
45 > >> "staff" is now considered a "developer."
46 > > I stated when the switch away from "staff" was done, that I felt we
47 > were
48 > > doing ourselves a dis-service by not picking a better word than
49 > > "developer" - something that includes all of the contributions
50 > above,
51 > > without implying specific technical skills. "Contributor" was
52 > down-voted
53 > > at the time.
54 > >
55 > Reading (somewhat extensively) between the lines, there is a subtle
56 > move
57 > for those developing code and ebuilds to "take over" control and
58 > management
59 > of the distribution (cf. electorate of 'council'). Whether this is
60 > something that is (1) really happening or (2) desirable, I shall leave
61 > as
62 > an exercise for the reader; but I thought was probably worth
63 > highlighting.
64 >
65
66 Compare the numbers of staffers to developers.
67 Its not really surprising that developers fill most of the "control
68 and management" roles in the distro.
69
70 There have been staffers on both the council and trustees.
71
72 In my view, your observation is both correct and not
73 statistically significant.
74
75 --
76 Regards,
77
78 Roy Bamford
79 (Neddyseagoon) a member of
80 elections
81 gentoo-ops
82 forum-mods
83 arm64