Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 25 October 2019 10:19 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7DA01200B8 for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 03:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 fRM8d7f_3U0f for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 03:19:08 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99AFE12083A for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 03:19:06 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id x9PAJ0qY000646; Fri, 25 Oct 2019 11:19:00 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C28D722040; Fri, 25 Oct 2019 11:18:59 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id BFCD62203D; Fri, 25 Oct 2019 11:18:59 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.46.229]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x9PAIw8d019358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 25 Oct 2019 11:18:59 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eliot Lear' <lear@cisco.com>
Cc: eligibility-discuss@ietf.org
References: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk> <CB806045-0E5E-4445-A377-7CD547B9DD90@cisco.com> <010a01d58ac1$c0ab2320$42016960$@olddog.co.uk> <CB7198FC-294A-4F5E-A57F-49333DD8C56E@cisco.com>
In-Reply-To: <CB7198FC-294A-4F5E-A57F-49333DD8C56E@cisco.com>
Date: Fri, 25 Oct 2019 11:18:58 +0100
Organization: Old Dog Consulting
Message-ID: <017a01d58b1d$9e5969b0$db0c3d10$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJAtSgmuKwIQAjILkVQZyHvzq+iagIHxZr9AuW8WQsCMZAAP6Zb0sYg
Content-Language: en-gb
X-Originating-IP: 84.93.46.229
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25000.006
X-TM-AS-Result: No--1.949-10.0-31-10
X-imss-scan-details: No--1.949-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25000.006
X-TMASE-Result: 10--1.949200-10.000000
X-TMASE-MatchedRID: EMyCvCfVN1HxIbpQ8BhdbPHkpkyUphL9ceFKyQwXWyYNZk45Kon56tiT 3u2NA72qxXrZx9nsOXO1ar8drXE5YwhNzULCAnM/kUvc5mAlMkGQYbmTvKGrFBAKjoHrIEcm0bp FijZjV29Jx3woazfgs3bNwLkoQ+6JksU6ZmyQL2dQ+S0N05fR+/ls1Rj4kmPIy5JfHvVu9Ivu8K 2F8g5C92deE4exmKu0UGVwlJCj/y6pRr/ThR9fnkI4eS9mV4/spRgiDG6+4P613P7r6QU9aE5iA VdrcggXm8illwYBAOCKgppSTR43KYyj7ma8b7zW3zen1b+Th8qlYZ4P/HFFyDJ0xHD2eXNKaXKz U8OFYujnT+tcLo0j5AIVcha099c2aR2vdrhgjHIsisyWO3dp271ZYuGtBm4aKcjvkak3PK6PFMF TgITPodANbaHVLvjl+dkY5u9Cc569k6Yzkdz+6U7tgjnds/VlfkuZtv/FS5qzU0R+5DbDbJ9+BG L7nFGIoYFUhxSsKhf+MsmyuwAzL77B68mjCRLBolVO7uyOCDV9LQinZ4QefBrZLyuS+0VxsOzOn crmCoP3FLeZXNZS4H0jHMQPhEvZrHxCPw3kN4gq+d4dpMRRvPdoBcKOvGbrA2VNgjpym71uimoq ftBYJDoYttnCJUXCCCP9qJSzgRCfLozBshRJ9teS+n3hnu9Y6Hq9RCTLxvsstHmcXeW1eBVSGW4 LjW40FYnPSoXfG8eN3TS5lTtZ8n7cGd19dSFd
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/rilGi4_7w8r8Yd1QlzEy0eI__jY>
Subject: Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2019 10:19:10 -0000

>> But let's take a leaf out of Ekr's book and try to understand
>> what problem you are solving.
>>
>> I think you are worried about "gaming the system". So, what
>> is the real risk?
>
> Fair question.  To me it’s not just a matter of gaming the system, 
> but a matter of acculturation or having a stake in the organization’s
> proper function.  Someone who has shown up relatively consistently
> demonstrates that interest.  People who have had work accepted at
> some level by the organization are similar examples.

Hmmm. I think I start to see your point, but when you talk about acculturation you are not talking about the effect/risk you want to avoid, but about the possible cause.

So, if I might rephrase, you are worried about:
- gaming the system (as previously noted)
- not understanding the IETF culture and attempting
  to make it that which it is not.

I hope I have that right.

Asides from the fact that that leads to perpetuation and ossification, I think we are agreed that "some level" of established participation is required.

Now, I would argue that physically attending three IETF meetings does not do much more than show financial support from a sponsor organisation. I might even suggest that there are a few people who have attended a number of IETF meetings who really have no clue how the IETF works: they "vote" on mailing lists; they post individual drafts and are upset that no one converted them to RFCs; they don't read the drafts. So let's not make the barriers for remote participants such that we embarrass ourselves.

On the other hand, I do agree that we need to see remote participants as, in some sense, full participants before considering that they can start a recall. So we are just arguing about the detail.

You (it seems to me) are suggesting a large number of potential criteria against which we can measure "involvement". I am looking for a more simple measure just like the 3-of-5 that we apply for physical presence where we don't additionally require co-authoring of I-Ds or some such. 

I think we could arrive at an easy bar such as 5-of-6 when less than 3 have been physical. And I'm happy to talk about that. But the question of "culture" comes down to this: what is the IETF culture and where is it documented? Do I understand the IETF culture? Do you? 

Best,
Adrian