Re: Old directions in social media.

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 05 January 2021 17:53 UTC

Return-Path: <jmh@joelhalpern.com>
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 C25C73A1093 for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 09:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level:
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 L55uV_aUw8jC for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 09:53:23 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 A4E023A1092 for <ietf@ietf.org>; Tue, 5 Jan 2021 09:53:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4D9Kq73cC5z1pGZG; Tue, 5 Jan 2021 09:53:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1609869203; bh=kyDScf8IG4b127ooE1flJ5C4EX+emoXXZ3Y1tlfJrvo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=CBqgpa9qJZaGDZBfPxlNoafz+6cHnyvbyVkrvub/gLWp+27Q9mZDM7z9iVp/O5Cxj l5s7T8J3lMfaT1cuX7tJOKL0CRhs36cZgwDkeHv4Rei1wFx5xyRjbOfnL+BmQQLluN hEbw/nbz2K/0H2kbVncMMZ1Pij5qlC+bccSOQ4NY=
X-Quarantine-ID: <5zrqDFGjhHzj>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4D9Kq66H2Vz1nslm; Tue, 5 Jan 2021 09:53:22 -0800 (PST)
Subject: Re: Old directions in social media.
To: Kyle Rose <krose@krose.org>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com> <519a0e4d-7102-fac8-1517-04c590a80080@network-heretics.com> <CAJU8_nUU0Km_YtgpWbLF-JVQVUXFYvxBNBYbzaLOXBqQyvvUaA@mail.gmail.com> <5692f00c-1709-624c-cd06-b14df28f73fb@network-heretics.com> <CAJU8_nUostFKjKU43wk-RG5+8SYgMc8Ag-MWs=UXi7x8YXTaKA@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <ddb7bdb9-0c58-ad99-9ecb-c7a894684839@joelhalpern.com>
Date: Tue, 05 Jan 2021 12:53:21 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAJU8_nUostFKjKU43wk-RG5+8SYgMc8Ag-MWs=UXi7x8YXTaKA@mail.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/60X-H3zEOtyTkw4GGPzoL6QmvNs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 05 Jan 2021 17:53:25 -0000

I am happy to have discussion such that they are in github issues and 
are meaningfully and understandably present on the email lists.

There are two problems.
One is that the current git side tooling does not do a good job of 
supporting this.  (Some peoples reactions describe it as much worse than 
"not a good job".)
The other is that a number of people have objected to the requirement 
that it be possible to effectively participate in all WG discussions via 
email.

Yours,
Joel

On 1/5/2021 12:32 PM, Kyle Rose wrote:
> On Tue, Jan 5, 2021 at 12:20 PM Keith Moore <moore@network-heretics.com 
> <mailto:moore@network-heretics.com>> wrote:
> 
>     If the new tooling were anywhere nearly objectively better overall,
>     you might have a point. 
> 
> Generally speaking, there's no such thing as "objectively better", so 
> that's a rather high bar to reach. But clearly there are participants 
> who have found GitHub to be an amazing productivity enhancement.
> 
>     Why in the world should IETF penalize the vast majority of its
>     participants in order to favor open source software developers?
>     Because that's exactly what this is doing.   I like open source
>     software too and definitely want us to be inclusive, but not at the
>     expense of significantly penalizing other participants.
> 
> How is this penalizing participants? You can still engage on the mailing 
> list in the traditional way. No one is required to use GitHub to 
> participate in any WG, and chairs should push back in the event an 
> author implies that a PR is required for a contribution.
> 
> Does GitHub make it *easier* for those who know the tools to contribute? 
> Of course: that's exactly the point. Learn the tools and you too can 
> benefit.
> 
>     And I can see why the model of making it easy to submit and manage
>     text changes, late in a document's development, can make sense for
>     IETF in general.   But git/github is still a really poor interface
>     for this, and PHB is exactly right that this actually impairs and
>     splits the discussion.
> 
> It does sometimes split discussion, which is where the WG chairs need to 
> step in and move discussion from an issue to the mailing list when that 
> happens. If that isn't happening, talk to the chairs or the AD.
> 
>     We did the experiment.  Now it's time to stop the experiment,
>     collect some results and learn from it.
> 
>  From where I sit, it's been a tremendous success. Why would we 
> voluntarily hamstring ourselves by moving back to a less efficient 
> universal model for contribution?
> 
> Kyle