On Fri, Oct 18, 2013 at 8:07 PM, joel jaeggli <joelja@xxxxxxxxx> wrote: > On Oct 18, 2013, at 10:39 AM, Andy Bierman <andy@xxxxxxxxxxxxx> wrote: > >> Hi, >> >> I don't think the Assistant AD job would be easy to define >> or even the right approach. IMO doubling the number of ADs >> would probably work better, although at an increased cost >> wrt/ managing the review process. I do not agree that >> every AD needs to review every draft. The review >> and WG management tasks should be shared by 4 people >> instead of 2 people. >> >> The problem I see is that few people are both qualified >> and able to do full-time volunteer work for the IESG. >> There is a disconnect between the official job requirements >> and the real job requirements that is being ignored here. >> >> Perhaps if the AD job really was only 20 hours a week >> there would be a lot more people willing and able to >> accept a nomination. >> > > For better or worse I told the nomcom that I only have 2 hours a day (7 days a week) for this… They took me anyway. The load is unevenly distributed. The internet and routing and Apps ADs appear to have more drafts to process and more complex working group interactions, then does the ops side of ops and management. > > That said, this is not a not a full time job for me and I am not compensated for doing it. If my level of available commitment isn't adequate, I guess we'll find out between now and the 2 year mark. My contribution to the things that bring me to the IETF as on operator have dropped off because I don't have time for them. You're mail gave me two thoughts 1.) are our current Internet and the interconnects of thing too complex for our current structure? Are IETF doing more than they should in one area or another? 2.) normaly there are two reason why people stop doing things, or don't have time for it, the normal change of interest is one thing. The other one are probably what you're going at, no time left for doing that. Both of these really tell me we need to consider our structure, not just shifting jobs or workload around. I mean, it's not the workload alone that is causing us problems right now. And no, I don't have any ideas right now either because I do believe our current structure is a strength that make the quality on what we produce to be quite high. We should not give up that quality, or lower it... -- Roger Jorgensen | ROJO9-RIPE rogerj@xxxxxxxxx | - IPv6 is The Key! http://www.jorgensen.no | roger@xxxxxxxxxxxx