-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Maintenance of xml-rs #221
Comments
I will start a process of approval to do anything with this project with my employer. Unfortunately, it will take some time - last time it took about 2.5-3 months. After this is done, I will be able to transfer ownership/add maintainers/etc. |
Since XML-rs is for the time being unmaintained[^1], and have been marked as such in RUSTSET[^2]. I have made ported the XML parsing to quick-xml. [^1]: netvl/xml-rs#221 [^2]: https://rustsec.org/advisories/RUSTSEC-2022-0048
Since XML-rs is for the time being unmaintained[^1], and have been marked as such in RUSTSET[^2]. I have made ported the XML parsing to quick-xml. [^1]: netvl/xml-rs#221 [^2]: https://rustsec.org/advisories/RUSTSEC-2022-0048
Since XML-rs is for the time being unmaintained[^1], and have been marked as such in RUSTSET[^2]. I have made ported the XML parsing to quick-xml. [^1]: netvl/xml-rs#221 [^2]: https://rustsec.org/advisories/RUSTSEC-2022-0048
Since XML-rs is for the time being unmaintained[^1], and have been marked as such in RUSTSET[^2]. I have made ported the XML parsing to quick-xml. [^1]: netvl/xml-rs#221 [^2]: https://rustsec.org/advisories/RUSTSEC-2022-0048
Hi @netvl ! Any news on this ? |
Hi @netvl, I would also like to help here, if needed. I work on Android as part of the team which supports Rust in Android. We use the crate in an Android component related to virtualization. So we'll like to help with the maintenance 😃 |
Hi @kornelski @untereiner @mgeisler |
Hi everyone, I have good news - I have just received an approval to go through with the maintenance transfer. I can do the necessary work any time. That being said, I'm not sure who I can transfer the crate to. Those who volunteered, is it all right for me to ask you to confirm your intention here? I personally don't really have a specific preference, but if you have experience with crate maintenance/have some crates that you actively maintain, that would be the best. Thank you! |
niiiice! :-) |
I'm still interested. |
`xml-rs` [is not maintained](https://rustsec.org/advisories/RUSTSEC-2022-0048) anymore. It is apparently [currently being](netvl/xml-rs#221 (comment)) transferred, but even if that happens (which is not a given), `xml-rs` still appears to have a large backlog of unresolved issues. Looks like it's time to switch. I found two crates that are actively maintained and can do SAX parsing: * [quick-xml](https://github.com/tafia/quick-xml). Clean codebase, no `unsafe`, lots of tests, lots of recent commits. Lots of dependencies as well, but fortunately all of them are optional except `memchr`, which I guess is OK. The API is similar to `xml-rs`, so migration is mostly straightforward. * [xmlparser](https://github.com/RazrFalcon/xmlparser). An absolute gem of a library: no dependencies at all, small and clean codebase, no `unsafe`. Unfortunately, the API doesn't group attributes together (the current geodata importer [relies](https://github.com/dfyz/osm-renderer/blob/87266a44464447be4951d4c244a7f85bc054e59c/src/geodata/importer.rs#L372) on that), and I don't want to make too invasive changes when switching. So, `quick-xml` it is (for now). By the way, it really lives up to its name: importing Serbia now takes **01:08** minutes on my laptop, while it used to take **02:51** minutes.
[Here](netvl/xml-rs#221) is the issues about xml-rs's maintenance.
I'm the new maintainer now. The new repo is at https://github.com/kornelski/xml-rs |
Big thanks for @kornelski to taking over the maintenance! |
It would be nice if you could transfer the repo, or at least give me access so that I can close issues. |
I'd like to help with the maintenance of this crate.
The text was updated successfully, but these errors were encountered: