-
Notifications
You must be signed in to change notification settings - Fork 0
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
Penalty for not using Github PRs is massive #3
Comments
Note that repo scores don't affect the order of results at all.
That will make the factors useless as lengthy inactivity detectors.
|
The exponential penalty kills packages that have only 1 author. As I'm sole maintainer of some of my packages I never need to do PRs and I don't close issues, but I do still add new code, fix bugs and make new releases.
It's understandable that there should be some negative score for having bus factor == 1, but if someone doesn't embrace GitHub for issues and PRs their package will be ranked down into oblivion regardless of any other merits.
Suggested fixes:
instead of
months_since_last_pr_merged
, usemin(months_since_last_pr_merged, months_since_last_release)
(ormonths_since_last_push
), so that GitHub usage is irrelevant as long as the package is getting new releases.cap github inactivity penalty not to exceed sum of all positive scores from other github factors, e.g.
score = max(0, subscribers + contributors_up_to_100/*etc*/ - months_since_last_pr_merged/*etc*/)
.the exponential could be smaller for packages with version >= 1.0, assuming the package may stable and doesn't need regular changes and fixes.
The text was updated successfully, but these errors were encountered: