Next steps: chat service trials

Robert Sparks <rjsparks@nostrum.com> Fri, 11 December 2020 19:01 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9D703A0DE8 for <ietf-announce@ietfa.amsl.com>; Fri, 11 Dec 2020 11:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 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, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 R3zvJlc3_J0V for <ietf-announce@ietfa.amsl.com>; Fri, 11 Dec 2020 11:01:08 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 110AF3A0DE4 for <ietf-announce@ietf.org>; Fri, 11 Dec 2020 11:01:08 -0800 (PST)
Received: from unformal-11.home ([47.186.0.128]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0BBJ14JT099507 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <ietf-announce@ietf.org>; Fri, 11 Dec 2020 13:01:05 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1607713265; bh=aNkakaeyLHI66vWumOHYqUheHeWNLppPp7HmYN0MoME=; h=To:Reply-To:From:Subject:Date; b=VPYd5MC+Q5fUDecXeV7pWjURTd5A4+mUr/EtUYs5csFNrHGiNrXyw5rsMGKX8vvv4 ZkFleCGuBdxFS3Qq/S5kOLr7o6JibMCR5Swyy85bWlMTm1gpv3VhAv/Tj6vAyQcRw+ 1jSbfKrvZptWKfBWgCJt6bQgAAPOhwJ7IpjJkIBc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.0.128] claimed to be unformal-11.home
To: ietf-announce@ietf.org
Reply-To: tools-discuss <tools-discuss@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Subject: Next steps: chat service trials
Message-ID: <f167ecf1-07f8-2f6c-31c8-0e9c2079e14d@nostrum.com>
Date: Fri, 11 Dec 2020 13:00:58 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/6bdY6SS6q2fjexqMaRAuaqmZEww>
X-Mailman-Approved-At: Fri, 11 Dec 2020 11:14:38 -0800
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Dec 2020 19:01:11 -0000

We have been running trial zulip, matrix, and xmpp services since October.
See
<https://mailarchive.ietf.org/arch/browse/ietf-announce/?q=%22trial%20chat%22>

As noted in those announcements, the issue that we are trying to address 
is the difficulty people have been reporting obtaining jabber services 
and clients. We are hopeful that these trials will help the community 
develop a better sense of whether to focus on improving the experiences 
with xmpp or to pursue other chat solutions. We are also open to the 
possibility that these other solutions may be worth operating in 
addition to improving the experiences from xmpp.

However, usage and feedback so far has not been sufficient to inform 
what services we should run in the future.

We had around 50 local jabber accounts created on xmpp-trial1.ietf.org, 
and around 40 accounts were created on each of the matrix and zulip 
services.
Few rooms have been created on the matrix service other than those 
bridging to xmpp.
Few streams were created on the zulip service other than those bridging 
to xmpp and those ingesting a few mailing lists.

We are not aware of anyone trying to use the zulip or matrix servers for 
ietf work outside the main meeting.

If you've used the services, please take a few minutes to provide 
feedback at tools-discuss@ietf.org.

Is providing local jabber accounts and a web interface to jabber sufficient?
Are there features that matrix or zulip provide that are truly helpful 
for progressing IETF work? If so, please describe how they are helping.

To collect more feedback, we are planning to extend the trials through 
IETF 110. Please take advantage of these services between now and then 
(at interim meetings for example) and let us know what you find to be 
effective.

If you are interested in using these services more directly for your 
group's day-to-day communication, and are willing to test one or both of 
these services on a primary basis for a while, please coordinate with 
the appropriate leadership and let the tools team know so we can help 
accommodate.  Please consider using these services for ad-hoc, 
design-team meetings, and even interims (again, coordinating with the 
appropriate leadership).

If you have had issues using Jabber in the past, please take some time 
now to work with these new services and describe whether they improve 
your experience.

We need more feedback about these services to develop a sense of what 
will best meet the community's needs going forward. Please engage in 
exploring and discussing them at tools-discuss@ietf.org.

While exploring, feel free to use the trial1-feedback room on Matrix and 
the trial1-feedback stream on Zulip.

Thanks again to the volunteers that have been helping configure these 
services and keep them going.

Robert Sparks, Tools Team Chair