-
Notifications
You must be signed in to change notification settings - Fork 10
Moving the usb-device
and usbd-serial
crates to this organization
#15
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
Comments
Your explanation fits right into the mission of this org so I would welcome these crates. Them being platform-agnostic or not does not matter. |
Sounds good! How would I go about transferring the repositories? AFAIK I can't transfer to an organization I'm not a member of. Also if you could mention which team needs access on crates.io, I can add it. |
Alright. You can transfer them to me and I will immediately transfer them here. |
There you go! When trying to add the team (
Is it a permissions issue, or am I doing it wrong? |
Alright the transfer is done now, thanks! About the team permission issue I've had it in the past but cannot remember how I fixed it. The team is visible and crates.io has OAuth permission through me and no further restrictions. |
I've sent you invites, let's see if that helps. |
Alright, that worked. I could invite the team and although it said only that it sent an invitation, the team appears as an owner in crates.io already. |
Hi,
I'm not currently interested in maintaining these crates, but it seems they're getting plenty of use which isn't an ideal combination. Other people have expressed interest in helping out with maintenance, but for that it'd be best if the code wasn't just under my personal GitHub account, but under an org. Would this organization be the best fit for a platform agnostic crate?
The reason I'm not interested in maintaining these at the moment is that they were my first real Rust project and I've learned a lot since, and my opinion is that they're due for a rewrite, which I want to do eventually. Before that however I want to see if async/await becomes the main way of doings things on embedded before changing the entire API, but that's still some time away, waiting for more issues to be resolved in Rust itself.
If you'd be willing to adopt these crates, I'd still like to retain commit access, how would we go about arranging that?
Thanks!
/ Matti
The text was updated successfully, but these errors were encountered: