1 |
On 1/31/08, Alec Warner <antarus@g.o> wrote: |
2 |
> One of my co-workers has a saying 'Trying things out is one of the |
3 |
> best ways to see if a thing works'. Just because he helped create the |
4 |
> structure we have today doesn't mean that structure was success; then |
5 |
> or now. Much of this involves experimentation. No one knows the best |
6 |
> way to manage a volunteer group of this size and we have to have some |
7 |
> sort of organization and we have to be smart enough and wise enough to |
8 |
> know when a solution is not working and work to fix it. Whether that |
9 |
> means incremental changes or more sweeping changes; I don't think |
10 |
> anyone knows ;) |
11 |
> |
12 |
> -Alec |
13 |
|
14 |
You pulled me back into the conversation with this good point :) There |
15 |
were certainly problems with Gentoo when I was leading the project, |
16 |
but we were always looking for ways to solve the problems, and we |
17 |
actually had the ability to make changes and try new things without |
18 |
dealing with a ton of politics or roadblocks. |
19 |
|
20 |
A lot of our challenges changing overall project structure or even |
21 |
portage itself. Examples of this were the creation of an unstable |
22 |
tree, the addition of "projects" within Gentoo, the creation of Herds, |
23 |
tweaking how herds operated, etc, etc. We tested stuff and when things |
24 |
were broken we tried to fix it. And we had the ability to try to fix |
25 |
any aspect of Gentoo. |
26 |
|
27 |
Also, your point about managing a volunteer group that is this large |
28 |
is well taken. My current approach to solve this problem is avoid the |
29 |
issue in the first place and work with smaller volunteer groups. I |
30 |
think this "solution" is something that the future heads of Gentoo |
31 |
should consider. With the software development tools that exist today, |
32 |
much of this centralization can be avoided in the first place. |
33 |
|
34 |
-Daniel |
35 |
-- |
36 |
gentoo-nfp@l.g.o mailing list |