Add a badge for crate authors to self-report their maintenance intentions

[carols10cents]

Part of RFC 1824, rust-lang/rust#41616.

Add to the badges table in Cargo.toml a maintenance key that crate authors could use to
self-report their maintenance intentions. The valid values would be along the
lines of the following, and would influence the ranking in the order they're
presented:

Actively developed

New features are being added and bugs are being fixed.

Passively maintained

There are no plans for new features, but the maintainer intends to respond to issues that get filed.

As-is

The crate is feature complete, the maintainer does not intend to continue working on it or providing support, but it works for the purposes it was designed for.

none

We display nothing. Since the maintainer has not chosen to specify their intentions, potential crate users will need to investigate on their own.

Experimental

The author wants to share it with the community but is not intending to meet anyone's particular use case.

Looking for maintainer

The current maintainer would like to transfer the crate to someone else.

Deprecated

The maintainer does not recommend using this crate (the description of the crate can describe why, there could be a better solution available or there could be problems with the crate that the author does not want to fix) Added from a suggestion in #549

These would be displayed as badges on lists of crates.

These levels would not have any time commitments attached to them-- maintainers
who would like to batch changes into releases every 6 months could report
"actively developed" just as much as mantainers who like to release every 6
weeks. This would need to be clearly communicated to set crate user
expectations properly.

This is also inherently a crate author's statement of current intentions, which
may get out of sync with the reality of the crate's maintenance over time.

Also need to update the documentation that currently lives in cargo's repo.

Please let me know if you have any questions, potential implementers!

[marti1125]

Hi @carols10cents!! I would like to work on this

[marti1125]

Hello @carols10cents I made list of tasks following the email

• Add another variant to the Badge enum https://github.com/rust-lang/crates.io/blob/master/src/badge.rs#L12
• Create that variant from the database in this match https://github.com/rust-lang/crates.io/blob/master/src/badge.rs#L48 no longer needed
• Add tests to https://github.com/rust-lang/crates.io/blob/master/src/tests/badge.rs
• Add an ember component like the other badge components in app/components
• Add a template in app/templates/components to display the badge
• Add JSON to the fixture used for frontend tests here https://github.com/rust-lang/crates.io/blob/master/mirage/fixtures/search.js#L23
• Add a frontend test that checks that the badge's HTML is rendered on the page around here https://github.com/rust-lang/crates.io/blob/master/tests/acceptance/search-test.js#L27
• Document how to specify the badge in Cargo.toml over in cargo's repo here: https://github.com/rust-lang/cargo/blob/master/src/doc/manifest.md#package-metadata

[vignesh-sankaran]

@carols10cents How do we want the maintenance intention badges to look like? Did we want it to look like the CI badges e.g. TravisCI?

[vignesh-sankaran]

We also need to:

• Fix up badge parsing in the crates.io backend. Cargo.toml requires the value to be a String, and cannot have the maintenance value as-is

EDIT: Turns out we don't need to do this since specifying the maintenance intention is done with snake-case :)

[vignesh-sankaran]

Could we close this issue @carols10cents? I think everything for this issue has been implemented.

[carols10cents]

Sounds good!