Re: [Tools-discuss] [Manycouches] Fwd: Next steps: chat service trials

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 15 December 2020 15:36 UTC

Return-Path: <alexandre.petrescu@gmail.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 0AA9A3A11DE for <tools-discuss@ietfa.amsl.com>; Tue, 15 Dec 2020 07:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.668
X-Spam-Level:
X-Spam-Status: No, score=0.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 qKGRNMai1fbF for <tools-discuss@ietfa.amsl.com>; Tue, 15 Dec 2020 07:36:09 -0800 (PST)
Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 346E83A11E7 for <tools-discuss@ietf.org>; Tue, 15 Dec 2020 07:36:09 -0800 (PST)
Received: from [IPv6:2a01:e35:2e59:ce10::da3d:a356] (unknown [IPv6:2a01:e35:2e59:ce10::da3d:a356]) by smtp4-g21.free.fr (Postfix) with ESMTP id 589A619F522 for <tools-discuss@ietf.org>; Tue, 15 Dec 2020 16:36:05 +0100 (CET)
To: tools-discuss <tools-discuss@ietf.org>
References: <f167ecf1-07f8-2f6c-31c8-0e9c2079e14d@nostrum.com> <04dd1d7d-8ee3-d5c0-d02b-059b007acb63@nostrum.com> <d0eef915-4893-79f2-6834-4e6dbb1e50e2@gmail.com> <3b673eec-3031-bbc8-6fd7-03f9180cfb0d@nostrum.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <28d2c1d6-6e1e-b788-54e8-8ff75454fd19@gmail.com>
Date: Tue, 15 Dec 2020 16:36:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <3b673eec-3031-bbc8-6fd7-03f9180cfb0d@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/6QMUJsYCaZ0qWj63RX7o94h4v_U>
Subject: Re: [Tools-discuss] [Manycouches] Fwd: Next steps: chat service trials
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: Tue, 15 Dec 2020 15:36:11 -0000


Le 14/12/2020 à 20:38, Robert Sparks a écrit :
[...]

> For convenience:
> 
> https://zulip-trial1.ietf.org, https://matrix-trial1.ietf.org and 
> https://xmpp-trial1.ietf.org

Zulip responds when clicked.  Matrix and xmpp dont; are they on IPv6?

(I am on an IPv6-only computer)

Alex

> 
> Those are detailed more thoroughly in the announcements you can re-read at
> 
> https://mailarchive.ietf.org/arch/browse/ietf-announce/?q="trial chat"
> 
> 
>>
>>> If you've used the services, please take a few minutes to provide 
>>> feedback at tools-discuss@ietf.org.
>>
>> This is a good point.  I wonder whether there can be an automated
>> forwarding between lists that have a certain common interest? E.g. when
>> I post here with 'tools' in the Subject line it also gets there, and
>> vice-versa with 'couches'.
> The zulip instance ingests a few mailing lists, but that bridge is not 
> bi-directional. There are different modes of conversation with email and 
> chat - the email reflection of chat would look similar to an email 
> reflection of a jabber room - not a very pleasant way to consume or 
> participate in the chat.
>>
>> Alex
>>
>>>
>>> RjS
>>>
>>>
>>>
>>> -------- Forwarded Message -------- Subject:     Next steps: chat 
>>> service trials Date:     Fri, 11 Dec 2020 13:00:58 -0600 From: Robert 
>>> Sparks <rjsparks@nostrum.com> Reply-To:     tools-discuss 
>>> <tools-discuss@ietf.org> To:     ietf-announce@ietf.org
>>>
>>>
>>>
>>>
>>> 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
>>>
>>> _______________________________________________ IETF-Announce
>>> mailing list IETF-Announce@ietf.org 
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>
>>> _______________________________________________ Manycouches mailing 
>>> list Manycouches@ietf.org 
>>> https://www.ietf.org/mailman/listinfo/manycouches
>>>
>>
> 
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches