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

New Maintainers #663

Closed
alexcrichton opened this issue Mar 8, 2022 · 12 comments
Closed

New Maintainers #663

alexcrichton opened this issue Mar 8, 2022 · 12 comments

Comments

@alexcrichton
Copy link
Member

I'm reaching the end of my tenure of maintaining this crate. I can't keep up with the constant inundation of platforms into this crate and this has outgrown my own personal ability to manage. I feel nowadays like all I can do is rubber stamp big changes since I have no idea how the targets work, but at the same time it seems to be the case that code is just dumped in this crate and no one ever looks at it again until there's a bug. Personally, I can't keep up with that any more.

If someone would like to take over this crate please let me know. I realize though that this crate is very heavily depended on in the ecosystem, so I won't necessarily give this to the first person that shows up. I'll need to recognize you and you'll also need to understand the importance of this crate and its stability.

@sunface
Copy link

sunface commented Mar 9, 2022

I have an idea, maybe you could create an organization like cc-rs, move the repo there ,and let other maintainers join in, each of them will account for certain targets.

This project is very great and important, ,if it is just moved to another github user, probably nothing will changed and things won't getting better.

@Dylan-DPC
Copy link
Member

I can help with the organisation part. Have done so for a few crates already and being a rust team member, it might be easier

@m-ou-se
Copy link
Member

m-ou-se commented Mar 9, 2022

This crate is such an important part of the ecosystem, I think we should consider making it part of the rust-lang organisation. I'll make sure it gets discussed by the library team soon.

@Be-ing
Copy link
Contributor

Be-ing commented Mar 9, 2022

Thanks for recognizing your limits and asking for help @alexcrichton. ❤️

@spl
Copy link
Contributor

spl commented Mar 10, 2022

I worked on cc-rs a while back. At the time, I did have some ideas for improving it, but I didn't get around to finishing them. I wouldn't mind taking a shot at maintenance, shared or otherwise.

@aloucks
Copy link

aloucks commented Mar 11, 2022

@m-ou-se I think it's a great idea to incorporate this crate into the rust-lang organization. If for whatever reason that doesn't happen, it might make sense to create a new org to host both this crate and cmake-rs. It might also be worthwhile to host cmake-rs in the rust-lang org!

@dvc94ch
Copy link
Contributor

dvc94ch commented Mar 26, 2022

any updates on this?

@m-ou-se
Copy link
Member

m-ou-se commented May 7, 2022

We've discussed this in the Rust library team meeting this week, and we think it's best if cc and cmake are both moved to the rust-lang organisation. Currently, we won't have the bandwith to work on new features to these crates, but we will be able to review incoming PRs and make sure these crates stay maintained.

@alexcrichton If you're on board with this, can you transfer the repos to the rust-lang GitHub organisation, and invite @rust-lang-owner as owner to the crates on crates.io?

@alexcrichton
Copy link
Member Author

Sounds good to me, thanks @m-ou-se and the other libs/rust-lang members!

I believe though I'll need to transfer these repositories to someone else first who has permission to create repositories within the rust-lang organization, currently if I try to perform the transfer I get the error:

You don’t have the permission to create public repositories on rust-lang

Otherwise though I have invited the rust-lang-owner account to both cc and cmake

@alexcrichton
Copy link
Member Author

Ok this repository is now moved over, thanks!

@m-ou-se m-ou-se closed this as completed Jul 6, 2022
@Be-ing
Copy link
Contributor

Be-ing commented Oct 17, 2022

Unfortunately there haven't been any commits to the main branch since July and pull requests are piling up without response...

@thomcc
Copy link
Member

thomcc commented Oct 17, 2022

@Be-ing We're making a team for maintaining these crates: rust-lang/team#861.

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

9 participants