[SCITT] Questions regarding automated per-commit notifications from GitHub to architecture draft

Alexander Stein <ajstein.standards@gmail.com> Tue, 16 April 2024 18:34 UTC

Return-Path: <ajstein.standards@gmail.com>
X-Original-To: scitt@ietfa.amsl.com
Delivered-To: scitt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E80B1C14F602 for <scitt@ietfa.amsl.com>; Tue, 16 Apr 2024 11:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 (2048-bit key) header.d=gmail.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 4LkH5FyHn3Kr for <scitt@ietfa.amsl.com>; Tue, 16 Apr 2024 11:34:32 -0700 (PDT)
Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 1A455C14F615 for <scitt@ietf.org>; Tue, 16 Apr 2024 11:34:32 -0700 (PDT)
Received: by mail-io1-xd44.google.com with SMTP id ca18e2360f4ac-7d5de651252so220029339f.2 for <scitt@ietf.org>; Tue, 16 Apr 2024 11:34:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713292471; x=1713897271; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UDncPvmMKJp7osSgLrnsVsLG2PQzhWO3WftsPNaCg9Y=; b=lvnGQ+Hp4vZBWciAQyNycMRZTIY3gYFWplAiS/gdypZsEBeI3Hov7Mc2A3yxRBvQyQ IcCpo2EtUiObpM0JQGFhADMuTi2zcxQkIF7I/dzTA46LHmRZmCnqdosSlNl34mGmgELr 0oCVmwaxxF0IW+SKQw6iCqMXkMOi/8d6Rzbx4ehpDA4vRuuO7/avGioFNn4YgI80lTPu 2p1/0e4zLXz2r5nqlnQaHuSNuq9Ddnj2ZUWxPoI+YfYwN7u8UCtYwnskRyquJPiZcok8 FlQt6beC6N90oIiA9L9BbwEWECiwJjdB6ffKl7bERNAD1T28eBSPbJa4Fq9/+YWSkrHZ WCBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713292471; x=1713897271; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UDncPvmMKJp7osSgLrnsVsLG2PQzhWO3WftsPNaCg9Y=; b=tch6T8XJYF2Znr1T91kmis8yTVZgnKerYRDhlBVK62ztOdYQZdSmhF6TTvKg2OQht0 WTRbVmO9Uwqd1TcjItyxhyecDjs+sfK1Qd5raS9whndqqPfSlKS95YM8Z8Fw/sp0PzTp d8v8AuY22glugm3KDJ6Tlyz8V4ZsX/GZvSmxlddPAErWv+zzbJgbCYDZTyIx4pMzE4cm TUWER9DFgoxa/3JgXjNZ/wru5kRufwLPSMFFomPYfYQGX4GQFFeNpyovL009tO11ncZx tQQT2Cot1VHzhkWi7YuZ42rd5PHAKSfmXJlmGElLHou8nusA3eTOqe1tSs8r4MGiSJ6X 9qNw==
X-Gm-Message-State: AOJu0YzVadUlIrGuso4o7hy/DndK7MjVoe0fyek/y2R2tPgE9TiAudBS KrldBHsOe2JVCyOLamrbubpav7xk049lTDUAU4PlAOcXAiIDmTS9sZAmDdwItHrGqfSqr3tL0sB W773PvSb+JVAoQRUazB+WiE00KAu4+cwEREc=
X-Google-Smtp-Source: AGHT+IHFrKRkxTJlMPfj4EjB54oS5YDt3pdqRnbYJCP+d/9zL8xdHhBo/10CBxpb1H8qCmTXxJL1G/8K1DOTyu/+5Vs=
X-Received: by 2002:a05:6e02:1d02:b0:36b:2731:7334 with SMTP id i2-20020a056e021d0200b0036b27317334mr5163320ila.21.1713292470777; Tue, 16 Apr 2024 11:34:30 -0700 (PDT)
MIME-Version: 1.0
From: Alexander Stein <ajstein.standards@gmail.com>
Date: Tue, 16 Apr 2024 14:34:19 -0400
Message-ID: <CAMvBLPK=+K3qydoavPzX7WB5RQr4yVuCbGQPXvVkyV4FuA6urQ@mail.gmail.com>
To: scitt <scitt@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001e04b306163afdc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scitt/onMB_PAjqX6-_8w2m4fvDdP9puM>
Subject: [SCITT] Questions regarding automated per-commit notifications from GitHub to architecture draft
X-BeenThere: scitt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Supply Chain Integrity, Transparency, and Trust" <scitt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scitt>, <mailto:scitt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scitt/>
List-Post: <mailto:scitt@ietf.org>
List-Help: <mailto:scitt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scitt>, <mailto:scitt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2024 18:34:36 -0000

Hello,

I recall this topic coming up recently, I had an observation about these
notifications, constructive criticism, and an offer to help if others agree
with my recommendation to optimize the current email template.

As of April 15, 2024, it seems we have enabled some level of automation (I
am not sure where; I thought it was GitHub Actions and I seem to be
mistaken) to send an email notice to this mailing list for every commit on
every branch for only the SCITT Architecture I-D. This appears to be the
first of this series of frequent updates.

https://mailarchive.ietf.org/arch/msg/scitt/AmTHkjsf30vCoURU9WIdnEBw-Ng/

Although I appreciate the heads up, this particular kind of email is
replicating what is already possible directly for every user with GitHub by
clicking the Watch option and selecting the All Activity option for every
repo of interest (as opposed to the as @ mentions and subscribed issues
only default).

If I recall the original request correctly, this change originated from a
request for a summary email of all current issues and pull requests for the
WG (this implies multiple repositories), not the per-commit detail. I
understood this as someone asking for a very similar report to this weekly
message for all subscribers on the COSE-WG list. Below is the most recent
example.

https://mailarchive.ietf.org/arch/msg/cose/KVbLe4nMjuHVB7kxB2nLH7y_ASQ/

To wit, this summary, which I believe is more inline with what is being
asked, is not readily available with GitHub functionality as-is.

Would others be amenable to the COSE WG variant? If we all get these
notifications (to the mailing list and not togglable for each of our GitHub
user accounts), I would find the COSE more beneficial and I find it more
informative (list new issues and PRs with comments and their summarized
titles). I am now essentially doubling up on new PR and commit updates.

If others agree with me, I can work with the chairs or whomever set that up
to adjust it.

Regards,
A.J.