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

[Warren Kumari <[e-mail]>]

Gaaaaah….

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

Sorry for the noise,
W


On Wed, Apr 10, 2024 at 2:36 PM, Warren Kumari <[e-mail]> wrote:

> 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: https://github.com/wkumari/
> Temp-DNSOP_Doc_Tracker/issues?q=is%3Aopen+is%3Aissue+label%3AChairs
>
> Documents where we need more WG input: https://github.com/wkumari/
> Temp-DNSOP_Doc_Tracker/
> issues?q=is%3Aopen+is%3Aissue+label%3A%22Review+needed%22
>
> 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: https://github.com/
> 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
>