mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 12:55:48 +03:00
[GH-ISSUE #350] Is this project still active? #195
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @saudiqbal on GitHub (Mar 8, 2024).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/350
I see a lot of pull requests and no activity, is this project abandoned?
@dusatvoj commented on GitHub (Apr 20, 2024):
It looks that @joohoi left the one man show project 😕 . Pretty strange when it's such important project for FOSS community.
@joohoi commented on GitHub (Apr 20, 2024):
Still here. Working on rewriting some tests for the refactoring PR #325
that is a blocker for anything else atm as the main branch will see large
changes.
After the rewrite, there are plans to move it to a different, organization
namespace where the project is able to more conveniently allow adding new
maintainers. As acme-dns operates largely in a trust - space, it will be
interesting to see how to best handle this especially in the light of
recent dependency chain attacks.
I have very limited time at my hands
On Sun 21. Apr 2024 at 0.25, dusatvoj @.***> wrote:
@dusatvoj commented on GitHub (Apr 20, 2024):
@joohoi , glad to hear that. I'm looking forward for things you mentioned 👍 🙏
@saudiqbal commented on GitHub (Apr 21, 2024):
Good to see this project is still active, also don't forget about https://github.com/joohoi/acme-dns/issues/345 to make acme-dns more secure.
@maddes-b commented on GitHub (Oct 29, 2024):
Count me in. I would be willing to maintain the current master, and also "port forward" changes to https://github.com/joohoi/acme-dns/pull/325
@shaneshort commented on GitHub (Dec 9, 2024):
@joohoi any update on this? is there anything anyone can do to try and help get this over the line?
@laf0rge commented on GitHub (Dec 16, 2024):
With all respect to @joohoi as the original author, it is clear that there are a lot of users reporting a lot of issues during 2+ years, and PRs are piling up without either getting merged or meaningful feedback. As a maintainer of many other FOSS projects myself, I sympathesize with the overload situation.
But in the interest of the [production] userse of the project, I would certianly appreciate if other maintainer[s] would be enabled to step up. I've read the plan was to do this after #325 - but the last news on that was more than 6 months ago.
Thanks to @maddes-b for offering to step up.
@joohoi commented on GitHub (Dec 16, 2024):
Yeah, I would love to get any and all help possible in #325 to get the tests up-to-par (the main remaining issue atm). That's the main "2.0" PR that needs to be landed in order to get the codebase more maintainable, and it's the mental milestone to get acme-dns to a more distributed maintenance model and moved to acme-dns organization.
@shaneshort commented on GitHub (Dec 16, 2024):
@joohoi I've managed to rope someone in to try and help get this over the line. Is there a discord channel or something we could find you on to chat about it?
@qzio commented on GitHub (Oct 13, 2025):
Any updates on this?
I would really like to use this project, but it's a bit unclear if it is active or not.
Would it make sense to fork and/or rewrite if #325 never gets through?
Maybe there is a similar project that does the same thing?