Skip to content
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

Closed
nrdxp opened this issue Nov 17, 2021 · 5 comments
Closed

Call for Maintainers #400

nrdxp opened this issue Nov 17, 2021 · 5 comments

Comments

@nrdxp
Copy link
Collaborator

nrdxp commented Nov 17, 2021

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!

@Princemachiavelli
Copy link

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.

  • Taking advantage of any upstream home-manager improvements like proper 2.4 profile support, etc.
  • Making the usage of portable HM users and system users a bit cleaner would be nice.
  • (Mostly a home-manager issue) Provide a unified way to define a user's SSH authorized keys for both system users and portable users.
  • Documenting a method for setting home-manager defaults.
  • Support for LDAP/unknown/generic users.

Deployment improvements

  • (Mostly an deploy-rs issue) Adding support password protected SUDO/privileges escalation methods.
  • Workflow for automatically updating the nixpkgs inputs so Nix's autoUpgrade feature can install routine package updates.
  • Possible bud improvements or integration with makes (at least once it gets proper flake support).

@nrdxp
Copy link
Collaborator Author

nrdxp commented Nov 22, 2021

yes, I should have clarified that in the original announcement, but this is geared toward maintainership of digga as well.

@Pacman99
Copy link
Member

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.
I think the main reason for this post is to find people who have the capacity to develop new features and get to those chores faster than we can.

@Pacman99
Copy link
Member

We have a new maintainer onboard! Welcome @montchr :)

@montchr
Copy link
Collaborator

montchr commented Feb 26, 2022

Thank you!

@Pacman99 Pacman99 closed this as completed Apr 1, 2022
@Pacman99 Pacman99 unpinned this issue Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants