How repository score should be computed ?

[callicles]

Something to start with.

Rules

• Score is base on some determined criterias evaluted by other users.
• Score also be influenced by some key automatic metrics
• A user cannot vote for a repository he contributes to.

Scoring criterias

Score things from 1 to 5.

• Documentation
• Code Quality
• Support

Automatic Criterias

• Community Size

[callicles]

Another thing to take into account that we have started to evoke is temporality. For a given repository quality can improve over time. Long past ratings should not matter.

We could compute the score only for a given period of time like 6 months of rating before the last commit so that the score is relevant to the current codebase.

[sheymann]

How about using a linear function that progressively decreases the importance of the reviews? This may be balanced with the number of commits per week, as some repositories may almost not evolve during 6 months (e.g. sigma.js).

[callicles]

That's why I was thinking before the last commit.

I am not sure a progressive deprecation would be the best. The evolution of a codebase can be constant but the user experience is also relative to the release. The code base is relative to a given release and constant.

If release are available, we should rate project on each release no ? else we could use linear deprecation.

[callicles]

Another thing that would be cool to take into account is the time since the last commit, the distribution of commits between contributors and the fact that the main contributors are active or not.

ex:
https://github.com/mgcrea/angular-strap/graphs/contributors
https://github.com/angular-ui/bootstrap/graphs/contributors

[callicles]

@pocman What do you think of this ? Could we try adapt it for our notation system ? The guy has a point.

[pocman]

C'est là tout l'intérêt de la distribution de la moyen au lieu de la
moyenne en elle même.
Les exemples donnés sont pour des cas binaires. Pour les notes, le mieux
est de comparer les distributions.
Le 10 juil. 2015 09:38, "Nicolas Joseph" notifications@github.com a
écrit :

@pocman https://github.com/pocman What do you think of this
http://www.evanmiller.org/how-not-to-sort-by-average-rating.html ?
Could we try adapt it for our notation system ? The guy has a point.

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[callicles]

Something we could take under consideration
http://mtov.github.io/Truck-Factor/
https://news.ycombinator.com/item?id=9874503