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

Transfering ownership #34

Open
Ogeon opened this issue Mar 17, 2024 · 4 comments
Open

Transfering ownership #34

Ogeon opened this issue Mar 17, 2024 · 4 comments

Comments

@Ogeon
Copy link
Collaborator

Ogeon commented Mar 17, 2024

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.

@Razican
Copy link
Collaborator

Razican commented Mar 17, 2024

This is fine by me :) makes sense that someone with more time to spend on this works on it

@Ogeon
Copy link
Collaborator Author

Ogeon commented Mar 17, 2024

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.

@Ogeon
Copy link
Collaborator Author

Ogeon commented Mar 23, 2024

@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 MIT OR Apache-2.0 dual license in the future. You may need to check with other contributors first. I'm not a lawyer and don't know what the intricacies may be.

@mwallner
Copy link
Owner

Hey @Ogeon - big thanks to you and everyone who's contributed to rust-wiringpi so far!
We strive to bring back WiringPi as the go-to lib for system level and high-perf development, so having a convenient rust-wrapper is a must 😄

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 🙂

👋

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

3 participants