Re: [Mtgvenue] Exploration of a "posting" metric - draft-elkins-mtgvenue-participation-metrics

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 21 July 2016 07:18 UTC

Return-Path: <brian.e.carpenter@gmail.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 C9A5212DA5A for <mtgvenue@ietfa.amsl.com>; Thu, 21 Jul 2016 00:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 up4kG-QtCRdI for <mtgvenue@ietfa.amsl.com>; Thu, 21 Jul 2016 00:18:56 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 F07ED12DA1C for <mtgvenue@ietf.org>; Thu, 21 Jul 2016 00:18:55 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id p129so1827763wmp.0 for <mtgvenue@ietf.org>; Thu, 21 Jul 2016 00:18:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=IFAUyb1aIDG0Zi7jDJr/LvnX3sgQUaWpMS+eQ7RIoIU=; b=VAHn9x/LwdCnkxJPUCvK5Vx8WUzlRdLx5jHrnKQTiYFik/cd70znikuplidoA5DbhC xv2PW/4lxE40FkK21fqvrcKRyquv1P04iY25XV0/NfCgGb2eQWzb3RbTdC1KvR+hGDOm HE0LHu4lKZifX6yFTX1BHzZtI8pNErr7IHTZcShzreuhc00h71icCkmScg+TwLd1UW5C DKVZRfmXlgltDSbladWwHmtjooyS1nrX/f+ZlH5TLo60aIP9zQfikI3YtJZ6Cvr+ceqV rl7nFwQxpS+fCfxPkB9eSYBoEiZtw7LlCZokYxCMC8lIEijzpEjDGgsam9zD+g+l2rbY t2UA==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=IFAUyb1aIDG0Zi7jDJr/LvnX3sgQUaWpMS+eQ7RIoIU=; b=gmCsAfYaLBQICg5hRPdPSnZg4yw/k1SPTsFZpMgTweG9Xo7Zn/wBc9vtdLg84fvXbd xMFvaoElf75+C7c3i1S8tf8iC7eDI+CCFUpFPKMcE0cRhICNwu8d25pgN9YIdlpvh6wQ 6W40ZcD9VtSOMd4NV/G75IYi9ISVU2kaiwRbJVywTB3T4echazIgyWIPb/b4oy/sSuiN N7mGdQmw/8svIr9tYpttDCJOWDwIy5OMT52D1QqiLau6cFoQ99SVAFZqk5xl2g2CCT7v FIMydMabqP6cpujtO/TYbv1sgaT48x1wb2Q9gszrJ/aY34H7E8+Lhxk8k8PZDcI2gHa+ unOw==
X-Gm-Message-State: ALyK8tLNx4dZC1pBpCcFsXIKVGEbD03JF6YuKMHrPvMsyPuC4PLZ5G3XZHkzNAUYuRsXIg==
X-Received: by 10.194.24.164 with SMTP id v4mr5282299wjf.116.1469085534526; Thu, 21 Jul 2016 00:18:54 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:152:28cc:dc4c:9703:6781? ([2001:67c:370:152:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d64sm1827530wmc.22.2016.07.21.00.18.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jul 2016 00:18:53 -0700 (PDT)
To: "Fred Baker (fred)" <fred@cisco.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
References: <F4EACEAA-0255-4985-AB4B-0247085C1D68@cisco.com> <6ca7e342-87b7-fa19-1ca4-ae8fa9908c12@dcrocker.net> <B6A66A5E-5DBA-43D5-8140-F4248A8E023F@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <10fdb18d-b620-a144-559d-601c23016ba0@gmail.com>
Date: Thu, 21 Jul 2016 19:18:59 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <B6A66A5E-5DBA-43D5-8140-F4248A8E023F@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/e5kKpmfCIjo6v59ksscRjD1hMz4>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>, Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: Re: [Mtgvenue] Exploration of a "posting" metric - 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, 21 Jul 2016 07:18:58 -0000

On 21/07/2016 06:08, Fred Baker (fred) wrote:
> 
>> On Jul 20, 2016, at 11:48 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>>
>> "Contribution" needs to be measured meaningfully, as well as objectively, even if the measurement is coarse and doesn't count everyone.
>>
>> This is why I've suggested reaching no deeper than the Acknowledgements and Contributors sections of I-D's and RFCs (as well as author lists, of course.)  If a name shows up there, the person made it through a basic filter for having been seen to actually contribute.
> 
> I'm thinking through the mechanisms by which one might extract the acknowledgements, contributors, and authors sections of an internet draft or RFC, and extract from it human names. If you have some good heuristics, I'd be interested. I don't think "hire an intern" is a long term solution.

It isn't. But "talk to Henrik" might point to a solution. He has a bunch of code
that extracts stuff from drafts and RFCs using a bunch of heuristics. I think
he could tell us pretty quickly what is realistic and what is science fiction.

   Brian

P.S. Re postings on mailing lists: I think that's binary. Either we count
all postings, or none. The fact that someone's posting is trivial is hard
to decide (even for humans, and definitely for algorithms). The only exception
might be to discard all messages that top-post the string "+1". (Personally
I'd also discard all messages that only make sense when viewed as HTML, but
that's me being old-fashioned.)