1 |
On Monday 14 January 2008, James wrote: |
2 |
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes: |
3 |
> > > It could just be managerial ineptitude though, combined with |
4 |
> > > emotional immaturity of certain persons (if Alan's previous |
5 |
> > > critique re.treating persons as machines holds true). |
6 |
> > |
7 |
> > Odds are that this is the real explanation. Gentoo management is |
8 |
> > full of people who are good devs but simply do not know how to run |
9 |
> > a group. To see this, just read over minutes of meeting etc held on |
10 |
> > IRC. There's little evidence of a meeting being chaired by someone |
11 |
> > who keeps things on track and on agenda, and meetings usually |
12 |
> > devolve into discussions of technical matters. |
13 |
> > |
14 |
> > It's entirely reasonable to assume that these same people will just |
15 |
> > ignore things outside their expertise that they don't understand |
16 |
> > and hope the problem will go away if they ignore it. |
17 |
> > |
18 |
> > Just as the solution to having a maintainer of a project that can't |
19 |
> > code is to replace him with someone who can, the solution to |
20 |
> > gentoo's current woes seems to be to appoint bodies to management |
21 |
> > who do know how to do it and have a track record of doing it. |
22 |
> |
23 |
> OK, let assume you are correct, and the majority of users support |
24 |
> these consensus beliefs. How do we go about doing this (fixing |
25 |
> gentoo with some documents that define the organization and lines of |
26 |
> authority? I know how to do it mechanically and legally but how to we |
27 |
> get devs to agree with being managed by anyone? After all, there are |
28 |
> no paychecks here. |
29 |
|
30 |
I think you have answered your own question actually. |
31 |
|
32 |
It's a common human failing to assume that their own situation is |
33 |
somehow unique and completely different from every other situation that |
34 |
has ever been. Gentooites might well want to debate this ad nauseam but |
35 |
the situation will resolve that same way these things have always been |
36 |
resolved, by one of these or a combination: |
37 |
|
38 |
a. a strong leader emerges with a vision and takes over |
39 |
b. a strong leader emerges with a vision and forks |
40 |
c. common sense prevails and everyone comes to their senses |
41 |
d. a hidden bad egg goes away or dies and suddenly everything calms down |
42 |
e. the project dies and nothing replaces it |
43 |
|
44 |
There might be more options. In any event, to progress someone has to |
45 |
step up to the plate with a plan and put it into motion, and the |
46 |
mechanics will fall into place behind that. Daniel has a plan. It might |
47 |
be a good one or a bad one. He might be The Ultimate Enlightened One or |
48 |
he might be Evil Spawn Of Satan, I have no idea. |
49 |
|
50 |
But he does have a plan, and thus far seems to be the only one |
51 |
*with*a*plan*. Let's hear what he has to say and respond accordingly. |
52 |
|
53 |
alan |
54 |
|
55 |
|
56 |
|
57 |
|
58 |
> |
59 |
> My alluding to the tribal system is because technical folks will |
60 |
> follow a technically strong leader. Are enough of those tribal |
61 |
> (elites) willing to be managed? If so, surely they will want quite a |
62 |
> lot of say in how a new structure to manage Gentoo is structured and |
63 |
> organized. The fact they are discussing this seems like the majority |
64 |
> of devs will make a decision and let us know? Surely they will want |
65 |
> a person that is mature and calm, yet very saavy with technology and |
66 |
> Gentoo. |
67 |
> |
68 |
> We can put together a very good guidance document, borrowing from |
69 |
> other projects and non profits, and add some interesting language, |
70 |
> but if the majority, or at least a handful of tribal leader do not |
71 |
> agree, we are dead, or starting our own fork..... |
72 |
> |
73 |
> It's more likely the user community will rally behind a group of |
74 |
> devs, that decide to fork, or the bickering will just continue until |
75 |
> everyone leaves? I have not read any of their posts (the devs) nor |
76 |
> any of the infighting. If they want help, they have to reach out. If |
77 |
> they are determined to intellectually bludgeon one another, all we |
78 |
> can do is prepare our ideas, here in this forum into a document, and |
79 |
> humbly submit it to of those tribal leaders that might be receptive? |
80 |
> |
81 |
> Maybe someone that reads this solicit from the devs a list of |
82 |
> grievances and we can begin drafting documents that the devs can |
83 |
> comment on and we continue the process until 'the beast is soothed' ? |
84 |
> |
85 |
> Does anyone think they can get cooler heads among the devs to |
86 |
> participate in a process like this, or something similar? I do not |
87 |
> know any of the devs enough to know who to approach..... |
88 |
> |
89 |
> |
90 |
> ??? |
91 |
> |
92 |
> James |
93 |
|
94 |
|
95 |
|
96 |
-- |
97 |
Alan McKinnon |
98 |
alan dot mckinnon at gmail dot com |
99 |
-- |
100 |
gentoo-user@l.g.o mailing list |