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

Rename to futures-openssl #12

Closed
cramertj opened this issue Apr 8, 2019 · 7 comments
Closed

Rename to futures-openssl #12

cramertj opened this issue Apr 8, 2019 · 7 comments

Comments

@cramertj
Copy link

cramertj commented Apr 8, 2019

This crate doesn't have any dependencies on the tokio runtime. @alexcrichton would you consider a rename for clarity? (it's tough to sort out at the moment which crates are usable on alternative executors and which are not, and keeping the naming straight would go a long way towards clearing this up)

@alexcrichton
Copy link
Collaborator

Certainly! I also don't mind transferring the repo to a new owner as I don't have time nowadays to maintain this. @cramertj I don't suppose you'd be interested would you?

(or maybe @sfackler you'd be ok moving into the openssl repo?)

@sfackler
Copy link
Collaborator

sfackler commented Apr 8, 2019

Yeah, I can move it into sfackler/rust-openssl.

@alexcrichton
Copy link
Collaborator

Ok thanks! I'm not personally too too interested in the history, so @sfackler want to import the crate and when that's done I'll archive this repository after updating docs to point to futures-openssl?

@cramertj
Copy link
Author

cramertj commented Apr 8, 2019

\o/ Thanks to both of you! :)

@sfackler
Copy link
Collaborator

sfackler commented Apr 9, 2019

I think it might make the most sense to do this when futures 0.3 is released. Seem reasonable @cramertj?

@cramertj
Copy link
Author

cramertj commented Apr 9, 2019

@sfackler I don't have a particular opinion about the release timeline-- seems fine to me either way!

@Darksonn
Copy link
Contributor

This issue seems outdated. The crate does depend on Tokio.

@Darksonn Darksonn closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2023
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

4 participants