1 |
On Wednesday 04 January 2006 21:39, Alec Warner wrote: |
2 |
> I think some people have attempted things that are interesting or |
3 |
> innovative, although they may not have gotten off of the ground quite |
4 |
> yet. I think for instance, that Stuart's webapp-config project is a |
5 |
> good idea, and while I also think his first attempt sucked, that perhaps |
6 |
> in the future it could be a great tool, especially for large virtual |
7 |
> host places. I think it sucks that he has gotten the flack from it here. |
8 |
> |
9 |
> The Gentoo Installer is an interesting project, not only for the |
10 |
> graphical frontend, but for the Distro-sponsored Network installer that |
11 |
> is being worked on. I think many distributions lack tools in this area |
12 |
> and we can be interesting and helpful here. |
13 |
> |
14 |
> The Portage project has some cool stuff coming up. I realize that the |
15 |
> 2.X codebase scares a lot of people away due to it's nature but recently |
16 |
> there has been a lot more active development in features and planning. |
17 |
> Plus there is code in the savior branch to do some "interesting" things :) |
18 |
|
19 |
Bingo. Bingo. Bingo. |
20 |
|
21 |
Where is the centralized vision that everyone is working together here that |
22 |
people not directly related to each project will buy in to and therefore do |
23 |
what they can to see it succeed? Where is the collaboration between groups |
24 |
to make it happen? I think this has already been hashed out enough, but your |
25 |
points can be drawn back to that. Portage team is running in one direction, |
26 |
webapps another, GLI a third direction (while kicking anyone who wishes to |
27 |
run with them in the nuts). In any structured environment I have worked in, |
28 |
you have a heirarchy where everyone, down to the grunts, know where they are |
29 |
heading as an organization, why they are heading that way, and what they can |
30 |
do to help. Even though groups work on differing things, they know how those |
31 |
things are directly affecting the end goal (mission statement, whatever) |
32 |
|
33 |
Right now, Gentoo has it's cliques that come up with their own things, and to |
34 |
get assistance from another clique you're gonna have to have some ties or |
35 |
work real hard to sell your idea to them. It's too flat of a model to work |
36 |
for any real innovation, else, as Kurt pointed out, we would have seen some |
37 |
cool stuff in the past couple of years. |
38 |
|
39 |
> If this Gentoo project fails/falters (like you seem to think it is |
40 |
> heading) you are free to do the same, form your own project with it's |
41 |
> own set of rules and leader if you so choose. |
42 |
|
43 |
Gentoo won't fail.. I don't believe that is what Kurt or Lance are saying. I |
44 |
think the point was that Gentoo is not moving at the typical pace of OSS |
45 |
development, and we believe that it is the organizational structure that is |
46 |
holding it back. |
47 |
|
48 |
> Partially I ( as currently still a user at this point ) would like to |
49 |
> see a bit more project management. I see that webapps posted a monthly |
50 |
> meeting reminder to -dev, but how many projects really have meetings |
51 |
> that often? Do they accomplish anything? Should we have someone that |
52 |
> tries to attend most meetings to make sure things are going smoothly, or |
53 |
> going at all? Do we need to have slacking projects that get killed off |
54 |
> by the council as well as "slacker" council members? |
55 |
|
56 |
Thanks for your comments.. As for management, anyone who reads "Five |
57 |
Dysfunctions of a Team" by Patrick Lencioni[1] will see all of the problems |
58 |
that Gentoo has, as well as the potential Gentoo has if it worked well. |
59 |
|
60 |
Cheers, |
61 |
|
62 |
-C |
63 |
|
64 |
[1] - |
65 |
http://www.amazon.com/gp/product/0787960756/104-9660666-9133512?v=glance&n=283155 |
66 |
-- |
67 |
gentoo-dev@g.o mailing list |