Re: [gentoo-dev] Proctors - improve the concept or discard it?

[Richard Freeman <rich@thefreemanclan.net>]

[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]

Galevsky wrote:
> But I do not understand why 7
> devs -even elected by the others- could make decisions on other
> projects and are described as the group in charge of the 'global
> issues and policies'.
> 

The logic is that most organizations are overseen by a board of 
directors.  This system is used in most corporations worldwide, most 
non-profits, and to some degree most governments.  The reason is simple 
- it generally works fairly well, although this is obviously limited by 
the makeup of the overall organization.

The concept is that the council provides oversight and high-level 
guidance.  If necessary they can step in and micromanage when necessary, 
but in theory they should be delegating their power whenever possible. 
The proctors are a body to which the council delegated day-to-day 
responsibility for enforcing the code of conduct.

In most companies if the head of an organization (who reports to the 
board of directors) makes a decision that a good chunk of the board 
disagrees with, the board does NOTHING in public.  At least not without 
careful thought.  Instead the board just sits down in private with the 
CEO/president/secretary/whatever and decides what to do about the 
disagreement.  This might ultimately lead to the appointment of a new 
CEO/president/secretary/whatever - usually without a whole lot of 
fanfare.  The reason for this is that the organization speaks with one 
voice at all times.  The board is in ultimate control, but they don't 
usually feel the need to step into the limelight.

What gentoo needs is a little more patience.  If somebody says/does 
something you disagree with, try talking to them in private about it. 
If necessary try talking to an appropriate moderator in private.  And 
don't expect a huge change within 8 hours....  And think about the good 
of the whole organization, even if you don't agree with every person who 
is in charge.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3875 bytes --]