-
Notifications
You must be signed in to change notification settings - Fork 77
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 #52
Comments
@jheyens Thanks for your work on |
This sounds really great! I am going to write you an email for further steps edit: Done. |
@10XGenomics has volunteered to take over this library. The new project home (due to having the wrong github permissions) will be at https://github.com/10XGenomics/lz4-rs |
Can you put notion to README.md that project at https://github.com/bozaro/lz4-rs not maintained anymore and new address https://github.com/10XGenomics/lz4-rs ? It's was hard to find such info. |
@pmarks @10XGenomics Out of interest, why issue section not available in your fork? |
@fanatid thanks - I noted the move in the README on 10xGenomics. Wea re trying to transfer this repo to that organization which will preserve the issue history. |
Dear users,
I am sorry I didn't live up to the promises I made in some of the issues and pull requests. My intention was not to deceive you, but to actually continue working on this library and to let this be my small contribution to the Rust community.
However, I don't want to make any more empty promises, I won't fulfill, so I am now looking for a new maintainer for this library.
My plan forward would be to give contributor access to a volunteer, but I just noticed, I can't even do that, since I am not a maintainer of this Github project. If someone volunteers, we should migrate to another namespace.
Regarding the crates.io access rights, I would suggest doing the updates myself for a transitioning period to ensure the new maintainer does not have any malicious intentions.
Cheers,
Jens
The text was updated successfully, but these errors were encountered: