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

Maintainership transfer #102

Closed
5 of 7 tasks
Amanieu opened this issue Apr 22, 2020 · 15 comments
Closed
5 of 7 tasks

Maintainership transfer #102

Amanieu opened this issue Apr 22, 2020 · 15 comments

Comments

@Amanieu
Copy link

Amanieu commented Apr 22, 2020

This crate is no longer maintained, but @jclulow and @pfmooney have offered to take over maintenance as part of the @deprecrated organization.

Pinging @rust-lang/libs for approval:

@BurntSushi
Copy link

I don't have access to tick my checkbox, but SGTM!

@bluejekyll
Copy link
Contributor

I just want to make sure people know that folks moved over to using the maintained and better design (IMO) of https://github.com/alexcrichton/socket2-rs

@Amanieu
Copy link
Author

Amanieu commented Apr 22, 2020

Yes but apparently this crate is still widely used in the ecosystem, which means that there is value is continuing to maintain it, e.g. to add support for new platforms (#101).

@jclulow
Copy link
Member

jclulow commented Apr 22, 2020

We are happy to put whatever signage up about deprecation and what you should do instead that folks think is wise!

@bluejekyll
Copy link
Contributor

bluejekyll commented Apr 22, 2020

To me for such a low level library, I would hope that we could convince folks to migrate, or maybe there’s a way to create an API shim that calls through to socket2.

Otherwise we’ll end up with both in a lot of networking code.

@SimonSapin
Copy link
Contributor

SGTM, thanks to the new maintainers for volunteering!

@pietroalbini
Copy link

I'll wait a couple of days to see if @withoutboats or @LukasKalbertodt have any opinion on this, then I'll transfer the repo.

@pfmooney
Copy link
Member

Is it acceptable to move forward on this with the two abstentions?

@pietroalbini
Copy link

@pfmooney @jclulow could you add me to the @deprecrated organization with permissions to create repositories? I'll then transfer the repository and leave that org :)

@pietroalbini
Copy link

Transferred the repository!

@pfmooney
Copy link
Member

Transferred the repository!

Thanks! I've created the crates team under the deprecrated organization. I assume push rights on crates.io can be assigned to a team like that?

@pfmooney
Copy link
Member

pfmooney commented May 1, 2020

If someone can add @jclulow or I to the crate on crates.io, we can do the rest. Thanks

@sfackler
Copy link
Contributor

sfackler commented May 1, 2020

I believe @alexcrichton is the only person who has the ability to do that - people who are only owners via team membership can't add owners.

@alexcrichton
Copy link
Contributor

Ok I've invited @pfmooney to the crate on crates.io

@pfmooney
Copy link
Member

pfmooney commented May 1, 2020

Ok I've invited @pfmooney to the crate on crates.io

Accepted. Thanks!

@pfmooney pfmooney closed this as completed May 1, 2020
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

9 participants