Gentoo Archives: gentoo-dev

From: Denis Dupeyron <calchan@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Council meeting 19 April 2010
Date: Wed, 07 Apr 2010 15:00:55
Message-Id: n2r7c612fc61004070800k1355c793g753cb94c2bbd3c5c@mail.gmail.com
In Reply to: Re: [gentoo-dev] Council meeting 19 April 2010 by Ben de Groot
1 On Wed, Apr 7, 2010 at 8:23 AM, Ben de Groot <yngwin@g.o> wrote:
2 > 1. reconsider metadata changepolicies proposal
3 > ==============================================
4 [...]
5 > Can council please decide to honor
6 > the wish from developers to implement this?
7
8 The council will be glad to vote on a GLEP when ready. From GLEP 1,
9 GLEPs are the "primary mechanisms for proposing significant new
10 features, for collecting community input on an issue, and for
11 documenting the design decisions". So use them.
12
13 Also, you might want to check the log and summary of the last meeting
14 to find out why the council may end up voting no to such a GLEP.
15
16 > 2. website redesign
17 > ===================
18 [...]
19 > Can council assure that a team will be assembled that can
20 > effectively tackle this issue?
21
22 You want the council to aim their collective gun at volunteer
23 developers and force them to assemble in a team and work on something
24 they might not want to work on?
25
26 In other words, if you want it then work on it and make it happen.
27 This is and has always been the Gentoo way.
28
29 > 3. manpower and recruitment issues
30 > ==================================
31 >
32 > Another recurring theme is the lack of manpower in certain areas, the
33 > recruitment bottleneck and the quizzes. There are some initiatives but
34 > more decisive leadership is needed. Can council decide to actively
35 > pursue solutions for these structural problems?
36
37 The only way to solve this is to address these issues where they are.
38 That means joining the recruiters team and helping them with that.
39 Another thing you might want to do is properly mentor recruits.
40 Because one reason recruiting takes so long, and thus why there is a
41 backlog, is (to put is simply) that mentors suck at mentoring.
42
43 > 4. devrel ineffectiveness
44 > =========================
45
46 In case you haven't noticed there was a recent change of devrel lead.
47 This means it is urgent to wait for the results of the change. Because
48 you never know, it might just be that the change of lead was intended
49 to solve such things at a perceived devrel ineffectiveness.
50
51 > 5. centralize developer documentation
52 > =====================================
53
54 This is an interesting idea which I believe I have seen discussed on
55 irc at some point. Feel free to work on a GLEP to address that.
56
57 Before we go any further, let me make the following PA announcement:
58
59 1 - If you want to improve a project or subproject the best (and
60 often only) thing to do is to join it.
61
62 2 - The council isn't a super-nanny metaproject with enough magical
63 powers to solve each and every of your oh-so-annoying problems. We do
64 have magic wands but you don't want to see them.
65
66 Denis.

Replies

Subject Author
Re: [gentoo-dev] Council meeting 19 April 2010 Ben de Groot <yngwin@g.o>
Re: [gentoo-dev] Council meeting 19 April 2010 Richard Freeman <rich0@g.o>
Re: [gentoo-dev] Council meeting 19 April 2010 "Petteri R├Ąty" <betelgeuse@g.o>