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

Melinda Shore <melinda.shore@nomountain.net> Thu, 14 July 2016 00:03 UTC

Return-Path: <melinda.shore@nomountain.net>
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 9343312DA1C for <mtgvenue@ietfa.amsl.com>; Wed, 13 Jul 2016 17:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20150623.gappssmtp.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 vbYiJWFY4ols for <mtgvenue@ietfa.amsl.com>; Wed, 13 Jul 2016 17:03:49 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FF2712DA18 for <mtgvenue@ietf.org>; Wed, 13 Jul 2016 17:03:49 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id t190so23350176pfb.3 for <mtgvenue@ietf.org>; Wed, 13 Jul 2016 17:03:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=oDxQNO+61LpLUAeQjkdKx2qcj6nIIT4pxLoKPburpls=; b=dcMWCRd2FNx63tPAdjpUkaVifUc/OQZx0J5TRyG0LPuXg71nyVuUVVQRNNwqlpKbwQ lHKCustMiiKbhqJq/cQdu0O3Ic8Rnz5jVmlFWTxAB9t3nCrqbMlhqIzfZGSNoMJi/v1l aHCS6skW9/r8g0h4A0j7k6/L/Ve85N5yYGmPxBy679e3Y8syoJAGEVAtAeCosePwhYtG eAHzofN7ykTGSW8iTqXxaqVfHiGYNxfReYUsM4wWwbozneGvJUJVbsvpLIGlAn+ARR9h EX8w3lZQSY6/kvLtGzXJSs88uh3w2ii/nBid4kO51WtEgL0yq+VUYeYzmolc6SSzVNks fGDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=oDxQNO+61LpLUAeQjkdKx2qcj6nIIT4pxLoKPburpls=; b=Dyt1px2kzEXZZ5kNqQskptGyuy7AbBPGzzu1pu1G2uVBZg5V2TBx3+gGVQ+PHDseF6 tgZHcdhqNdCRLOjwPiybC4MTnnD9emtmflWldRnfdJvDjneR5RsZxRF1X716t5TwZdMN hiMJNKl5KcSMwBXNdlkEqXlTjCJOLvEehQaboPJuIAfF79pA9A4Uzb23S4yxVPt/gI8J t2AQMjnckG3DbLgOYc0j7Kp2Awv2DEB2oEfrI5SKt1F9AwSI4lUjoy2oDlrOdFBwHdMO p0Ltr63MhcaWUussdNXo5y9pPFI5mwNdc11Ydrq4yCOBgqyUt3/KM8V26vOBhCxdMOP3 MTOw==
X-Gm-Message-State: ALyK8tJxdPxGBo7SbYSncK0TGTWAfRn7vZqoF0qkkAFhfuVmUVjQRp/D35MQ8c+oRMIogQ==
X-Received: by 10.98.79.140 with SMTP id f12mr76765pfj.161.1468454628762; Wed, 13 Jul 2016 17:03:48 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (209-193-10-229-radius.dynamic.acsalaska.net. [209.193.10.229]) by smtp.gmail.com with ESMTPSA id 9sm4268971pfo.74.2016.07.13.17.03.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Jul 2016 17:03:48 -0700 (PDT)
To: "Fred Baker (fred)" <fred@cisco.com>
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>
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <01bfc432-e013-af39-546d-42aaff9c5387@nomountain.net>
Date: Wed, 13 Jul 2016 16:03:43 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <3D51128A-DB3B-4FDB-9CB6-A5F8B0EBD241@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/e9SqlJuq9eFtD7LRJoNUsgWWL9E>
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
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 00:03:51 -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.

Melinda