[DNSOP] Demo of Github issues for tracking documents and next steps..

Warren Kumari <warren@kumari.net> Wed, 10 April 2024 18:36 UTC

Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4DE40C14F6B7 for <dnsop@ietfa.amsl.com>; Wed, 10 Apr 2024 11:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Status: No, score=-7.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=kumari.net
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1aDd8iEMxQwM for <dnsop@ietfa.amsl.com>; Wed, 10 Apr 2024 11:36:34 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 2C5B7C14F618 for <dnsop@ietf.org>; Wed, 10 Apr 2024 11:36:33 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-56e6acb39d4so4210452a12.1 for <dnsop@ietf.org>; Wed, 10 Apr 2024 11:36:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; t=1712774191; x=1713378991; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=uAqGG/LG5KvY+tP/6XOmS/6yGYc1LgDP9Hv182Id0UU=; b=KR0dN7j2lpTZDd7vOlpkPTDJ39pVLTodOXQcKj1UPby9ocB4i5C1d5FDUAUKC7XVCD MnGCf/OZZTL4Pf03jCDgYIfr++O3L5lWlWRUJaggPVWLMmzQd/AoqO+fxqQD5w/RB+gv PGlnovs0ppun27qkQJKfwYeV6Eyo9eQIk33PtDATMQnSfszeytwT9xlmfdhTkTQEXMGJ rTNMqLzRq4bnhXR+f75Q537aTVC6qHuo5HSLonGP2CE1txm8Mh4+fhFj8+Rj30nZ3qhV xZ6atdtAM98MPD/vpwtS83mIRDcd6zq9pNBWINHDMhKsTum3E9YYHrA+/p79Let6T+rP O37g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712774191; x=1713378991; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=uAqGG/LG5KvY+tP/6XOmS/6yGYc1LgDP9Hv182Id0UU=; b=P6ROfHQVEsuSMwSrD8R3wABjsk04U/0I944XUBMv4b4r/k8ahlhmLtazuVd7ftuhzk uFODEz5oxe7pJkFzN6EAOn3frfq4EgyBUF85Ts3h3IZe8ERgzggowQzi3rOCzMch7o1h op0H6Nls6Z/MFQo0lrggMdaV5QjMw2JgEDKjWlDLNlx2rLPK/gCIWtQh0xkN3tcVLpNU m4alqtmYppQx6oK8JwE9fUcbYxsJw38h5y8lc5M0TNoZ2x7zR7TneTEAMfL3ybJcp2nu qeu2/lEyTC/amBVqXnmK8Pdxwl4oW2F5qAIrkOdQ/fOreS1x/xC2S4uaeDMPaYJr8ek0 F+BA==
X-Gm-Message-State: AOJu0YwzoFLgM1PY6d36yolAmDGLUMFmwtqNtGIqYCXyD/eXtQPq2aGu Pc9FfW0vhbiJrEGHQxUorcNHNa9s7pczyn2oG7HpYx4IVM4Pp+qXNyN4FxgMdaRXw6EYLveTUDb HsRPJzDPTvwpITaAzL0ogQs8btx1KlM5U2lTPap0NopnwHOV8
X-Google-Smtp-Source: AGHT+IEEizlAmRrE8Fzj/4Feeorons6AkzkssCZ0B3ogsD4+KAlMt0i8eviiWtBFELqFWYyAedenKJpadsxQIZislE8=
X-Received: by 2002:a50:bb07:0:b0:56e:6aa:c7c4 with SMTP id y7-20020a50bb07000000b0056e06aac7c4mr2099442ede.42.1712774190621; Wed, 10 Apr 2024 11:36:30 -0700 (PDT)
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Wed, 10 Apr 2024 14:36:28 -0400
Mime-Version: 1.0
X-Superhuman-Draft-ID: draft00b48a91fde6a91c
X-Superhuman-Thread-ID: draft00460a6f7daa30df
From: Warren Kumari <warren@kumari.net>
X-Mailer: Superhuman Desktop (2024-04-09T19:06:18Z)
X-Superhuman-ID: luu5iluw.2c2c78fd-f50b-49ba-ab27-f8dfb11a55de
Date: Wed, 10 Apr 2024 14:36:28 -0400
Message-ID: <CAHw9_i+_mOCp-RVf0sUPu3Kg5HOTXpzO6gt94KZ1PrA7g4VLqQ@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000368bbe0615c25190"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vthus4KdM-MJdenGRtwaYeQSIpY>
Subject: [DNSOP] Demo of Github issues for tracking documents and next steps..
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2024 18:36:38 -0000

Heyya chairs,

I futzed some more with the demo GH issue tracker I created on the call,
and invited you to the repo:
https://github.com/wkumari/Temp-DNSOP_Doc_Tracker/issues . I did also play
more with github projects (and some other project / ticket things), but
they don't really looks like they would work well for this….

I've only put in a few drafts and labels, but I think that it gives a
flavor of how we might be able to use it to track, and more importantly,
communicate the status of documents.

Some examples:
Documents waiting on chairs:

Documents where we need more WG input:

Things that need actions from me:
https://github.com/wkumari/Temp-DNSOP_Doc_Tracker/issues/assigned/wkumari (once
you've accepted the GH repo invite we demo assigning things to you).

A document with some more detail / synthetic info:

Clearly this is just a demo (and it will be much much more useful after
it's been used for a while and so actually has useful information / data),
but I figured it was worth playing with.

Ideally, once we've had a look (and probably added some more labels, etc.)
we can share it with the WG, and see what they think. People should be able
to subscribe to particular issues, and so get updates when things change,
I'd also like to look into adding labels for "I'm requesting CfA" or
"Requesting WGLC" that authors/participants can apply - this seems like it
will be easier to track than a request buried in the bottom of an email.

I fully agree with Suz it's sucky that we will have the same info in
multiple places (DT, GH, etc) — ideally, after some amount of timing we can
write up good feature requests, and ask the tools team to fold some of
this into the datatracker. Yes, DT does already have the "History" tab for
each draft, but the info there isn't shown on the dashboard, and you cannot
(yet) add tags, etc.

In the meantime we can probably write some simple automation to copy DT
into into GH issues…

Thoughts?  Does this seem useful?