-
Notifications
You must be signed in to change notification settings - Fork 17
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
Transfering ownership #34
Comments
This is fine by me :) makes sense that someone with more time to spend on this works on it |
I thought the same, and I see no reason to keep sitting on the name on crates.io, either. 🙂 Let me just figure out the practicalities, then, and I will transfer it to @mwallner sometime during the following week. |
@mwallner, you should have received both an invite to the crates.io crate and a request for this repository. Once the transfer is done, you should probably want to edit the Cargo.toml file to have up-to-date info. The same with any links in the README.md file. You are free to refer to me for attribution and as part of the crate's history, but I hand over the full responsibility for any further development and for releasing new versions to you and @WiringPi. As mentioned, I do not intend to resume maintenance. All of my own contributions to this repository under the MIT license may be re-licensed under the more common and permissive |
Hey @Ogeon - big thanks to you and everyone who's contributed to rust-wiringpi so far! If you're interested, keep an eye out for a new release in the next 2-3 weeks, we're in the process of fixing ISR with the latest debian/ubuntu kernels - as soon as the release is out I'm going to start working on getting rust-wiringpi updated 🙂 👋 |
Long time, no see!
Earlier this week, I received an email from @mwallner (I hope you don't mind that I make this an open conversation) asking if I would like to transfer this repository to the @WiringPi organization. Like I mentioned in my response, I'm willing to do this, but I'm not going to resume development, myself. They would get it in its current state. This would also come with a transfer of crates.io ownership.
I decided to move the conversation here to give @Razican a chance to have a say. Your name is also on this, so I would like to know if you think this is a good idea before doing anything.
The text was updated successfully, but these errors were encountered: