Re: [gentoo-dev] *IMPORTANT* top-level management structure!

[Svyatogor]

Hello!
I am fairly new to this project and of course don't know all the difficulties, 
which you might have faced lately, but still I'd like to make as some 
questions on this plan.

First of all, the whole thing sounds quite nice. Especially cause it seems to 
bring some order and also some understanding who's responsible for what, and 
whom you need to contact in case you have this or other trouble.

Secondly, in a number of places you point out such thing as 'accountability'. 
Of course it is extremely important, but this is an Open Source project 
(AFAIK) and I don't actually see how you're planning to enforce responsibity 
for meeting project goals and deadlines.

Then, you say:

"Both the scope and any necessary decision-making authority must be
agreed upon by both the chief architect and project members."

How do you actually see this being done? While all project members and 'chief 
architect' and top level guys will most likely have the same intuitive 
understanding of what needs to be done, it'' be hard to agree upon a certain 
formal plan/definition. I am not trying to imply, that I don't like the idea. 
What I'm trying probably you need to elaborate on some procedures of reaching 
this agreement.

Ok, something else. You mention mailing list and IRC channel. However, you 
don't specify if they are gonna be opened for everyone to read listen, or 
not. I believe, it is extremely important for everyone - both devs and users 
to see what is going on in the management of the project. In the end of the 
day most people are volunteers and don't want to find thmesleves one day in 
situation when top managers, just bring them ready decision, which they've 
never had a chance to comment on.


-- 
Sergey Kuleshov <svyatogor@g.o>
Let the Force be with us!


--
gentoo-dev@g.o mailing list