Help us understand how you evaluate crates so we can make crates.io better!


#1

@shepmaster and I are doing this little user research survey to inform an RFC we’re working on. It should take about 15 min of your time. Thank you for your help!!

Take the survey!


Six Easy Ways to Make Your Crate Awesome
RFC: Ranking crates on crates.io
#2

The information I want on crates.io would be irrelevant for those crates, but is hugely useful in general. In particular whether the crate supports Windows and whether it requires any external libraries (other than system libraries like windows api).


#3

I can’t +1 this enough. As a new Rust developer who started working with Rust using Piston on Windows, it was challenging at first wading through examples and Github pages to find out that I needed to install MSYS2 (for gcc) and at the time had to figure out I needed to add a C library FreeType to link in (that dependency is now thankfully gone).

Also, knowing whether a crate supports nightly and/or stable Rust is important (and a badge for docs/GitHub page example). Perhaps even giving the option to list what versions of stable Rust it supports.

While I’m not sure they are exactly the best system, perhaps Rust could look at the PyPI trove classifiers for some inspiration.

A few I’d like to see in some way:

Development Status :: ...
Operating System :: ...
Programming Language :: Rust :: Stable
Programming Language :: Rust :: Stable :: 1.13.0
Programming Language :: Rust :: Nightly

Regex 0.2 is out (precursor to 1.0)
#4

I’m definitely getting inspiration from PyPi :slight_smile:


#5

:+1:

If the package uses travis, the build status combined with information from .travis.yml works for answering this. It would of course be great if crates.io could check and display it.