Gentoo Archives: gentoo-dev

From: Daniel Drake <dsd@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Gentoo metastructure reform poll is open
Date: Wed, 08 Jun 2005 15:08:02
In Reply to: [gentoo-dev] Gentoo metastructure reform poll is open by Daniel Drake
1 Daniel Drake wrote:
2 > - Form a task force for additional study ("Task-Force")
3 > -core mail (7 June 2005) from jstubbs, 42A4D555.7010009@g.o
4 > (will be available on gentoo-dev as a response to this message)
6 Jason Stubbs' proposal:
8 I'm past this deadline, but I'd like to propose a modified "keeping it the way
9 it works (fails) now". My motivation is that I don't feel any of these
10 proposals will solve the issues at hand in the long run. You may call it
11 `Jstubbs' "Task Force" proposal`. ;)
13 At the outset I will explicitly state what seems to be implicit in the other
14 proposals. If this proposal is allowed to be entered into the ballot and ends
15 up being ranked highest, a ballot on the positions of top-level managers
16 would ensue. The number of positions and the projects would remain the same
17 in the short term.
19 The "Task Force" part of the proposal is that a new top level project be
20 created to specifically deal with how the organization functions. Its role
21 would be to document and improve all structure, policies and procedures.
22 However, it would have no power to enforce them. All policies and procedures
23 must be signed off on by the top-level managers for them to become
24 enforcable. For this reason, the task force would not be represented within
25 the top-level managers. Think of it as the organizational ombudsman.
27 In the short term, the goals would be to get policies and procedures
28 documented and approved that prevent stagnation within the top-level
29 managers. The main aim here being the ability to transition to one of the
30 proposals above or to some entirely different structure should documentation
31 prove it to be appropriate.
33 Medium term goals would be to step in and help other projects get their
34 procedures documented where need be. And in the long term, the aim would be
35 to have policies and procedures documented for everything.
37 Just to quickly preempt the main negative to this proposal, policies and
38 procedures don't mean you have to behave like a robot. Policies are only ever
39 a recommendation that serve to create a common direction. Procedures are only
40 ever a list of steps that are known to work. They are more of a safety net
41 than anything else. In either case, if you follow it and stuff up - even
42 badly - it is a fault of the policy or procedure.
44 And no, I don't have a name for the project yet although, looking back at the
45 projects page, I think I've just describe what the existing "metastructure"
46 project *should* be doing. So... worth putting on the ballot?
48 Regards,
49 Jason Stubbs
50 --
51 gentoo-dev@g.o mailing list