IETF Logo Mail Archive

Re: [Manycouches] IETF Slack workspace

Richard Barnes <rlb@ipv.sx> Sat, 11 July 2020 22:04 UTC

Return-Path: <rlb@ipv.sx>
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 D79B63A087C for <ietf@ietfa.amsl.com>; Sat, 11 Jul 2020 15:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=ipv-sx.20150623.gappssmtp.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 C8zMXaF-SYhT for <ietf@ietfa.amsl.com>; Sat, 11 Jul 2020 15:04:18 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 3D8A33A0878 for <ietf@ietf.org>; Sat, 11 Jul 2020 15:04:17 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id i3so7237395qtq.13 for <ietf@ietf.org>; Sat, 11 Jul 2020 15:04:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OCjrUUg1udV0xfOdJmVNaOCOc/Y/JLK3tJuqVkiUp8M=; b=0AZT1rqKcmcxoWLdM5OT/DaNS8F2vyv7gftg+zwLIEOZf5KL9SgRBtb4nWxKxpkbS9 AoPCJ/Gkjeab94ETKD2feB3ryvl1tlhoBkKcUxAeXf+4071//b1rPHB6JIqVm6LaySer 3w0NdEU5FL0FgsprjYZchws38OGrSN6hUo9VSVxqQehyq8Na8J0aInCP7/lSuktcB4Xm 1owbP9vulGUoTaDFO0+Kqj+7ksCMnwl37IeMjFbZbsNWPHDrumH/T+ush2CFCe0NM+Zx 8bOlrl704siQ+PAyWU+vIBd7RmXjRiam6hPWwrWnLUIewzTEey9gupnV+VWq8fNokH6u E2zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OCjrUUg1udV0xfOdJmVNaOCOc/Y/JLK3tJuqVkiUp8M=; b=mTgoP1C/PO2lkljnWYr8KGPQBGPkW4qo66x9OBj3j+zRcJOu+F1+2LedmOuDMErsRV cwMrr0+LaMNfB3BjijHZB6wbDcSnBv1UwksOM6Nb1cb8zxVMeWw8Zpv/o5FrLDiVPUcd 0xRO61UPcmOoz9VmCSWz4IN//2Ms4P1+LGRo7t+NXeKOkr5UCtxWN/2Yol9yCt8zL69J BzUjCQpZOTOth6yfnrd8s2pmDCALgA0N6dpH29M9e6wcu4AUA9sRztb9XeJ/OzOwB2eE RPDAokkafVuknf1AtOTYj8e+xo51G3tuwLtryaXJJYDHgApQJV4QRM4MQJgdKpdvaLuj jrig==
X-Gm-Message-State: AOAM531KTtVdnTr72whHWvKeWCWUTB/yGdp+kfpjQxA5YYNPkSBZR1vY JjvQlIci4VK+/JT0xZ8+KWAAb/h3sbuChCh3J6nBgg==
X-Google-Smtp-Source: ABdhPJxGGgTS+/HY7lxbOzrRJg+9cmCUTgD7BqmkcYoqwEREQAmpYnauVswpr30XRa/PcnlKxBw3NvTHCGIHNu3A5Rc=
X-Received: by 2002:ac8:441a:: with SMTP id j26mr77841793qtn.191.1594505056895; Sat, 11 Jul 2020 15:04:16 -0700 (PDT)
MIME-Version: 1.0
References: <3064c634-3958-f5e3-26c2-cdd148a86605@tenghardt.net> <CAMGpriUJm-Wx48bAO4LNgFzvrBO0ksQ60_Qs6iz8YL7RfzGrLw@mail.gmail.com> <aa7ee087-7314-26db-6184-2443def3cb4b@tenghardt.net> <20200711060823.GX3100@localhost> <CANMZLAY8wtq1cVtHPPAwyCvygiO2rEc9yPNotD+bdvHtZa1tTQ@mail.gmail.com>
In-Reply-To: <CANMZLAY8wtq1cVtHPPAwyCvygiO2rEc9yPNotD+bdvHtZa1tTQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Sat, 11 Jul 2020 18:03:56 -0400
Message-ID: <CAL02cgStMc7tVGL7iaP0m0gSe+TCj1dmRH5g2v-9w3vJTdXOaw@mail.gmail.com>
Subject: Re: [Manycouches] IETF Slack workspace
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: Nico Williams <nico@cryptonector.com>, Erik Kline <ek.ietf@gmail.com>, IETF discussion list <ietf@ietf.org>, manycouches@ietf.org
Content-Type: multipart/alternative; boundary="000000000000825df605aa31a30f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W-GxdRpS0uAug2nP_T7vJhdRmSo>
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 22:04:20 -0000

As Theresa said, this mechanism is explicitly for discussions that are not
IETF Contributions.  They are equivalent to hallway conversations at an
IETF meeting and will be treated as such -- they will not be archived or
included in meeting records.  Since we are using a free instance, Slack
will remove messages once we hit a 10,000 message limit.

--Richard

On Sat, Jul 11, 2020 at 6:36 AM Brian Carpenter <brian.e.carpenter@gmail.com>
wrote:

> So this presumably amounts to IETF Contributions under the IPR rules. How
> will it be added to the meeting records, like a jabber log, for the benefit
> of other participants?
>
> Regards
>     Brian
>     (via tiny screen & keyboard)
>
> On Sat, 11 Jul 2020, 18:09 Nico Williams, <nico@cryptonector.com> 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.
>>
>> Nico
>> --
>>
>> _______________________________________________
>> Manycouches mailing list
>> Manycouches@ietf.org
>> https://www.ietf.org/mailman/listinfo/manycouches
>>
>

v2.23.0 | Report a Bug | By Email