Add simple-acme to clients.json#1880
Conversation
There was a problem hiding this comment.
to following Let's Encrypt's official guide for PR
we also need to update data/clients.json 's Line 2 "lastmod"
https://letsencrypt.org/docs/client-options/#adding-a-client-project
There was a problem hiding this comment.
Thanks, I've updated the date as well now.
|
Can anyone clarify why this pr is stalled? I'm not involved in it from either side: I'm simply a participant in the acme ecosystem, wanting to see that others learn (on the acme clients page) of simpleacme, as it's the key fork of winacme (by its primary maintainer). Also, at what point might it make sense to remove winacme from the list, or at least to mark it deprecated/no longer supported. The front page if its repo makes that point clear. But folks following the link here to the winacme WEB SITE would not know it. The bottom of the simpleacme site offers a link to a page with the history of the two projects, for those uninformed: https://simple-acme.com/manual/about/simple-acme |
|
I see that the pending change (to the docs/client-options/index.html and language-specific variants) does at least now add simple-acme...but in listing it at the bottom (as the "spiritual successor to win-acme"), I'd fear most folks may still just choose win-acme since it's near the top of the list. I'd asked in my July comment:
Can anyone speak to that, before just closing this once the pending merge conflict is resolved? Or is this not the right place to discuss such things? I'm just a user, not a maintainer or even contributor. |
|
@carehart I've written a script that will annotate the clients.json with automatically-obtained last-modified data, and the current plan is to hide clients that haven't had any code updates since some threshold time. At some point win-acme will hit that threshold and be hidden, but we might also be able to have a manual annotation for projects that have declared themselves unmaintained. |
|
Sweet. Great to hear on both counts, and thanks so much.
|
|
Thanks, I'm including this via #2018. |
Important
If this PR updates a file in
content/enwith alastmodfield, it must be updated.If this PR is a translation, please read TRANSLATION.md first.