Re: [Gendispatch] WG Review: General Area Dispatch (gendispatch)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 25 October 2019 03:02 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D83B1200A3; Thu, 24 Oct 2019 20:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 0dC_ho0FZQo9; Thu, 24 Oct 2019 20:02:05 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 AA1D61200EF; Thu, 24 Oct 2019 20:02:04 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id c4so919056lja.11; Thu, 24 Oct 2019 20:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jEXBPpnC/JBa885/memVpKFm3jYUYd0s7D7BKloEU4o=; b=glQ0Ve8A0dBnlSScl6zhJwo6FcH33uL6Mrr+eUXddFvCAowQ0NZEHc+9cTiYgcrkH2 SfiMl5tUmZQ5KnJD6Ul1FwoLLEuKRpeIxlY/6fJl89XeBoVkmdT3EXrY3ICwM83p4CYV 67d71Af8i0NHZJ1/U2ZlKzpnHNWrlQ5p7bvkE3joTVN8D39RoH9JrSq5QOGd8b/b9PVm GvOmZ0q+bcmoimvONSr8uRrPpkT7mNsdqEoRf8uwSXv9RL6hIUkjKJy4XeW40lulvUjV /VepIr+jmmSldNJiYtyiso8fQCfVw/wMoXzawTWIlVoI41GUyAC5fpY0UDbM4aXhC24U vZyQ==
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=jEXBPpnC/JBa885/memVpKFm3jYUYd0s7D7BKloEU4o=; b=TubJNlPwSeg7lDkjrJc0Ktq3f+8yGY+waFyTgK/gQjPoDn0GzwZ5lB48az4b0nbSfU tBbrhw2GOqZHcBGMGbncld/NXBIw20M5SeNNzQDVr5JgFVe3sXsd1gnZfvgKQiQ7TTZ0 1i0yBNOj1cCNTsv4NpZYjOwN6+HEtyanemuSnmYbmTRIGVG/+T2dfQML4juFHl/rJdDp dINWvVWlOZ9h5yXUq96LuB7hjNcKaLH8j4cIhdL80aYa1mEtSnE1P8C2o0CfB+5Ciq/p 0xj7oyQV2hMOTmM4uJuJXbMDonRGVwQ/UYSQE00Zo8t+Y3hUsQmgU/rzi0WQNfmvAJZx S8Vw==
X-Gm-Message-State: APjAAAUUiwEZdNu3yHLVojWdbHzHYCuhzjuTxd91RNcxXpVKHLWcmpYb gwfoaVIgipuWkwzJRsQbeoDNwIYpGSw87NRsYUQ=
X-Google-Smtp-Source: APXvYqyxxqMdoc9laOFT6kuOsECfgyGAVgIdao/9nzfVVLFQeNHvrikaP53O/055qOJsIZ+VFG77gCktQjTzQg/HPYo=
X-Received: by 2002:a2e:8616:: with SMTP id a22mr15906lji.30.1571972522742; Thu, 24 Oct 2019 20:02:02 -0700 (PDT)
MIME-Version: 1.0
References: <156953786511.31837.12069537821662045851.idtracker@ietfa.amsl.com> <8A15D8AF-6B1A-42A0-85CE-DF861E73C1C2@nostrum.com> <CALaySJL0-=Jn0Wk8GR+xrGcZ6Vyv4QO+p=LgkKt5srdVu+Zh_g@mail.gmail.com> <6CC7893B-7A6C-4A6A-9AB4-9C62A4E1777A@nostrum.com> <6F6819D9-E681-4247-8C19-F87709ADB1CA@mnot.net> <2DE4AAEA-13A0-4D49-AE3E-8ACCD81BF49E@nostrum.com> <2E4933D9-ECD0-436A-9ADA-5EF6C6470C01@nostrum.com> <18383AE8-9AF2-4C93-8598-EF33F7E49A4B@cooperw.in> <6B306CEB-3DC3-4315-ADF3-56A8FCE4225E@nostrum.com> <338E53C5-08C7-470A-A7A9-EF548B00F320@cooperw.in>
In-Reply-To: <338E53C5-08C7-470A-A7A9-EF548B00F320@cooperw.in>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 24 Oct 2019 22:01:34 -0500
Message-ID: <CAKKJt-drqVgT1T3ic6j0J5OJWggB+k8DU0pZPO1RUz=P+L9p_Q@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: Ben Campbell <ben@nostrum.com>, Barry Leiba <barryleiba@computer.org>, gendispatch@ietf.org, IETF discussion list <ietf@ietf.org>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d095900595b35f9e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/MjRJelP-twzdGx_t42YWiQ_T3hM>
Subject: Re: [Gendispatch] WG Review: General Area Dispatch (gendispatch)
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2019 03:02:08 -0000

Chiming in very late hear, but only to say something I hope is encouraging
...

On Mon, Oct 14, 2019 at 7:19 AM Alissa Cooper <alissa@cooperw.in> wrote:

> Hi Ben,
>
> > On Oct 11, 2019, at 3:12 PM, Ben Campbell <ben@nostrum.com> wrote:
> >
> >
> >
> >> On Oct 11, 2019, at 4:10 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> >>
> >> Hi Ben,
> >>
> >>> On Oct 10, 2019, at 6:05 PM, Ben Campbell <ben@nostrum.com> wrote:
> >>>
> >>> Here’s an attempt to distill my concern a little better:
> >>>
> >>> The “dispatch process” can reasonably be thought of as a triage
> process. Triage makes sense when you don’t have the time and resources to
> address every problem and have to pick and choose where you can have the
> most impact. If you do have time and resources to address everything, then
> triage is just a process bump.
> >>>
> >>> Do we believe that GEN area proposals will routinely exceed our
> capacity to discuss them? If so, do we think that will continue to be true
> for the foreseeable future? (I assume this is intended to be a long-lived
> wg).
> >>
> >> I guess I see the question differently. If there are people in the
> community who are willing to manage discussions about process proposals
> while they’re in formation (i.e., people willing to chair this WG), that
> seems like a better arrangement than the current one both from the
> perspective of being more community-led and from the perspective of the
> other time commitments that the IESG has. If the WG isn’t busy or meeting
> all the time, that’s fine — it will still be nice to have it there for
> times when process proposals do come up and inspire discussion.
> >
> > I think I’ve been unclear in my concern. I have no objection to having a
> working group for discussion of proposals to improve processes. I think
> that’s a good idea. My question is about whether such working group should
> be limited to the dispatch process.
> >
> > Certainly there may be case where there it is appropriate dispatch work
> to some other venue, spin up a new wg for a proposal, etc. But I wonder why
> we need to decide in advance that work on a proposal will cannot be
> completed by this group. Especially when it seems likely that the people
> working on a proposal will often be the same whether the work happens in
> gendispatch or somewhere else.
>
> Ah, got it. This is a good question. Perhaps we can try it in
> dispatch-style for awhile and see if we’re often arriving at an outcome
> where it seems like just processing a document in the WG would be the most
> logical thing to do. If so, a re-charter to allow that would be possible. I
> was a little hesitant to jump straight to having a General Area Working
> Group; the dispatch-style group seemed like it could be a useful
> intermediate step.
>

I think trying something Dispatch-style will be helpful - it was helpful
for then-RAI to have a way to sort through proposals without having to spin
up full BOFs - and I'm reading Alissa's note here as "I want to try to do
something that could improve things, and if we need to change what we're
starting with in order to improve things, we can make changes, and keep
trying to Do The Right Thing".

That would be lovely.

Best of luck!

Spencer