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

Warren Kumari <> Wed, 10 April 2024 18:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BFE26C14F6BD for <>; Wed, 10 Apr 2024 11:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Status: No, score=-2.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_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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0GTwlac5eV8e for <>; Wed, 10 Apr 2024 11:41:48 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::529]) (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 (Postfix) with ESMTPS id 9E2B8C14F6EA for <>; Wed, 10 Apr 2024 11:41:48 -0700 (PDT)
Received: by with SMTP id 4fb4d7f45d1cf-56e2e09fc27so248746a12.0 for <>; Wed, 10 Apr 2024 11:41:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; t=1712774506; x=1713379306;; h=to:subject:message-id:date:references:in-reply-to:from:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=IQav8DcTukFcB+dJ2o8RkjUmLeFlh0PBU8LMTUVNrD8=; b=DZEvmD0U/KU9SL4uPDFtBF8h3Gr0QJQRawye28ao3bPBLtbRxsVgbFypSZCT1fAc02 P9+62Aq3qn/SK8FUDkOHQXCcjgBv4WI6l1k7O/cw+InSUcv1Rkv/49CjGXONrSEuXoPk 1vqjG7Dq2cPfFZ+EdMlR9YteUzy3mDPpbsiTQCdxYP9qE8Xb778vkhRYiieZhydeU7BB HXi00Y/zpJyVAPIxiG6NwZj5plk0SkUKw8W1NZKHlA+Dnf30TRF9T2WVM2476oJ7dO8Q g2WFaRAuAs665kB/u4485Hvi6MZk1/h34hjNUKyIdcD/qOt3knsaHx236X7wDnftml// 5jIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1712774506; x=1713379306; h=to:subject:message-id:date:references:in-reply-to:from:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IQav8DcTukFcB+dJ2o8RkjUmLeFlh0PBU8LMTUVNrD8=; b=VTTFnWVF/jhGxamSfmkpKAfpLaI34nw9Rca6Q2afUlW/ZYE+rJ/dnldnQimqLAjyjq xR6psjSjzFmvP0UWkwi3tV7adxjPmAT4nWJ40rx3AIcloCOOVYrKtLLU58p/6lxbhqHm ulZhbzH1RdnRirgGNYqDe7isSEl8jkaRvIbB+QQGj0ueXRD4rDGmoLPtFMmuQ6c2NARD fIiMryJHcernk43hhniinDmJbvlGlD8goKXfmyn4use6QoiJkJ0LqI8EztOmv5q+fXIE DA+cnJl7uxwueTfQfgEBTH5r7YDLDOYuX9hs3K2bQ+H6l+84zf02Gm/g2DS5kMccwDMT Tg9w==
X-Gm-Message-State: AOJu0YxMR/nAu1a6iICAnWmYnT/BS8Q5n6fL0dG3/4DDxF/0Vj3zI1UO ASx+fzajDZCC7tYSHS6xFbRPOjcbHLuMYfgQHUhtMCpBkKljn0zg1oFkmplazwi+vMpKHe3o7OE v+UxeTmsUbrrXSTY4ckctyTez9niosQ0v34zOluwl3spyoc2M
X-Google-Smtp-Source: AGHT+IHS8fOclcwzPNzKPXuAsfRkIsZ8s8mFhAtjG0i4bT/o6xTxuO3JB8duZdw4xEGX/0fIBoyVdpda7DVONcdL+QY=
X-Received: by 2002:a50:cc92:0:b0:56e:2c34:cff2 with SMTP id q18-20020a50cc92000000b0056e2c34cff2mr384331edi.19.1712774505899; Wed, 10 Apr 2024 11:41:45 -0700 (PDT)
Received: from 649336022844 named unknown by with HTTPREST; Wed, 10 Apr 2024 14:41:44 -0400
Mime-Version: 1.0
X-Mailer: Superhuman Desktop (2024-04-09T19:06:18Z)
From: Warren Kumari <>
X-Superhuman-ID: luu5pdsr.f5c775f0-616e-4497-887b-58e69680a70d
X-Superhuman-Draft-ID: draft00ef5a941d58d8fb
In-Reply-To: <>
References: <>
Date: Wed, 10 Apr 2024 14:41:44 -0400
Message-ID: <>
To: dnsop <>
Content-Type: multipart/alternative; boundary="0000000000000146c70615c264ed"
Archived-At: <>
Subject: Re: [DNSOP] Demo of Github issues for tracking documents and next steps..
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Apr 2024 18:41:52 -0000


Apologies all, autocomplete fail — turns out "dnsop-chairs" starts with

Sorry for the noise,

On Wed, Apr 10, 2024 at 2:36 PM, Warren Kumari <> wrote:

> Heyya chairs,
> I futzed some more with the demo GH issue tracker I created on the call,
> and invited you to the repo:
> 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:
> Temp-DNSOP_Doc_Tracker/issues?q=is%3Aopen+is%3Aissue+label%3AChairs
> Documents where we need more WG input:
> Temp-DNSOP_Doc_Tracker/
> issues?q=is%3Aopen+is%3Aissue+label%3A%22Review+needed%22
> Things that need actions from me:
> 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:
> wkumari/Temp-DNSOP_Doc_Tracker/issues/8
> 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,
> etc.
> 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?
> W