Re: Re: IETF Meeting Venue Selection Criteria

[John Loughney <[e-mail]>]

Dave, Jordi,

I think this is a non-issue.  If participants are motivated, they will show-up. If their employer values their work, they will cover the meeting costs.  Other SDOs have more extensive travel destinations than the IETF, and participants in those organizations cope.  The IETF is an global body we just have to deal with that.

I dislike the 'primary contributors' concept very, very much.  What it is saying is that there are participants, but only a few of them really matter, and that it is possible to measure this.  In working groups I have chaired, we've had a pretty good dispersal of active contributors, but the active contributors have come and gone & sometimes come back again.  

If some active contributors can't make an IETF meeting because of location, and forward progress is needed, have an interim meeting at a more agreeable location.
John
> 
> From: JORDI PALET MARTINEZ <[e-mail]>
> Date: 2005/10/22 Sat AM 04:43:48 EEST
> To: "[e-mail]" <[e-mail]>
> Subject: Re: IETF Meeting Venue Selection Criteria
> 
> Hi Dave,
> 
> While I see your point, and certainly agree in some degree, I also think
> that any of the measures to look into who are "primary contributors" will
> turn to be unfair and subjective.
> 
> In a so big community this kind of measurement will never work well, unless
> everyone has the right to speak up for the venue selection, which will turn
> to be absolutely impractical.
> 
> Just one example from your own one, not to be taken as any personal issue.
> Why you have been queried for a schedule conflict (by the way "secretly")
> while others have not had the opportunity for that (including myself) ?.
> Clearly is not fair and is not consensus based, good or not, it may turn in
> being the only realistic way and always could mean people being limited to
> attend for this. How you know if there is much more people not being able to
> attend because those who had been surveyed are able to attend and how you
> measure how many of them are "more" primary contributors ?
> 
> Regards,
> Jordi
> 
> 
> 
> 
> > De: Dave Crocker <[e-mail]>
> > Organización: Brandenburg InternetWorking
> > Responder a: <[e-mail]>
> > Fecha: Thu, 20 Oct 2005 08:43:33 -0700
> > Para: Brian E Carpenter <[e-mail]>
> > CC: "[e-mail]" <[e-mail]>
> > Asunto: Re: IETF Meeting Venue Selection Criteria
> > 
> > Brian,
> > 
> >>>> What is the evidence that we will not gain that new
> >>>> participation without hurting current participation
> >>>> by primary contributors?
> >> It's very hard to get those data... There is no objective way to
> >> identify 'primary
> >> contributors' other than by assuming the regular attendees are
> >> also contributors.
> >> ...
> >> Which, BTW, means income that we badly need.
> >> ...
> >> We also badly need hosts for financial reasons.
> > 
> > Unfortunately, the ultimate and practical meaning, of these kinds of
> > conclusions about venue selection, is that we do not place productivity
> > as a high priority.  We have a collection of other priorities that take
> > precedence, for a collection of reasons. This means that the impact of
> > face-to-face meetings, on productivity and quality, is almost entirely a
> > matter of luck.
> > 
> > I should note that this is a similar problem with respect to Nomcom
> > member selection:  We use highly indirect criteria, because they are
> > easy to administer, but which are certain to have poor correlation with
> > member expertise about IETF management -- although IETF management is
> > what is being chosen -- and then we hope for the best.
> > 
> > It is interesting that essentially all public discussion of these sorts
> > of stategic issues and the criteria for pursuing them almost always
> > focuses on what is easy or already established, rather than what will
> > work best for achieving the desired result.  In particular, negative
> > implications appear to be entirely ignored, such as the one Eric Rosen
> > just pointed out, about encouraging participation by professional
> > standards goers.
> > 
> > For an organization that claims to care about the quality of its work
> > product, this all seems a rather strange approach to its management.
> > 
> > I suspect that organizations rarely achieve their primary goals by
> > making strategic and tactical decisions that ignore those goals.
> > 
> > d/
> > 
> > p.s.  "Primary contributors" could be operationally defined as previous
> > IETF attendees who are authors or chairs of current work.  One might
> > always want to factor in mailing list activity levels for some
> > individuals, but that's also an indirect measure.  However, all involve
> > objective data that are available.  An additional approach is a
> > variation on something that is already done:  Currently, some
> > participants are queried for schedule conflicts within the IETF week.
> > That could be extended to "venue conflicts" which would prevent them
> > from attending at all.    And the primary point behind my making these
> > suggests is to point out that it is easy to give up on pursuing criteria
> > that are not trivial to enforce, but that that is not always warranted...
> > 
> > _______________________________________________
> > Ietf mailing list
> > [e-mail]
> > https://www1.ietf.org/mailman/listinfo/ietf
> 
> 
> 
> 
> ************************************
> The IPv6 Portal: http://www.ipv6tf.org
> 
> Barcelona 2005 Global IPv6 Summit
> Information available at:
> http://www.ipv6-es.com
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/ietf
> 


_______________________________________________
Ietf mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ietf