-
Notifications
You must be signed in to change notification settings - Fork 107
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
Call for Maintainers #400
Comments
Does this apply to the related divnix projects; digga and bud? I currently use devos in several production projects and have plans for more so I certainly have a vested interest in keeping everything functional. Since I haven't directly contributed more than the occasional bug report I'm may not be the best fit for a maintainer currently but I have started reviewing many of the open tickets & PRs. I can certainly help work through those. I'm not sure what the current roadmap or priorities for devos/divnix are but there are a few areas I will be looking into: Better home-manager integration and user management.
Deployment improvements
|
yes, I should have clarified that in the original announcement, but this is geared toward maintainership of digga as well. |
I do want to note that I don't plan to stop maintaining these projects. And I think the future of the projects are relatively secure. I use digga for a number of computers, so I have a stake in keeping them maintained. I can commit to dealing with bugfixes, updates, and PR reviews - they just might take me some time to get to. Over time I'll try to keep improving the documentation. |
We have a new maintainer onboard! Welcome @montchr :) |
Thank you! |
While @blaggacao, @Pacman99 and myself have become busier with personal obligations, we've noticed a lag in our ability to maintain the project. There are several members of the community besides ourselves who have been very active, and we'd be more than happy for the help if anyone is up to the task. Please feel free to drop a reply in this issue if you'd like to help!
The text was updated successfully, but these errors were encountered: