You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #2436 and #2437, we want to offer crate owners the option to add a badge to their README files that reflects the current maintenance status.
We currently use https://shields.io/ to display the maintenance status badge and the service seems stable enough for now to keep using it. I would propose adding an API endpoint that reads the maintenance status for the selected crate from the API, and then redirects to the corresponding shields.io URL like:
Remove some badges documentation.
Badges have been removed from crates.io, so this updates the documentation. I don't think Cargo should manage a schema for the different services, and since crates.io isn't using these, I think it is mostly a dead feature. I left the `maintenance` field, because that might still have some meaning in the future.
More details:
* Removal from crates.io: rust-lang/crates.io#2436rust-lang/crates.io#2440
* Solicited feedback for this change: https://internals.rust-lang.org/t/cargo-badges/12982
* Potential future support of `maintenance` status: rust-lang/crates.io#2437rust-lang/crates.io#2438rust-lang/crates.io#2439. It's not clear, if crates.io manages the status in the database, the motivation for putting it in `Cargo.toml` is probably pretty small.
Related to #2436 and #2437, we want to offer crate owners the option to add a badge to their README files that reflects the current maintenance status.
We currently use https://shields.io/ to display the maintenance status badge and the service seems stable enough for now to keep using it. I would propose adding an API endpoint that reads the maintenance status for the selected crate from the API, and then redirects to the corresponding shields.io URL like:
https://img.shields.io/badge/maintenance-actively--developed-brightgreen.svg
The text was updated successfully, but these errors were encountered: