-
Notifications
You must be signed in to change notification settings - Fork 112
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
Maintenance status? #173
Comments
rustc switched to https://github.com/tikv/jemallocator according to https://www.reddit.com/r/rust/comments/s18136/maintenance_status_jemallocator/ |
I've still got access to the crates.io crate but I haven't maintained this crate in quite some time. I think it's ideally worthwhile to keep this crate going, especially because the tikv-jemallocator crate is an active fork. I reached out to @BusyJay (the crates.io-owner of tikv-jemallocator) and they're willing to take over the @gnzlbg if you don't have any objections (or if I don't hear from you for a week or so which is also ok!) my plan is to add @BusyJay to the |
Hi all, hi @gnzlbg,
thank you for this great projects! Correct me if I'm wrong, but this projects seems unmaintainened unfortunately. Some trivial PRs are pending (e.g. #152, #164, #161, #172), the published versions are not tagged in this repo and contain questionable content, and some great work has not been reviewed.
@BusyJay created a fork of this project for his use case and looking at https://github.com/gnzlbg/jemallocator/network there seems to be a few more.
I wonder if we find a few people who have the skills and time to maintain this project. Ideally it would be possible under the existing crate name jemallocator, which @sfackler and @alexcrichton seem to have access to.
I'd love to hear from @gnzlbg but looking at his GitHub activity, I'm not sure we'll reach him.
The text was updated successfully, but these errors were encountered: