Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt)

[Harald Tveit Alvestrand <harald at alvestrand.no>]

On rereading, my previous reply could have been better formulated......

--On 1. august 2005 12:42 -0400 Eric Rosen <erosen at cisco.com> wrote:

> > the  normal process  for AD  replacement  involved choosing  which of
> > the people who had  worked with the AD for  a long time could do  the
> > job this time,
>
> In American vernacular, this procedure is known as "cronyism".
>
> Generally, one doesn't expect to see this advocated in a public forum ;-)

The selection mechanism I advocated was the following (quoted from the 
expired draft):

> 5. Details
>
>    All members of the leadership are selected by the nomcom for
>    membership in an area.
>    The nomcom also selects which member is supervisor and vice
>    supervisor for an area.
>
>    [UNCERTAIN]The supervisor may also be selected by the members of the
>    council, or by other means.  Yearly selection by the council?
>    It's also been suggested that instead of nomcom selecting everyone,
>    the leadership team can make selections to the area councils, based
>    on recommendations from the area supervisor.  This would not increase
>    the load on the nomcom as much as envisaged here.  [/UNCERTAIN]
>
>    Special care should be taken that the composition of area teams and
>    the leadership team results in functional teams.

(The term "area supervisor" is a concept that is a successor to the current 
term "AD" - the draft tried to use new names to point out that things 
changed.)

One core difference between this idea and directorates is that directorates 
serve, explicitly, at the pleasure of an AD; ADs can create, disband or 
replace directorates without any public input or control. Your concern is 
one reason why the idea was different.

Note that nothing here prevents the nomcom from picking people outside the 
"council" to be supervisor; if all is well, common sense would say that 
they don't, but when things are not well, they should have the power (IMHO).

But the idea didn't generate any groundswell of "let's do it", either in 
the community or in the IESG, so I turned to fixing things that were more 
obviously broken, with more obvious fixes.....

                    Harald


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf