Beman library maturity model: express status using an extra badge (additional to LIBRARY_STATUS rule)

[neatudarius]

• Add SVG badges
• Update LIBRARY_STATUS rule to also indicate usage or badges

Expected badges:

Expected usage example:

[neatudarius]

@JeffGarland , can you please help here with a quick decision it is related to style?

Context:

1. We have a poll which says we want badges instead of logos. And we want badges to be present in each repo.
2. I was wondering if we can remove the line with Status: ... and avoid duplication. Merge this information with a generic mention near the badge.

I'm fine with either option:
V1: put badges and keep Status: ... line
V2: put badges and remote Status: ... line

[JeffGarland]

and avoid duplication

We should do both, because it isn't useless duplication -- it's two different ways of communicating. Good human factors design for visual displays will often provide both text and an icon with color. The duplication is in recognition that some significant portion of the population has different color perception (see also colorblindness -- which really refers to a range of vision differences among people). In this group the text will often be more effective. That said, a shape/color can confer information quickly without the need to read. So both modes do have a value.

[neatudarius]

and avoid duplication

We should do both, because it isn't useless duplication -- it's two different ways of communicating. Good human factors design for visual displays will often provide both text and an icon with color. The duplication is in recognition that some significant portion of the population has different color perception (see also colorblindness -- which really refers to a range of vision differences among people). In this group the text will often be more effective. That said, a shape/color can confer information quickly without the need to read. So both modes do have a value.

@JeffGarland , done. Thanks!

Check latest status:

Library PR example: bemanproject/exemplar#89