Re: [Tools-implementation] Rough draft of message to the community re Zulip and Matrix

Russ Housley <housley@vigilsec.com> Mon, 21 September 2020 20:29 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tools-implementation@ietfa.amsl.com
Delivered-To: tools-implementation@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903333A0901 for <tools-implementation@ietfa.amsl.com>; Mon, 21 Sep 2020 13:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 PYX-9RlFqLD8 for <tools-implementation@ietfa.amsl.com>; Mon, 21 Sep 2020 13:29:30 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D99773A08F8 for <tools-implementation@ietf.org>; Mon, 21 Sep 2020 13:29:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7AF4D300B3C for <tools-implementation@ietf.org>; Mon, 21 Sep 2020 16:29:27 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8BPe45YWwPsC for <tools-implementation@ietf.org>; Mon, 21 Sep 2020 16:29:25 -0400 (EDT)
Received: from [192.168.1.161] (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id F19C6300BA2; Mon, 21 Sep 2020 16:29:24 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <e22a1edf-e5ed-4ab2-8fff-44466f94bc1f@nostrum.com>
Date: Mon, 21 Sep 2020 16:29:25 -0400
Cc: "tools-implementation@ietf.org" <tools-implementation@ietf.org>, Jay Daley <jay@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5FF3B7B-A5ED-44FE-A648-051D9E1EF830@vigilsec.com>
References: <e7a6fdf3-09dd-1328-60cc-6dd32dda7601@nostrum.com> <8EC6DB09-5959-42CE-A218-98BCA2E103D5@vigilsec.com> <e22a1edf-e5ed-4ab2-8fff-44466f94bc1f@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-implementation/TZ6FpFDplLtxPQ2EEMgMOQO_zvk>
Subject: Re: [Tools-implementation] Rough draft of message to the community re Zulip and Matrix
X-BeenThere: tools-implementation@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Implementation <tools-implementation.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-implementation>, <mailto:tools-implementation-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-implementation/>
List-Post: <mailto:tools-implementation@ietf.org>
List-Help: <mailto:tools-implementation-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-implementation>, <mailto:tools-implementation-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2020 20:29:32 -0000


> On Sep 21, 2020, at 4:18 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> a couple of quick responses inline
> 
> On 9/21/20 3:10 PM, Russ Housley wrote:
>> Robert:
>> 
>> Comments below.
>> 
>> Russ
>> 
>> 
>>> On Sep 21, 2020, at 3:20 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>>> 
>>> All -
>>> 
>>> First, note that Glen is offline this week, and I do not expect him to see any of this conversation until he returns. But please don't wait for him to refine this. I would like to have it in a form that we can send by early next week.
>>> 
>>> Please point out (and offer text for) missing things that need to be addressed in this initial message.
>>> 
>>> ====
>>> 
>>> We are deploying trials of the matrix and zulip chat services to gain
>>> operational experience and get community feedback about how well these services
>>> meet the need for IETF related chat.
>> Is thee a sentence or two you can add about the things that we hope will be better than the current solution?
>> 
>> We expect the chat to support face-to-face IETF meetings, virtual meetings, interim meetings, and virtual hallway discussions.  We should say that all of these are dimensions to consider.
>> 
>>> The installs currently have almost no local configuration or customization.
>>> Over the next few weeks, we will be exploring reconfiguring them to use
>>> datatracker credentials for sign-in, and explore bridging between these systems,
>>> Slack, and Jabber.
>>> 
>>> The secretariat is operating each instance. We've chosen this path for these
>>> trials over third party hosting to learn what would be needed if the community
>>> felt self-hosting was important in the longer term.
>>> 
>>> The services can be found at matrix-trial1.ietf.org and zulip-trial1.ietf.org.
>>> 
>>> Any matrix client can be used with the trial matrix server. We are also hosting
>>> an instance of the element web client at matrix-trial1.ietf.org.
>> ... there is also a web client available at matrix-trial1.ietf.org.
>> 
>> It currently refuses to create an account with "common" names that are easy to guess.  This does not seem ideal for the IETF community.
>> 
>> This should tell people what convention we want to use for these accounts.
> 
> Expand please?
> 
> I don't think this initial message should be speaking at the level of "what your account name can look like". I also don't think we want to try to start changing the configuration to route around this kind of issue (unless we're forced to to make progress). Letting people see these kinds of edges are part of why we're running this as a trial set of services.

Do we want them to use their email address or some handle?  I was surprised that "housley" was rejected.  I think we want to tell people enough that they do not get surprised.

> 
>> 
>>> Similarly any zulip client can be used with the trial zulip server, which has a
>>> built in web interface.
>> It currently uses your email address, which is not bad for the IETF.  However, I never got the email when I tried to create an account.
> 
> Something we'll have to wait for Glen to get back online for to diagnose.

It came, but it took a long time.  We may want to tell people to expect that ...

> 
>>  Probably needs plumbing into the IETF mail system.
>> 
>> This should tell people that their email address will be used, and ask them ti use the email address known to the datatracker.
> 
> Well, as we get a week or two in, we may integrate accounts with the datatracker anyhow, so it may be moot.
> 
> But I don't think we should wait on getting that integration working beforew we start getting feedback. I've already called out that we will be making changes like that.

It will be easy if the user names are the same.  It will be a bigger pain if they have to make a new account.

> 
>> 
>>> Around December, we will assess our experiences and the feedback received to
>>> inform what chat services we provide in the future and how we will operate
>> Where do we want them to provide feedback?
> I think tools-discuss
>> 
>>> them. In January, these trial instances will be taken down. We do not intend to
>>> preserve or migrate any account configuration or chat history from the trial
>>> instances as we move forward.
>>> 
>>> This does add to the potentially confusing large number of places conversation
>>> might take place. We hope to address that with some level of bridging, at least
>>> with Jabber, but have been cautioned by the respective development communities
>>> that bridging between Zulip and Matrix is unsatisfying since the conversation
>>> models in the two applications are so different.
>>> 
>>> The chat services are intended to be explorational and informal. However,
>>> please treat them as contexts where participation rules apply (See
>> ... IETF participation ...
>> 
>> Some would argue that NOTE WELL applies to contributes, not participation.  You may want to word smith to avoid that tussle.
>> 
>>> https://www.ietf.org/about/note-well/).
>>> 
>>> We are not, at this time, planning to host jabber accounts. We may revisit that
>>> as an option as we continue to gather more feedback.
> 
> -- 
> Tools-implementation mailing list
> Tools-implementation@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-implementation