Re: [Tools-discuss] Trial chat services: matrix and zulip

Ted Lemon <mellon@fugue.com> Thu, 01 October 2020 15:18 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE3263A117D for <tools-discuss@ietfa.amsl.com>; Thu, 1 Oct 2020 08:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, 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 (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 g-wAeVAGftrD for <tools-discuss@ietfa.amsl.com>; Thu, 1 Oct 2020 08:18:37 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 922DD3A1157 for <tools-discuss@ietf.org>; Thu, 1 Oct 2020 08:18:30 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id g72so5686131qke.8 for <tools-discuss@ietf.org>; Thu, 01 Oct 2020 08:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:in-reply-to:to; bh=5S5SNdsgOM/73uwONQbs1+bX6X27PiNpxpykuAjxUak=; b=EIA/7Tv7x5motnE3ktOFgjvihtB5dVCwfGpz8NK77gymtxdg0H4FxISZBqoy/HpR3c iHabbGzJerxwLOfDPG9JFeBuANQF4g9/h+9FuC/J/5jN2axVjB304VN8lpoU2vILmR3G Qn3db3BmirV4uhiEpH00f92LIQEE0bfkuAg/GMPvqF0o4M8+TiGbajYunoNzjfS0AqD+ PUdsQhqOU1IQmxIEd6WFDbEmLpXvmk/y9FtSH8H8K5AakmaRzj0V7XWVpDCj0cIWSIgR JjX/nmJn9AdrGRQOVhGON822EtVP9hDLy8aeAMkFZIXEz3OtOmI24chvFLVsHoQ3GjwR lYhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:in-reply-to:to; bh=5S5SNdsgOM/73uwONQbs1+bX6X27PiNpxpykuAjxUak=; b=UNXMKkHCjL62IPwuhfbFREbKoypAqcJdHkCWu424Ww8KBG07G8mfBxdkMMSdVe4RMl 5Jb88Z/DtyYLgMWkkB7g7vu/gGKKtq2w86lgFP6dC7GpaIFPJ0zjGvWSHjJU8Ey2xdi2 Ode15PosGmyvJk6/+E6bqWBYl2YPVxNX5OT1+Dr2TPfd68gy2XHMGfDpqwxNX5Obr8cT Ug1MuJk7KNsyu0/rso+IkPIQdr1Lccz4Jm8HjNTXiMOQAkAq7ChrRYYMjR6us+im/Meh ILBHJr5tAt1+ovYjizRFRhzQjSRtIayHJvSvkkGb1Jg8weOk2fG4RjFhOO1tgrUGiaeB ZVXA==
X-Gm-Message-State: AOAM5338/s9U1ih5EvTHNtZ4H2qDi5sVgrjHq7vqssfhHPl24j44H6Wr zXXQfQaOLddazQvTTleJCjJhqs2V/6hGFVJr
X-Google-Smtp-Source: ABdhPJyepStg2pl6xNvf4aemRW6gleHPJ/s9fMJ6imy8pQPqFj+uZ3ivPrDowMYs2X0c/IXryp/zSA==
X-Received: by 2002:a05:620a:15a6:: with SMTP id f6mr7952960qkk.418.1601565504134; Thu, 01 Oct 2020 08:18:24 -0700 (PDT)
Received: from localhost.localdomain (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id y7sm7232812qtn.11.2020.10.01.08.18.23 for <tools-discuss@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Oct 2020 08:18:23 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 1 Oct 2020 11:18:22 -0400
Message-Id: <6BFA5C6F-E743-44CB-8F99-6FCDC6F04DC5@fugue.com>
References: <3817345c-e25f-ec82-47af-5216a6234560@nostrum.com>
In-Reply-To: <3817345c-e25f-ec82-47af-5216a6234560@nostrum.com>
To: "tools-discuss@ietf.org" <tools-discuss@ietf.org>
X-Mailer: iPhone Mail (18A373)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/cUd9P35cj-nGsaioZ9HmMLmf1G4>
Subject: Re: [Tools-discuss] Trial chat services: matrix and zulip
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 15:18:46 -0000

It might be more effective to trial them sequentially rather than in parallel. 

> On Oct 1, 2020, at 10:33, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> 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.
> 
> We have clear evidence from the IETF 107 post-meeting survey
> (https://www.ietf.org/media/documents/ietf-107-survey-results.pdf) that many
> IETF participants find jabber a significant problem.  This is partly due to
> difficulties in finding a free jabber service and partly due to client issues.
> There are two paths to try to resolve these problems, one is to improve the
> IETF jabber service and the other is to switch to an alternative groupchat
> solution.  The community has already taken a step on the latter path with the
> introduction of an IETF Slack space, and we want to ensure that this path is
> properly explored by widening the range of options to well established
> free/open source tools.
> 
> 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. One consequence of these explorations is that there
> will  likely be times, outside of meetings, when accounts will be disrupted or
> even removed and will have to be recreated. Initially, we suggest you use an
> email address for the username on each service.
> 
> We considered running these trials using instances run by the Zulip or Matrix
> communities. We went with instances operated by the secretariat to learn what
> would be needed if the community felt self-hosting chat was important in the
> long-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. There is also
> a web client available at at matrix-trial1.ietf.org.
> 
> Similarly any zulip client can be used with the trial zulip server, which
> has a built in web interface.
> 
> We would like feedback on how well each client meets chat needs during
> meetings, both the full online IETF 109 meeting, iterims, adhocs, and hallway
> conversations.
> 
> 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
> 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 contribution rules apply (See
> 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.
> 
> Please send feedback on the services to tools-discuss@ietf.org
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce