Danny,
you expressed *perfectly* my thinkings.
Vincenzo
Danny Angus wrote:
On 10/19/06, Serge Knystautas <[EMAIL PROTECTED]> wrote:
Can we just discuss the underlying issue? Noel knows this software
inside and out and made the majority of the commits for a couple of
years there. Now he doesn't have time to check emails daily and
always participate timely in a very active group. How do we make that
work? How do let the community make changes as fast as possible and
get Noel's opinion constructively added to the mix?
IMHO the community of active developers has the right to make
decisions like this by lazy consensus, Noel, (and you and I) have the
right to be involved in a timely manner, or to step back, or even to
get involved after the fact. The goal should be to allow James to
progress, if the older generation wants to remain involved we must do
so in good time, and not be a dead weight holding the project back.
The two issues I can see are a) that the PMC must have sufficient
oversight, because decisions made on the dev list cannot be anything
other than decisions delegated to the dev list from the PMC. But in
this case we have enough PMC members voting to ensure that there is
adequate PMC involvement.
And b) decisions made without the involvement of all of us *might* be
less well thought out than if all of our experience is brough to the
discussion.
Just might.
In that case it should really be up to the *active* group to decide
whether they believe that an extension to allow those of us who's time
is much more highly contended to add our 2c. In this case I don't
think the time scale was too short, I might have been happier if my +1
would have been counted, but it would have been +1 and I doubt that
Noel's would have been anything else either.
James is in the funny position right now of having two generations of
community, the older one is much less active but has knowedge of
lessons we've learned in the past, the newer generation is very
active, but may not be aware of stuff we've done or the reasons for
decisions we've made in the past. It is all of our responsibility to
make this division work for the benefit of the project, and it isn't
always easy but I don't see anyone at fault in this.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
