Re: [Tools-implementation] 2nd iteration: Re: Draft of message about chat trials

Alexey Melnikov <aamelnikov@fastmail.fm> Thu, 10 December 2020 18:37 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 6F5F53A119E for <tools-implementation@ietfa.amsl.com>; Thu, 10 Dec 2020 10:37:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fastmail.fm header.b=hc8FHZCs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Q5GgDHso
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 RHc6A0wGAdft for <tools-implementation@ietfa.amsl.com>; Thu, 10 Dec 2020 10:37:53 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CB9D3A119C for <tools-implementation@ietf.org>; Thu, 10 Dec 2020 10:37:53 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BFED45C0186 for <tools-implementation@ietf.org>; Thu, 10 Dec 2020 13:37:51 -0500 (EST)
Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Thu, 10 Dec 2020 13:37:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm1; bh=rUpNq fJiw1zCPACpIGyXBl3IlXRvY3TEfuTTxC8rEHA=; b=hc8FHZCssvjM7Nznknkhy vNijZlrzgUf6+87GlWbH5V0VUYaPczlvEOEpZsN6d758MilOFUPxGyvOVOf0Ikf/ jdpWd1DGa3e+hyibKIghD2JRlUJ4KOPumW8/9N+Y2mubt9OFlYST11OJqK+2lt5p BevgCWYvXXAP9SvAjcfPHuIMMMzkf1yacgsvqBSSEEY2TEHR/M7Jhjr5xzHjOIu7 ZlPM7c4zgJ/FlULKrP/jULVSH+as6QnqWHsVaTFaVdhYaTTWw+fNTvSXHVRSxv8n jii501NBc1ahwKt44er29+p9dk1mEWo2mmIvSfQzTzb1m9gqyCj0et2jbV1cteSy w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=rUpNqfJiw1zCPACpIGyXBl3IlXRvY3TEfuTTxC8rE HA=; b=Q5GgDHsoLaD1xXLXjXvfqfX/71zQivmVMlA6w8HcseJeyCnsLnVJKuy9N tjHoWrO1fwOwX3oB0X9GCRV3P4oHw5Zq4uz5chIVc2UUKweE23rjpg3JJcFcbBHQ 2vDXU4OJZHGFMuoMBB2ofK9ZRqFtIeDQLFIZSx5YrTCjro7TofBlTs/aS0dKW56u DXFnqYqiRfGc5ltDMAT25pAGAGVt4c3hFcw4N0TwrhS5yAyrVsHyoG7XpdrNRB26 2GYZ+k45GDFJm+pIcjQxiTd4DVI2XJs7LlPRZQdHCnKUZTB1IjX83UKHns88C48p OMulZJmqcr0E4sdX8Fe8bCBKx4Jig==
X-ME-Sender: <xms:_2rSX1mqV5M0hr7CFHWYzkq9iBZ6El8gfn9LBAbg-UEXRgBQrLSY8Q> <xme:_2rSXw2aYf8DJkSWHV5nUGJ0REIVrhllq9hDC3lLKKH8F_P3WNmPo22LigqkEEyqj FZWMN7zV9n_ukQSag>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudektddgudduhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgse htqhertderreejnecuhfhrohhmpedftehlvgigvgihucfovghlnhhikhhovhdfuceorggr mhgvlhhnihhkohhvsehfrghsthhmrghilhdrfhhmqeenucggtffrrghtthgvrhhnpeelve ejfeevhfdvfeeftdegfeduveekkeejgfffgfeffeeiheelleefgfegfeeuvdenucffohhm rghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfhhm
X-ME-Proxy: <xmx:_2rSX7qdUq605hWVhuhRjfxILG0E0OoxxAiafaGXCsxv4f-QrGThHA> <xmx:_2rSX1mwPWuYwJYs0BoUGgfEVCjpsLrXuCOiKO7QymJ8eFwIzaeFZA> <xmx:_2rSXz3QAxKKwm8B4a-1Azq2zZDdGMrrt1517w9Lhoq4xj92lX0PHA> <xmx:_2rSX0CnR-Ow2c8avdvvDtXoaBARWW8cJsKPUoVs5EarIvcDt3a5Pw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D3F3A6F6005F; Thu, 10 Dec 2020 13:37:26 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-622-g4a97c0b-fm-20201115.001-g4a97c0b3
Mime-Version: 1.0
Message-Id: <b0f7f892-8ca5-48dc-bbb9-9a17a166b084@www.fastmail.com>
In-Reply-To: <7db35978-94c4-f67a-08d2-031746b0cbd0@amsl.com>
References: <79a73ae2-d565-33b3-6753-58587269861c@nostrum.com> <c06a6297-4a5a-f7dc-c9ce-387b1ce12794@amsl.com> <41D3FBF3-81F4-49ED-B776-DE3D8E52071B@ietf.org> <1c886ee6-e7be-21c1-167c-e1e25a5dadfd@nostrum.com> <7db35978-94c4-f67a-08d2-031746b0cbd0@amsl.com>
Date: Thu, 10 Dec 2020 18:36:07 +0000
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: tools-implementation@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-implementation/fcVPHijRkmNRcsvtlP8JEw99YS8>
Subject: Re: [Tools-implementation] 2nd iteration: Re: Draft of message about chat trials
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: Thu, 10 Dec 2020 18:37:56 -0000

On Thu, Dec 10, 2020, at 6:10 PM, Glen wrote:
> This seems good to me...

+1
> 
> Glen
> 
> On 12/10/2020 06:34, Robert Sparks wrote:
> > I've tried to worked the spirit of Glen's suggestions into the text, and 
> > aimed people at some specific resources on matrix and zulip
> > 
> > Some inline comments at the end.
> > 
> > ===========
> > 
> > To: ietf-announce
> > 
> > Subject: Next steps: chat service trials
> > 
> > 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
> > 
> > =====
> > 
> > On 12/9/20 2:02 PM, Jay Daley wrote:
> >> I’m too busy right now to give detailed feedback but I like all of 
> >> Glen’s suggestions.
> >>
> >> Jay
> >>
> >>> On 10/12/2020, at 8:50 AM, Glen <glen@amsl.com 
> >>> <mailto:glen@amsl.com>> wrote:
> >>>
> >>> On 12/9/2020 11:30, Robert Sparks wrote:
> >>>> Do you think this is sufficient or do we need to take a different 
> >>>> approach?
> >>>
> >>> Might I suggest one potential add:
> >>>
> >>> Truncating for focus.... maybe between these two sections add 
> >>> something like:
> >>>
> >>> --snip--
> >>>
> >>>> 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 <mailto:tools-discuss@ietf.org>.
> >>>
> >>> If you are interested in using these services more directly for your 
> >>> working 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 let 
> >>> us know so we can help accommodate.   We especially encourage 
> >>> leadership teams, and groups with an interest in remote 
> >>> participation/communication to get involved here.
> > I think we directly approach the IESG, IAB, IRTF chair, and manycouches 
> > (which is the shmoo list) with followup messages.
> >>>
> >>> If you are one of those who has had, or has reported, issues using 
> >>> Jabber, please take some time now to work with these new services and 
> >>> help the IETF help the community.
> >>>
> >>> The more usage and exposure these services get, the better informed 
> >>> the IETF's future planning will be.
> >>>
> >>>> 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.
> >>>
> >>> --snip--
> >>>
> >>> My thoughts just for this list (and its public archive):
> >>>
> >>> I feel like we don't want to just be observers here.  We've all heard 
> >>> *repeated* complaints about Jabber.   I like Jabber, but, really, 
> >>> we've gotten complaints, and here we're trying to solve issues, and 
> >>> we've had...  37 people participate.
> >>>
> >>> I feel like we should encourage, even *prod*, the community to work 
> >>> with these new services (including the new Jabber client services) 
> >>> and really get involved in this process.
> >>>
> >>> And there are some obvious candidates for these things:
> >>>
> >>> * We should encourage the IESG, IAB, IRTF leadership teams to get 
> >>> involved.  Not to mention the Tools Architecture Team, and even the 
> >>> larger Tools-Discuss team.
> >>>
> >>> * We should encourage the XMPP, SHMOO, MANYCOUCHES, and any other 
> >>> such groups to get involved.
> >>>
> >>> * We should encourage anyone currently using IETF Slack or other 
> >>> alternative channels.
> >>>
> >>> * We should encourage the team members for each of the three 
> >>> protocols (i.e. the people who set up Prosody/EJabberd, Matrix, and 
> >>> Zulip) to step up and help us encourage participation.
> >>>
> >>> * Because Matrix has active attention from its developers, I have 
> >>> been hanging out on Zulip, I'd like to make an Implementation stream 
> >>> there and see if I can get the six of us involved.  :-)
> > Sure!
> >>>
> >>> * We should make clear that if people want positive change, they need 
> >>> to get involved.
> >>>
> >>> Otherwise, a less-informed decision will be made, and the community 
> >>> will be less-happy.
> >>>
> >>> You obviously don't need to use my words, or even any of this, this 
> >>> is just feedback.  The IETF needs some visible guidance and reminders 
> >>> to get involved here, and I think that falls to us.
> >>>
> >>> Glen
> >>>
> >>
> >> -- 
> >> Jay Daley
> >> IETF Executive Director
> >> jay@ietf.org <mailto:jay@ietf.org>
> >>
> >>
> > 
> 
> -- 
> Tools-implementation mailing list
> Tools-implementation@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-implementation
>