Add more maintainers

[XVilka]

It seems that you don't have time to maintain this repository. This crate is a "core" with a big count of downloads. Please consider adding more maintainers.
I sent two PRs modernizing the code:

• Update AppVeyor #159
• Rust 2018 transition. #158

[XVilka]

cc @dtolnay

[dtolnay]

Hi @XVilka, thanks for the PRs!

If you are interested in maintaining, I would recommend publishing your fork under a different crate name. I think the community would appreciate having a maintained fork; it doesn't have to be this repo.

[pksunkara]

We would use the fork in clap v2 if our security PR gets merged.

[CreepySkeleton]

@pksunkara No, we wouldn't. Switching to a fork would mean that Yaml types became different, exactly the reason we can't just bump it to yaml-rust 0.4.

I suggested to switch to a fork of yaml-rust clap 3.0 was because depending on something that's being maintained is way better than depending on something unmaintained.

@XVilka Are you looking forward to forking and maintaining the repo on you own? If not, I would go ahead and do that myself.

[XVilka]

@CreepySkeleton sadly no time for this, I am already scattered among many projects.

[louib]

@XVilka did you get any updates on this issue? I see that your 2 PRs ended up being merged.

[olalonde]

Is this project still maintained? @chyh1990 @XVilka or is there a maintained fork?

[XVilka]

@olalonde not that I am aware of. Maybe @dtolnay could suggest an alternative.

[dtolnay]

I am not aware of a maintained fork.

[davvid]

My (previously) maintained fork (yaml-rust-davvid` @ crates.io) has merged efforts with @Ethiraric's fork as of Ethiraric#2.

yaml-rust users should switch over to the actively maintained yaml-rust2 project ~ https://github.com/Ethiraric/yaml-rust2 (yaml-rust2 @ crates.io).

Upgrading from yaml-rust

Use this Cargo.toml snippet to use yaml-rust2 as a drop-in replacement for yaml-rust:

[dependencies]
yaml-rust = { version = "0.6", package = "yaml-rust2" }

This allows you to switch to yaml-rust2 while continuing to refer to yaml_rust in your code (e.g. use yaml_rust::YamlLoader; will continue to work so that no Rust code changes are required).