Re: [Mtgvenue] New Draft: draft-elkins-mtgvenue-participation-metrics

<nalini.elkins@insidethestack.com> Thu, 14 July 2016 07:08 UTC

Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564A412DAD7 for <mtgvenue@ietfa.amsl.com>; Thu, 14 Jul 2016 00:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m340Dx0M-2t5 for <mtgvenue@ietfa.amsl.com>; Thu, 14 Jul 2016 00:08:16 -0700 (PDT)
Received: from nm42-vm4.bullet.mail.gq1.yahoo.com (nm42-vm4.bullet.mail.gq1.yahoo.com [67.195.87.155]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19B0E12DAD6 for <mtgvenue@ietf.org>; Thu, 14 Jul 2016 00:08:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1468480095; bh=kJU+6k5w4annbh5O3iqUzqfS6E1Du5AKsr6XWER9EJU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=d5obKCqAtPz0PTxqUjCsu0cTXzsorvl1Nn5JOJVaT2yrnf92ccsruXK7mm9RzdbCti8pCT9k1ZEFWee8sFf4R6NIGiY8Wrsgb4GE1LWOzcaCZpGfErEjruwlB5dI7u6CW013IGMKLc/2DqvlnSmh3e6eJAVr45/GHr2pes9UYGIf8B+SQSfW/HwjfZosJEzTzk7qV9KMawd0s1Nxqia5j8hxvyf5u5EDCOxHG27gGiBVsA79038TSZssCGIij70lC/2pL44jOgb7o8H/tPdrieM1VTi7Aa4w0rvsIQMFXjjvcXxR/cNGCWcB373AVRRFmN+j9r3JnzszCixcx43mPg==
Received: from [127.0.0.1] by nm42.bullet.mail.gq1.yahoo.com with NNFMP; 14 Jul 2016 07:08:15 -0000
Received: from [98.137.12.63] by nm42.bullet.mail.gq1.yahoo.com with NNFMP; 14 Jul 2016 07:05:19 -0000
Received: from [98.137.12.202] by tm8.bullet.mail.gq1.yahoo.com with NNFMP; 14 Jul 2016 07:05:19 -0000
Received: from [127.0.0.1] by omp1010.mail.gq1.yahoo.com with NNFMP; 14 Jul 2016 07:05:19 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 96327.71076.bm@omp1010.mail.gq1.yahoo.com
X-YMail-OSG: z03TOjIVM1kACNN4hE9xpeozv6vRLzMY_U30zstt3.u_2cPhjj7LwJLPJuPZQcB KO9oa4zMJv4tiL9aRkyJnDBPWEa4H7lCkdjf9b5_Ih.57nRdolBtqL0_hUL1bxVeQ5ZL2vbdIZsa 6KDN7gJ5aYr9YH_bKt6gD6bVy_phXDSaZTqjXYHr8VgiQ_hLe8SkffqlUdwmhEu_S3K51PxblomI rFPB1fM7bXrKAgkXoKzuKfdHYzeGsyQbJhaK8Io3oAChMBUJdqJ8ZwKlikPxVv.b95HafBiJwn7J H7jmei2BCn.pVIsr5LoM78RPH8rZNVOYTTgpvtfMC7pD5rzZfSM_.UQtlS2KN7LQfqyoLSPs4769 61RLy232RFNgLdaBjWIHdp9UgVgJSZPhiQFkSFtTuFh0N38s8ay.HXodnIUS_4F7p4pWf0qik_yW OuzyXrkKwg5qcZ2Ysk4OHah4B0o5N0z5Ea4JxPGE2lJC3LOeibjwS5uB7ZxJvSLSQH8NhfBrhnVd QnZGpTpM8_KR6NdlhZmmnCQT_glJovlLnbONl1Z7GIeo_GBzI
Received: from jws10089.mail.ne1.yahoo.com by sendmailws122.mail.ne1.yahoo.com; Thu, 14 Jul 2016 07:05:17 +0000; 1468479917.713
Date: Thu, 14 Jul 2016 07:05:17 +0000
From: nalini.elkins@insidethestack.com
To: Melinda Shore <melinda.shore@nomountain.net>, "Fred Baker (fred)" <fred@cisco.com>
Message-ID: <1994413395.3539717.1468479917049.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <01bfc432-e013-af39-546d-42aaff9c5387@nomountain.net>
References: <226347980.2361764.1468309043895.JavaMail.yahoo.ref@mail.yahoo.com> <226347980.2361764.1468309043895.JavaMail.yahoo@mail.yahoo.com> <A9CC92A6-F98E-4763-9BF0-F56B29A53A37@cisco.com> <dd62041c-3fca-3562-9a04-7ec990c7df9d@nomountain.net> <3D51128A-DB3B-4FDB-9CB6-A5F8B0EBD241@cisco.com> <01bfc432-e013-af39-546d-42aaff9c5387@nomountain.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/nIOWXh2SPuJdmNPe-TY8RbrGtzc>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Subject: Re: [Mtgvenue] New Draft: draft-elkins-mtgvenue-participation-metrics
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2016 07:08:17 -0000



On 7/13/16 2:35 PM, Fred Baker (fred) wrote:
>
>> On Jul 13, 2016, at 1:16 PM, Melinda Shore
>> <melinda.shore@nomountain.net> wrote:
>>
>> On 7/13/16 12:07 PM, Fred Baker (fred) wrote:
>>> So on drafts, I would similarly go for "simple": if you post a
>>> draft, you have participated.
>>
>> I have a few concerns about the draft, and one of the primary ones
>> is that I'm hopeful that "participation" is being defined in
>> service of the broader goal of figuring out who ought to be at
>> meetings, but I'm not sure it is.
>
>> I *think* the discussion has to do with where meetings should occur,
>> based on the rubric that meetings should happen in places where we
>> have participants - "so who is a participant". "Where meetings should
>> occur" is central to the charter, whether IETF participation is
>> directly so or not.

>I think so, as well, but I have a personal concern about meetings
>being effective, and being places where we do things that can't
>be done on mailing lists or by use of other mechanisms, and I'm
>not sure that what's under discussion captures that.  As chair
>of this particular working group I have concerns about whether or
>not we should be defining what a "participant" is, both as a matter
>of scope and as a matter of not heading into ratholes.  That said I do
>think metrics can be extremely useful, so I'm interested to
>see where this discussion goes.

The reasons I wanted to start this discussion is:

1.  As Fred said (and as the other drafts in this WG say), where an IETF meeting is physically held depends on where the participants are.  So that really begs the question: "What do you mean by participant?"

As far as I know, historically, a participant has been someone who attended physically and / or was in a leadership position.  I believe there was also some consideration given to RFCs written.  (All, please correct me if I am wrong on this.)

To my mind, that is not fair to some regions of the world which are emerging economies and cannot participate physically in person as readily as others.  So, if such regions want to grow their IETF participation, they can most readily grow via electronic means - email, remote hubs, etc.

As many have said, much of the IETF work is done via email lists.  So, if we have good strong contributors participating via email, then why should that NOT be counted?  So, I want to get consensus that we should count such things and then consensus on how to count, weigh, etc.


2.  There is also much discussion of the type "We held a meeting in such and such a place & how do we know if we have additional contributors?"

My personal feeling is that there ARE additional contributors.  But, that is only my feeling and I am only one data point.  So, let's find out if there really are additional contributors.  Why have a fact-free discussion?


3.  There is quite a bit of outreach being done by various parts of the world - India, Africa, Asia-Pacific, Russia and of course Latin America.  And, that is only what I personally know about.  I am sure that there is much more that I do not know about.

I think it is good for these regions to know what are the specific metrics of IETF contribution so that they can gauge their own progress and also show others of the progress in their region.  


4. We need consensus.  We should have metrics that we all agree on are "good enough".  We will never have perfect metrics.


I do not believe we need to rathole.  I understand your concern.  Let's stay focused.

Thanks,
Nalini