-
Notifications
You must be signed in to change notification settings - Fork 126
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
New maintainers #127
Comments
May be re-post this message also on reddit/users.rust-lang.org ? |
I am willing to participate in the maintenance work. |
I'm not super invested in the Rust community anymore, but I am heavily invested into CMake (and am probably one of the more expert people in it, given my work in vcpkg); I don't know if I would be best as a primary maintainer, but I'd love to help. |
Ok I've added @strega-nil to this repository for now and sorry @PsiACE I don't recognize you but if you're willing please feel free to help out reviewing PRs and triaging things, it would be greatly appreciated! If it goes well I'd be happy to add you too. |
Ok I've decided that my time maintaining this crate has now come to a close. @strega-nil if you'd like I can transfer to you, but otherwise I won't be maintaining this crate unless something like a security issue comes up. |
Hi @alexcrichton, I can try to help with maintaining this crate if you're open to it. I'm not a heavy cmake user, but I do have some projects that leverage this and I'd like to make sure they continue to compile. |
Hey, I also depend upon this crate for work, happy to help with maintenance. |
To clarify I'm not necessarily looking for assistance in maintainership any more, I'm more looking now to completely transfer this repository to a new owner. |
That's understandable. @m-ou-se suggested migrating |
We are a small team at https://github.com/enhancecp our code mostly is closed but happy to take ownership and maintain it as a team. Along with other OS devs. Please let us know if something can be worked out. |
This issue seems ot be hidden deep and hard to find. It seems to me such a state of the crate has ot be announced at least at the top of the 'front page' README.md - so would be easily visible. And consequently on https://crates.io/crates/cmake description. Perhaps even be printed aout as a warning message during any work of the crate - this crate is now subject to bit-rot, thus it seems ot be fare to announce it during work, for all the projects that "merely use" it for years, so they would know. Maybe this person/team has experience with BOTH CMake and Rust? |
Added commad option to simplify use of the tool. If the version is not installed it will installed it. Otherwise it will switch to the version.
rust-lang/cc-rs#663 (comment):
|
Ok this repository is now moved over, thanks! |
This is now under the maintainership of the rust-lang/crates-maintainers team. I am not a cmake expert, but I'm familiar enough with the tool to know how it works and help keep this maintained. I'm going to close this because there's nothing really left to do here. |
I've maintained this crate for quite some time now, but I don't think I really have the time/energy to maintain this any more. I personally only ever really barely understood CMake to begin with so I was also probably never the best maintainer of this crate either.
At this point, I'd be interested in finding someone else to take over ownership of this crate. Given a suitable maintainer I'd be happy to transfer the repository and crates.io crate as well.
This crate is pretty heavily depended on in the crate ecosystem, however, so I would prefer to not simply hand this over to the first volunteer. I would ideally prefer to hand it off to someone who's otherwise been involved in the Rust community for some time and I can trust to keep the crate well-maintained and suitable for the number of crates that depend on this crate.
The text was updated successfully, but these errors were encountered: