Should we archive this repo?

[trishankatdatadog]

Should we mark this repository as archived? It has long since not seen active development, and is probably not the best reference implementation for various reasons.

[lukpueh]

It has long since not seen active development

True. It also pins some outdated dependencies and a stale TUF fork hosted by @awwad.

not the best reference implementation for various reasons.

Can't tell. Do you have any particular reasons in mind? The demo instructions seem quite elaborate to me.

Should we mark this repository as archived?

I think we should. As per the GitHub docs on archiving the repo will remain visible and available in read-only mode, so visitors can still use it for educational purposes.

If wished, I can patch the README to say that this repo currently is not under active development (but may still be used as a guide to learn the standard?). cc CB @JustinCappos and co-maintainers @mnm678, @SantiagoTorres, @awwad.

[JustinCappos]

I'm supportive of this.

…

On Mon, Nov 23, 2020 at 5:12 PM lukpueh ***@***.***> wrote: It has long since not seen active development True. It also pins some outdated dependencies and a stale TUF fork hosted by @awwad <https://github.com/awwad>. not the best reference implementation for various reasons. Can't tell. Do you have any particular reasons in mind? The demo instructions seem quite elaborate to me. Should we mark this repository as archived? I think we should. As per the GitHub docs on archiving ***@***.***/github/creating-cloning-and-archiving-repositories/about-archiving-repositories> the repo will remain visible and available in read-only mode, so visitors can still use it for educational purposes. If wished, I can patch the README to say that this repo currently is not under active development (but may still be used as a guide to learn the standard?). cc CB @JustinCappos <https://github.com/JustinCappos> and co-maintainers @mnm678 <https://github.com/mnm678>, @SantiagoTorres <https://github.com/SantiagoTorres>, @awwad <https://github.com/awwad>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#205 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGRODYFIVKFH6KTKP2LGU3SRIROZANCNFSM4T7CRXQQ> .

[mnm678]

I agree. This repo is probably already missing newer changes to Uptane, so achiving it will make it more clear that this is an implementation of an older version of the standard.

[lukpueh]

See #206 for the mentioned README patch.