Another major message from the survey and elsewhere is that Rust's ecosystem, while growing, is still immature (1 in 9 survey respondents mentioned this). Maturity is not something we can rush. But there are steps we can take across the ecosystem to help improve the quality and discoverability of crates, both of which will help increase the overall sense of maturity.
Ideas
Some avenues for quality improvement:
Provide stable, extensible test/bench frameworks.
Provide more push-button CI setup, e.g. have cargo new set up Travis/Appveyor.
[x] Crates.io now gives crate authors the ability to add badges indicating quality. Current badges include build status from TravisCI, Appveyor, and GitLab, code coverage from Codecov and Coveralls, and issue resolution time and number of open issues from IsItMaintained.com.
[ ] @shepmaster and @carols10cents have been working on, and will complete soon, a way to report build status of released versions of a crate on different platforms and different versions of Rust to crates.io
Point of contact
@carols10cents
Overview
Another major message from the survey and elsewhere is that Rust's ecosystem, while growing, is still immature (1 in 9 survey respondents mentioned this). Maturity is not something we can rush. But there are steps we can take across the ecosystem to help improve the quality and discoverability of crates, both of which will help increase the overall sense of maturity.
Ideas
Some avenues for quality improvement:
cargo new
set up Travis/Appveyor.Some avenues for discoverability improvement:
A number of ideas along these lines were discussed in the Rust Platform thread.
Status 2017-06-05
Completed
In progress
Planned - short term
cargo new
add a template README and template documentation