-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still active? #350
Comments
It looks that @joohoi left the one man show project 😕 . Pretty strange when it's such important project for FOSS community. |
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:
It looks that @joohoi <https://github.com/joohoi> left the one man show
project 😕 . Pretty strange when it's such important project for FOSS
community.
—
Reply to this email directly, view it on GitHub
<#350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABH6DJKLNC55EX4BCJCMTNDY6LMNBAVCNFSM6AAAAABENDR2A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXG44DKNJWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@joohoi , glad to hear that. I'm looking forward for things you mentioned 👍 🙏 |
Good to see this project is still active, also don't forget about #345 to make acme-dns more secure. |
Count me in. I would be willing to maintain the current master, and also "port forward" changes to #325 |
@joohoi any update on this? is there anything anyone can do to try and help get this over the line? |
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. |
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. |
@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? |
I see a lot of pull requests and no activity, is this project abandoned?
The text was updated successfully, but these errors were encountered: