Skip to content

State of urlencoding #11

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

Closed
soerenmeier opened this issue May 12, 2021 · 3 comments
Closed

State of urlencoding #11

soerenmeier opened this issue May 12, 2021 · 3 comments

Comments

@soerenmeier
Copy link

I like this crate, it's easy and lightweight, however some issues and feature requests are still unanswered.
As i read in #9 @kornelski offered to help maintain this crate.
Can we expect urlencoding to be maintained and maybe get some new features like #5, #10 or kornelski#1 or should we move to another one?
There seems to be around 70 other crates depending on urlencoding: https://crates.io/crates/urlencoding/reverse_dependencies.
Even if this crate is small it should probably have an active/passiv maintainer.
@kornelski if your still maintaining this crate, maybe you could get access rights to this repository or create a new one, not a fork?
If you @bt and @kornelski don't wan't to maintain this crate anymore, I would volunteer.
As a last resort there's always the possibility to file unmaintained rustsec/advisory-db#173.

@kornelski hope you forgive me for not waiting longer than 20 days for a response in kornelski#1.

@kornelski
Copy link
Contributor

@soerenmeier
Copy link
Author

Yes i saw that, the problem is there you can't open issues.

@soerenmeier
Copy link
Author

Anyway, thanks for resolving this issue so quickly.

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

2 participants