Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

Abandoned/ maintenance repo alerts #1560

Open
oprogramador opened this issue May 1, 2019 · 1 comment
Open

Abandoned/ maintenance repo alerts #1560

oprogramador opened this issue May 1, 2019 · 1 comment

Comments

@oprogramador
Copy link

oprogramador commented May 1, 2019

Many people check whether a repo is still maintened by the date of the last commit but it's not the best way because there can be a simple library which is already finished so it doesn't need any new commits. However if somebody reports a bug, a performance issue or a feature request it would be good to resolve such issues or at least answer them.

We can calculate a maintanability coefficient:

coefficient = percentage_of_answered_prs_and_issues_withing_last_2_years + percentage_of_answered_prs_and_issues_withing_last_1_year + percentage_of_answered_prs_and_issues_withing_last_6_months + percentage_of_answered_prs_and_issues_withing_last_3_months

However the PRs and issues opened within the last 7 days are excluded.

I would like info at the main repo page (with the coefficient value):

  • red abandoned if coefficient equals 0
  • orange almost abandoned if coefficient is more than 0 and not more than 20
  • amber very poorly maintaned if coefficient is more than 20 and not more than 50
  • gold poorly maintained if coefficient is more than 50 and not more than 100
  • yellow below average maintained if coefficient is more than 100 and not more than 160
  • chartreuse yellow average maintained if coefficient is more than 160 and nor more than 240
  • chartruese green above average maintained if coefficient is more than 240 and not more than 300
  • lime well maintained if coefficient is more than 300 and not more than 350
  • green very well maintained if coefficient is more than 350 but nor more than 380
  • azure wonderfully maintained if coefficient is more than 380 but less than 400
  • blue perfectly maintained if coefficient equals 400
@TPS
Copy link
Collaborator

TPS commented May 4, 2019

#562 seems like it could use an implementation of this, even if only to see whether it'd be useful in production. It does seem elaborate.…

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

No branches or pull requests

2 participants