Re: [Manycouches] re-engaging the manycouches mailing list

Melinda Shore <melinda.shore@gmail.com> Mon, 25 March 2019 19:24 UTC

Return-Path: <melinda.shore@gmail.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C0512079B for <manycouches@ietfa.amsl.com>; Mon, 25 Mar 2019 12:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 b6r3S1IY1VdN for <manycouches@ietfa.amsl.com>; Mon, 25 Mar 2019 12:24:46 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 6C5B0120020 for <manycouches@ietf.org>; Mon, 25 Mar 2019 12:24:46 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id cv12so415472plb.9 for <manycouches@ietf.org>; Mon, 25 Mar 2019 12:24:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=OLh2lRH45aot3E1ohYJSg5obD8gSPyVjmm8srreT0Ik=; b=Rice+QweMyW2c7kejHE40gKAhBwHKJH+J2G3u1bXuZgPw6kU6+T8+n+A0tu7ndrNjG ubmF7qAAOqcSR8mAylypthfguRaS3HzPojRjKduYwcJ56HSR/z78BTDWlNOxovunQSFc Lu18kovP6abUPouSsrMFwYwtEi4xI30jbJLU4IpgMwqU24+oG9A3MaKh4aFthqVRT5L5 MaVuAqaC37xMgyuYctwKMJeOPnbrV2+8hn3gjNsTeXnRHLhP/n3uf8KvBzd7iIU0iu4s +dS8kioJiqohIDgd3e9KhG3Ni6ZlM+kwydt3TM3Ox2VOn2mj6nZ4nHflq5jabg/gXf1V zEAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=OLh2lRH45aot3E1ohYJSg5obD8gSPyVjmm8srreT0Ik=; b=BcxLSCnLNB61SEixquU/I7k0hMXoObyEHmuDBi9B9pkpGkQu7vdt9nZMT9dBr51N9D wjwqTk4Ngcq6j/mnkQNjKxYXVhj8zn5HJHvOIHFScI0r7hey0FeXqEDDkes1EBo3QiQY YlO4vxpqwKa+naCpuaooHIu7UQDE4zrBXlW0Rh0WsLAr4NZMZ/Tko0U+hslCkkUjVb57 hOq0MWo4ST7VuXweh4ahbw/8vofuIMrKKgqCCgZGNgkEzb3pep90/GdmFIEJsHc7s+ih Qz77cL4o1VD8b7MpQvzYQlAXxAiRKuA1TtHQMpYfx469Ceoo8cONos4i2aTpz0BuzWWT Gz6g==
X-Gm-Message-State: APjAAAXRFUcNiouYH6iZqvktzwsDtrUQ5gJVIKZvnXKnKODjfJgKWybG RWVztT/G5uB6hgU+5pXoOQ84HHuJCio=
X-Google-Smtp-Source: APXvYqwv5u+1Wyb8ywSnLvAF+6xOd7g1wV0nV3mtPNO7CQHuyW2npoVyQU1yvyvTMYjwftQv2QUtow==
X-Received: by 2002:a17:902:8a4:: with SMTP id 33mr25707713pll.7.1553541885294; Mon, 25 Mar 2019 12:24:45 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local ([173.239.198.243]) by smtp.gmail.com with ESMTPSA id l74sm16749413pfi.174.2019.03.25.12.24.44 for <manycouches@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Mar 2019 12:24:44 -0700 (PDT)
To: manycouches@ietf.org
References: <ybl4l7q4vhy.fsf@wu.hardakers.net>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <d2e09150-64cf-9ff2-5db8-ef7e454587cf@gmail.com>
Date: Mon, 25 Mar 2019 20:24:43 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <ybl4l7q4vhy.fsf@wu.hardakers.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/3rzmJB_vwzdzd1Y4QXpXzHQCKXk>
Subject: Re: [Manycouches] re-engaging the manycouches mailing list
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 19:24:48 -0000

On 3/25/19 8:14 PM, Wes Hardaker wrote:
> In the mean time, does anyone on this list object to us stealing this
> list for follow on discussions to this excellent past work?  If not, you
> may suddenly see a lot more traffic (hopefully) after Tuesday this week.

I think it's outstanding - you'll need to track down who
currently owns the mailing list and get management credentials,
etc., but I'm really glad to see some movement on this again.

Unfortunately I think I'll have to miss tomorrow's meeting but
I'm very interested in 1) seeing this happens, and 2) making sure
that our processes can adapt well to completely virtual meetings
(and vice versa).

A big "yay" from here,

Melinda