Separate ADs roles from IESG

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Refering to the Change the Job subject of AD roles:

IMHO, the weakest point in the IETF process is having ADs in the IESG,
we need different expert directors roles in there. The AD can abuse
the system in his benefits because he can do ALL types of
participations at input and output, which I never seen that in any
organisation. Some one on the IETF list suggested two paralell IESG
which is nice to separate the area-output from IESG, but I think it is
better Separate ADs from IESG to have: 1) body of ADs and 2) the body
named IESG without current ADs (it may have past ADs experts of each
area). Similar
idea of having two groups of leading but different roles.

Also I always don't like when the IESG is discussing and I see that
the AD responsible for the I-D already made his decision, I prefer
that AD should wait until all put in their decision/discussions, and
then he may say what he thinks.

The ADs SHOULD have important-things in IETF that they are not allowed
to do. I don't like this off-hat and on-hat activities, or two/three
role-images per person in one volunteer organisation.

Best Regards
AB

On 10/17/13, Dave Crocker <dhc@xxxxxxxxxxxx> wrote:
> On 10/18/2013 3:54 AM, Tim Chown wrote:
>> I believe the "intense service" you mention is a significant deterrent for
>> many.
>>
>> I'm sure it's been suggested before, but is there mileage in rethinking
>> the
>> AD roles,
>
>
> It has been suggested many times.  The suggestion has been ignored.
>
> We have been having some very serious recruitment problems for a number
> of years now.  This year's crisis was entirely predictable.
>
> The only way the situation will change meaningfully is to make the job
> less onerous, and especially make it possible for the AD to continue
> doing real work for their company.
>
> ADs are senior folk.  That makes them a strategic resource for their
> company.  Or, at least, they'd better be.  Only very large companies can
> afford to lose a strategic resource for years.
>
> Looking for alternative funding does not make the job less onerous and
> does not permit the AD to continue doing real work for their company.
>
> Re-define the bloody job.  At a minimum, make the workload realistically
> no more than 50%, but I actually suggest trying for 25%, given that
> reality will increase the actual amount above that.
>
> This means taking the current list of AD tasks and deciding on the ones
> that absolutely cannot be done by others, and specifying other ways to
> do the remainder.
>
> d/
>
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]