Gentoo Archives: gentoo-dev

From: Tom Wijsman <TomWij@g.o>
To: hasufell@g.o
Cc: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] about inactive project members/leaders
Date: Tue, 15 Oct 2013 21:25:56
Message-Id: 20131015232544.47046f3a@TOMWIJ-GENTOO
In Reply to: [gentoo-dev] about inactive project members/leaders by hasufell
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Hello
5
6 As you have just affirmed the undertaker's lead decision; this mail
7 now rather serves as questions and argumentation for future reference.
8
9 On Tue, 15 Oct 2013 22:16:43 +0200
10 hasufell <hasufell@g.o> wrote:
11
12 > -----BEGIN PGP SIGNED MESSAGE-----
13 > Hash: SHA1
14 >
15 > I wonder if undertakers should also check for inactive project
16 > leaders/members remove them from the projects in case there has
17
18 Why? What makes this an improvement over what we already do?
19
20 Is there an actual need for this? What triggered this thought?
21
22 > not been any activity for a while, regardless of the internal project
23 > structure.
24
25 How would you define activity? Commits? Discussion? Presence?
26
27 > Authority does not only come with knowledge, but also with commitment.
28
29 Commitment and for example commits are two different things; so, the
30 meaning of activity is a crucial thing to understand this metaphor.
31
32 > If no one disagrees, then we should add this to the list of
33 > undertakers competence.
34
35 This competence should not be a rule or a job; rather, it should be the
36 exception. It is already rare for this to happen in a project; so, if
37 we start forcing this to happen a bit more often (as that's the effect
38 this action will lead to) it is simply going to hurt more people.
39
40 Unless, of course, there is a good reason to; I wonder if there are any
41 projects where the lead is blocking progress, unresponsive, ... in a
42 way that affects Gentoo as a whole without members speaking up about it.
43
44 As for project members, I think this is up to the lead to determine.
45
46 Scanning the project list, I do not see anything really problematic;
47 so, I think we are discussing something that is not an actual problem.
48
49 - --
50 With kind regards,
51
52 Tom Wijsman (TomWij)
53 Gentoo Developer
54
55 E-mail address : TomWij@g.o
56 GPG Public Key : 6D34E57D
57 GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
58 -----BEGIN PGP SIGNATURE-----
59 Version: GnuPG v2.0.22 (GNU/Linux)
60
61 iQEcBAEBAgAGBQJSXbLYAAoJEJWyH81tNOV9+sgH/ilMI8Ey+woviXyJUaHgi/Wj
62 gLM5Bmf5eGbEmDr1bhevkIJ2wLc26D1P+aICiW+GIiLaeQw+w1WDxzvZKmozI6QJ
63 dJFqU6/qoktxTy+bsW2nCqUkQzHU3ZfQ5pBxsQ/ovUDKdyUaPLqG1nFRjUX1zXLi
64 7tEKN9JfOiUOBgENasOEnH8wLRMU+Mk03JOplYI4PcPVKFOoYDGYh8u60SUh1e5M
65 PwQ4/qmIuRF5XC2BT1F3FcBS77ZuX+2KbEy66IwH2tnydhC9NowxF0gzSDlwiMAr
66 bXiBnZveuvYNiSk6CQE70Yjtrbq8QUQsAWg6B6WpffLypSLbJ1EJA61y554k0hE=
67 =xpa7
68 -----END PGP SIGNATURE-----