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

Russ Housley <housley@vigilsec.com> Mon, 21 September 2020 20:23 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 039793A08C7 for <tools-implementation@ietfa.amsl.com>; Mon, 21 Sep 2020 13:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 TGQZA89V-nAV for <tools-implementation@ietfa.amsl.com>; Mon, 21 Sep 2020 13:23:41 -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 3B8EE3A08C1 for <tools-implementation@ietf.org>; Mon, 21 Sep 2020 13:23:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id CB4FD300BAB for <tools-implementation@ietf.org>; Mon, 21 Sep 2020 16:23:38 -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 PCZjLHXqBCEB for <tools-implementation@ietf.org>; Mon, 21 Sep 2020 16:23:36 -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 26CBB300B3C; Mon, 21 Sep 2020 16:23:36 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <A3B550BF-6F78-4EE6-9A1B-58CC30EC0F81@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_31CB3E26-7BF4-4380-8339-E971CB4B65C1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Date: Mon, 21 Sep 2020 16:23:36 -0400
In-Reply-To: <8EC6DB09-5959-42CE-A218-98BCA2E103D5@vigilsec.com>
Cc: "tools-implementation@ietf.org" <tools-implementation@ietf.org>, Jay Daley <jay@ietf.org>
To: Robert Sparks <rjsparks@nostrum.com>
References: <e7a6fdf3-09dd-1328-60cc-6dd32dda7601@nostrum.com> <8EC6DB09-5959-42CE-A218-98BCA2E103D5@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-implementation/cYHTuxAaczDegKgZAYgsqULvCIU>
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:23:43 -0000

The zulip client email did come, but it took a long time.  The next screen has Glen's email address.  Shouldn't it have action@ietf.org <mailto:action@ietf.org>?

Russ


> On Sep 21, 2020, at 4:10 PM, Russ Housley <housley@vigilsec.com> 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.
> 
>> 
>> 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.  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.
> 
>> 
>> 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?
> 
>> 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.
>