Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguishing between dead and stable packages #5

Open
kornelski opened this issue Jan 28, 2017 · 2 comments
Open

Distinguishing between dead and stable packages #5

kornelski opened this issue Jan 28, 2017 · 2 comments

Comments

@kornelski
Copy link

kornelski commented Jan 28, 2017

There are some kinds of packages that don't require active maintenance:

  • very small single-purpose packages that can be finished

  • *-sys packages/FFI bindings. They may not need to change at all, or may only require updating once in a while when the API of the underlying library/system changes.

  • Mature projects that don't have much churn, because they're stable and maintain high degree of backwards compatibility (although Rust probably doesn't have these yet :)

Related to #3

@kornelski
Copy link
Author

One factor could be looking at usage of the package — whether it's growing or declining. If it looks inactive, but new users are still adopting it, then it's probably stable. If it's inactive and loses users, then it's dead.

A simpler solution may be to have slightly different ranking for crates named *-sys and with versions past 1.0.

@MoSal
Copy link
Contributor

MoSal commented Jan 28, 2017

Note that I'm aware of this caveat. It's mentioned in the README:

  • The inactivity factors bias against complete, or maintenance-only crates. This will become more relevant when the echo system matures.

Detecting this with non-reliable magic is a no-no for me. Instead, I think users should be conscious
about what kind of crate they are looking for. And maybe use -p, --sort-positive when they deem it fit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants