Re: Old directions in social media.

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 05 January 2021 21:43 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 4BE553A086D for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 13:43:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.261
X-Spam-Level:
X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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=cs.tcd.ie
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 FceSKaAGS239 for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 13:43:38 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 851D63A0868 for <ietf@ietf.org>; Tue, 5 Jan 2021 13:43:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 22924BE2E; Tue, 5 Jan 2021 21:43:37 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJ-Ng8quUobq; Tue, 5 Jan 2021 21:43:35 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5CE91BE24; Tue, 5 Jan 2021 21:43:35 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1609883015; bh=f1l9h+vYFoVDMz9apQeKSJGwNuMPlDYZKQ7m6Vv4GZA=; h=To:Cc:References:From:Subject:Date:In-Reply-To:From; b=A7r5SftgASjfPGuVGWrDtwt8/J6GaoxFSA1fKYHYKwSiqLn//zzpx0zt3vWLQT0PU lmHEDk0gXtHaiVVGvwquadEFkUX3O6pDqbq56ed0RX5Pznj34HTBRVUOsAQtgHpi/Z tNV+8NCPp1zSfIDB4MH/RCPPTGofy6Fh8LtSpHLs=
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> <062d01d6e387$39c46270$ad4d2750$@acm.org> <CAJU8_nWD3MwLs5aVNMi_3LqZysrfjv0N7N3ujV-zhqxiFh3tsA@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Old directions in social media.
Message-ID: <fff234f2-266e-90cf-8c23-0cf19d21929e@cs.tcd.ie>
Date: Tue, 05 Jan 2021 21:43:34 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <CAJU8_nWD3MwLs5aVNMi_3LqZysrfjv0N7N3ujV-zhqxiFh3tsA@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="XRWQ7xt7Jrlwe4XkC2PFTYvuVZ8b4xn75"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Np6oB0Bn7GrDnVWkFr3rYWOVzXI>
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 21:43:40 -0000

Hi Kyle,

On 05/01/2021 17:46, Kyle Rose wrote:
> Again, no one in any WG is required to interact with GitHub to contribute.

I don't think the above is true in practice, at least in some
cases. In one case where I'm implementing a draft I've found
the github issue discussion effectively excludes me from
really being part of the discussion.

Github issue discussions do work fine for many people, and
could work fine for me some other time (e.g. if I and others
involved were in similar TZs and online at similar times),
but my experience is that even with the best will in the
world, the split-discussion or exclusionary effect PHB
complained of can and does happen.

I don't think this is only because the github->mail tooling
is worse than useless (for Rich: few mins ago, having been
offline for an hour or two, I got 40 mails for one repo to
which I'm subscribed;-), I think there are problems with
timezones too (hence this mail).

I don't have a good solution for that. Equally, I'm not
asking that we stop with git or github - I just think we
need to do more work to better take into account that the
github issue discussion workflow is not everyone's workflow.

Cheers,
S.