Re: [Manycouches] IETF Slack workspace

ned+ietf@mauve.mrochek.com Sat, 11 July 2020 18:56 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E811C3A116C for <ietf@ietfa.amsl.com>; Sat, 11 Jul 2020 11:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable 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 jQBN5zxB5uUb for <ietf@ietfa.amsl.com>; Sat, 11 Jul 2020 11:56:06 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (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 EA62A3A116E for <ietf@ietf.org>; Sat, 11 Jul 2020 11:56:05 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RN40HT4OIO007ZPL@mauve.mrochek.com> for ietf@ietf.org; Sat, 11 Jul 2020 11:51:02 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RN40CMUE800076ZY@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 11 Jul 2020 11:50:54 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Cc: Nico Williams <nico@cryptonector.com>, Erik Kline <ek.ietf@gmail.com>, ietf@ietf.org, manycouches@ietf.org
Message-id: <01RN40HLHDA20076ZY@mauve.mrochek.com>
Date: Sat, 11 Jul 2020 11:47:47 -0700 (PDT)
Subject: Re: [Manycouches] IETF Slack workspace
In-reply-to: "Your message dated Sat, 11 Jul 2020 11:19:56 -0700" <dbc30fd2-bef3-eada-71ee-22baa70cb890@tenghardt.net>
References: <3064c634-3958-f5e3-26c2-cdd148a86605@tenghardt.net> <CAMGpriUJm-Wx48bAO4LNgFzvrBO0ksQ60_Qs6iz8YL7RfzGrLw@mail.gmail.com> <aa7ee087-7314-26db-6184-2443def3cb4b@tenghardt.net> <20200711060823.GX3100@localhost> <dbc30fd2-bef3-eada-71ee-22baa70cb890@tenghardt.net>
To: Theresa Enghardt <ietf@tenghardt.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Lj_n8V8ot7egQTchPjsYw-NJOE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jul 2020 18:56:08 -0000

> On 10.07.20 23:08, Nico Williams wrote:
> > On Fri, Jul 10, 2020 at 10:25:48PM -0700, Theresa Enghardt wrote:
> >> On 10.07.20 22:20, Erik Kline wrote:
> >>> How will conversations on Jabber be synchronized with those on Slack?
> >> So far we are not planning to bridge or synchronize both
> >> technologies/platforms by any technical means.
> > Hmmm.  Might I suggest then that the experiment be limited to one or two
> > WG meetings?  Otherwise this split may prove quite disruptive.

> Slack is neither intended as a replacement for Jabber, nor is its usage
> tied to any particular WG meeting.

> We rather envision it to be used for more ad-hoc, side conversations,
> for which no Jabber channel exists.

I am required to use Slack at work. There's probably an amount of pressure
sufficient to compell me to immerse myself in the IET's version of "let
everyone else define your folder structure for you", but rest assured it would
be very high indeed.

FWIW.

				Ned