-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
Looking for new maintainer #755
Comments
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nur-is-looking-for-a-new-maintainer/51129/1 |
@Mic92 Hi, I'm learning about Nix and am interested in becoming a maintainer. |
@vedantmgoyal9 I looked up and you don't seem to have a nur repository or any other nix-related contributions. What is your motivation for maintaining this repository? |
@Mic92 As I said, I'm learning about Nix, and, a few hours ago, I made my first contribution to nixpkgs too. I'm developing a project RustReleaser, which is basically "goreleaser, but for rust", and was looking to support publishing packages to a nur. That's where my Nix journey began, and I'm yet to learn more about it :) |
I don't think I'm personally qualified to maintain this project, but I would like to co-maintain with others so I can learn Nix from them. I'm currently maintaining two packages from nixpkgs and contributing to some nix-community projects (mostly regarding the Emacs ecosystem). I'm planning to use NUR more, so I don't want it to be archived anytime soon. 🤔 |
I‘m also new to Nix language and I'd be interested to dive deeper and be a co-maintainer of NUR. |
I need to be a maintainer of NUR. |
I've got a lot of experience with nixpkgs, although I have no experience with NUR. I'd be happy to be a maintainer if it can avoid NUR shutting down. |
I am not using NUR directly myself actually for a while, but it seems that many other people do.
For me personally flakes have replaced the schema that I also introduced with NUR.
Therefore, I would like to transfer the project to a new maintainer.
The work is not too much for the most part as most repositories are self-contained.
However there are probably infrastructure and CI that could be improved.
I set the 01.01.2025 as a deadline, if there is no new maintainer found until than, I may archive the project by then.
The text was updated successfully, but these errors were encountered: