Hi Andre,

On Tue, 2008-08-12 at 08:57 +0200, André Schnabel wrote:
> I know enough examples for this. But as said - we should work to correct 
> the role of projects / project leads (would reduce adminstration 

        Sounds sensible as a parallel activity.

> Cor is drafting an activity plan for the council and this 
> is one of the topics. (Seems like you are heading for a workaround
> instead of fixing the problem ;) )

        Well; where is the workaround ?

        I find it hard to understand why disenfranchising code contributors is
a good idea - when there is a great way to find our who our core
contributors really are there. Sure - we can proliferate projects - to
create more project leads (and co-leads (do they vote)) - but even then
it is not fair.

        Clearly some projects (perhaps writer) have a large code-base, and many
contributors, and other projects - perhaps 'kde' (not picking on kendy
of course ;-) have relatively small code-bases. Is it reasonable to give
them both the same influence ?

        If so - why is it a better metric than something that is fair to all
code contributors ?

        Then of course, there is the contribution across the board problem:
that of fixing many things in many places - this is often true of people
doing distributions, tending the build, and so on: valuable work that is
easy to ignore.

        And finally - once again, putting Project Leads, often affiliated with
companies, who can never be replaced (because of their long term
contribution to that code-base) in a situation where they have to
(somehow) reconcile the conflicts of interest between themselves, their
corporate direction, and other contributor's strong views is -highly-
sub-optimal. By far the most fair and nuanced input would come from an
open and flexible meritocratic approach.

> Ok I'll take this as suggestion. Im not the one to decide about it. I'd 
> love to hear comments from developers on this (e.g. people who are 
> actually listed).

        It seems many developers do not subscribe to or read discuss - due to
volume & SNR issues. I'd love to hear objections from developers too.

> Or maybe you consider yourself more important than you actually are ;)

        It's entirely probable ;->

        Regards,

                Michael.

-- 
 [EMAIL PROTECTED]  <><, Pseudo Engineer, itinerant idiot


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to