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

Community Repository Scoring #64

Open
andrew opened this issue Jul 28, 2020 · 3 comments
Open

Community Repository Scoring #64

andrew opened this issue Jul 28, 2020 · 3 comments

Comments

@andrew
Copy link
Collaborator

andrew commented Jul 28, 2020

Now that we're starting to collect a good picture of all the open source projects across github that use IPFS in some way, it'll be useful to have some ways to rank/sort/filter them. I propose we have a "ecosystem score" that can be generated based on metrics and attributes of each repository.

Some basic ones to begin with:

  • Does it exist?!
  • Is it a fork?
  • Is it archived?
  • Is it owned by an org?
  • Is it published on a package manager?
  • How large is the repository?
  • How many issues?
  • How many pull requests?
  • How many contributors?
  • How many stars?
  • How many forks?
  • How many watchers?
  • How long has it existed?
  • When was it last updated?
  • When was it last committed to?
  • Does it use go-ipfs as a library?
  • Does it use js-ipfs as a library?
  • Does it use go-ipfs via docker?
  • Is it owned by an internal org?
  • Is it owned by a collab org?
  • Is it owned by a collab contributor?
  • Is it owned by a core contributor?
  • If it has published packages
    • How many downloads?
    • Do they have any dependent packages?
    • Do they have any dependent repos?
@andrew
Copy link
Collaborator Author

andrew commented Jul 29, 2020

First pass of this has been deployed and only showing repos on /collabs/repositories and /community/repositories if they have a score of 0 or greater (mostly filtering out old, archived and forked repos).

Next step is to boost by:

  • dependencies on internal packages
  • known owner
  • published packages

@andrew
Copy link
Collaborator Author

andrew commented Jul 30, 2020

I've made some tweaks to the score calculator to limit the impact of repos with very high numbers of stars, forks and watchers.

It also boosts projects with dependencies on any indexed package right now (collabs, community and internal), for this to be effective, need to index the dependencies of 20K community repos that haven't download the dependency data for yet.

One other thing I added in was boosting by number of tracked search hits, which does help although often finds superficial mentions of ipfs in readmes, so may need to tweak the weighting on different kinds of search results.

@andrew
Copy link
Collaborator Author

andrew commented Jul 30, 2020

You can also sort repo lists by score now: https://ipfs.ecosystem-dashboard.com/collabs/repositories?order=desc&sort=score

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

1 participant