IETF Logo Mail Archive

Re: zulip.ietf.org is fully deployed.

Robert Sparks <rjsparks@nostrum.com> Wed, 18 May 2022 21:18 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 151F3C1850DC for <wgchairs@ietfa.amsl.com>; Wed, 18 May 2022 14:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.933
X-Spam-Level:
X-Spam-Status: No, score=-8.933 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, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSc2tFUBGl2F for <wgchairs@ietfa.amsl.com>; Wed, 18 May 2022 14:18:51 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4562CC1850D2 for <wgchairs@ietf.org>; Wed, 18 May 2022 14:18:51 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 24ILImEf004088 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <wgchairs@ietf.org>; Wed, 18 May 2022 16:18:49 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1652908729; bh=3QcvCCRWtiVFJaTat/KIoIjOCGGebVKwkYOWMRZeQtA=; h=Date:To:References:From:Subject:In-Reply-To; b=k0u77ANiJqnCHSeVPJKJ7VpevVLkjoXS+vCheJZ3NIxGKosKVLPg+Uo3rtWr9bJAC UHQBaL54tF25ftjTDIwT74a9bR0xTxJtC/0lenofLz7WRb0+5qkr6sxLDSJfrZz9DV ZvVkpztOmH2tfLZ+TIdaD0nz9WOyzrLtPafBxkxk=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <3d5d94a8-e228-9a8a-ddcb-1c7a8db31e4a@nostrum.com>
Date: Wed, 18 May 2022 16:18:43 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
To: wgchairs@ietf.org
References: <d6243da0-1eaa-7406-de82-f485b692afc8@nostrum.com> <e1708af8-d0de-71c7-3eb4-32a94f500ed9@comcast.net>
From: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: zulip.ietf.org is fully deployed.
In-Reply-To: <e1708af8-d0de-71c7-3eb4-32a94f500ed9@comcast.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/RGUynCiScrt_vz3CTvsUFILGzmI>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2022 21:18:55 -0000

On 5/18/22 3:34 PM, Paul Kyzivat wrote:
> Robert,
>
> Perhaps I just haven't been paying attention, but aside from noting a 
> few passing references this is my first introduction to zulip.

There were several things that I had hoped would have caught your eye 
along the way - here are a couple of key moments:

Oct2020 starting a set of trials of various services: 
https://mailarchive.ietf.org/arch/msg/ietf-announce/UtPuWgXhYbjyf7wHGJh4ax4kQrA/ 
(which we extended through more meetings to get more feedback).

Sep2021 closing the trials and setting the way forward: 
https://mailarchive.ietf.org/arch/msg/ietf/V3I0ReOV7l-U9PUdJIl1RVlcLPs/



>
> Can you explain what role it is intended to take relative to other 
> modes of communication? I gather it is intended to replace jabber. 
It is where we've landed for chat services.
> But the integration with mailing lists is confusing.
First, note that it is a read-only integration - it is not possible to 
send to the mailing lists from within zulip (see the service plan linked 
below).

You don't have to use it. Several long-time zulip users suggested we 
provide this view from zulip into the mailing lists, since zulip's 
conversation threading model works well for them. I've found it to be a 
nice way to consume the lists that I monitor semiregularly. If it 
doesn't work for you, don't subscribe to those channels.

>
>     Thanks,
>     Paul
>
> On 5/18/22 12:53 PM, Robert Sparks wrote:
>> All -
>>
>> Zulip for the IETF has been fully deployed and is ready for use now 
>> and at IETF 114. Streams for all of the groups have been created.
>>
>> We plan for MeetEcho to use Zulip as the back-end for its chat window 
>> at 114. The associated zulip streams will be bridged to jabber for 
>> this meeting.
>>
>> For more information, see the service plan at 
>> https://github.com/ietf-tools/zulip-implementation/blob/main/Service-Plan.md 
>>
>>
>> If you discover problems or have changes to suggest, please bring 
>> them to tools-discuss@ietf.org (the Reply-To for this messages is set).
>>
>> RjS
>>
>>
>

v2.23.0 | Report a Bug | By Email