Re: Bad/Good ideas and damage control by experienced participants

Nick Hilliard <nick@foobar.org> Wed, 15 June 2022 12:37 UTC

Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17253C15D881 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2022 05:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.785
X-Spam-Level:
X-Spam-Status: No, score=-3.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YyRegW9yMBk6 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2022 05:37:37 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AAB8C157B35 for <ietf@ietf.org>; Wed, 15 Jun 2022 05:37:35 -0700 (PDT)
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) by mail.netability.ie (Postfix) with ESMTPSA id C15149CE80; Wed, 15 Jun 2022 13:37:32 +0100 (IST)
Subject: Re: Bad/Good ideas and damage control by experienced participants
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ietf@ietf.org
References: <20220614144751.97882437791D@ary.local> <cf6d63e8-aebc-9c2a-1137-96c3d1c86570@gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <962ec243-78c9-fb54-1666-90b43b3b240c@foobar.org>
Date: Wed, 15 Jun 2022 15:37:31 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.56
MIME-Version: 1.0
In-Reply-To: <cf6d63e8-aebc-9c2a-1137-96c3d1c86570@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PSSp50k_6s7Rcy3fC2NdOYuHun4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2022 12:37:42 -0000

Brian E Carpenter wrote on 14/06/2022 23:37:
> On 15-Jun-22 02:47, John Levine wrote:
>> It appears that Miles Fidelman  <mfidelman@meetinghouse.net> said:
>>> On the other hand, is it really a negative when someone is snarky with a
>>> snot-nosed kid who doesn't appreciate being told that their "great new
>>> idea" is a retread of something folks learned not to do decades ago?
>>
>> Depends.  If your goal is to make sure nobody new ever comes to the 
>> IETF, sure, do that.
>>
>> On the other hand, if someone new goes to the effort to write up an 
>> I-D and ask us
>> to look at it, there are a lot better ways to see if you can redirect 
>> their interest
>> to something that might be useful.  Sometimes they may go off in a 
>> sulk, but sometimes
>> a little politeness and specific references to prior work they should 
>> read about can
>> go a long way.
> 
> I think it is also a very effective sieve. Newcomers who respond positively
> to this are much more likely to become genuine contributors than people
> who won't listen and learn. The ones who don't listen are unlikely to
> succeed anyway.

Brian, John,

thank you for speaking up for the values of courtesy and politeness.

The freedom to be "snarky with a snot-nosed kid" also includes the 
freedom not to be snarky, and given that the latter almost always 
produces a better outcome, this is what we need to collectively spire to 
on IETF mailing lists.

Nick