You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the results file reports the final risk index, but not the breakdown of how the score was derived. You can figure it out from the other data, but it might be better to report the specific values as well.
This could be reported as a bunch of new columns, one for each value. That would be easy to import into SQL and search on, for example. If that's a pain, it could be reported in the form "0+2+0+1+1..."; each of the values could be in a specific order.
This is inspired from Nathan Willis's article in LWN.net; see https://lwn.net/Articles/651268/ which says, "Regrettably, the raw numbers that make up each package's score do not appear to be available. It would have been interesting to see the exact point values assigned for number of contributors, for example."
The text was updated successfully, but these errors were encountered:
Currently the results file reports the final risk index, but not the breakdown of how the score was derived. You can figure it out from the other data, but it might be better to report the specific values as well.
This could be reported as a bunch of new columns, one for each value. That would be easy to import into SQL and search on, for example. If that's a pain, it could be reported in the form "0+2+0+1+1..."; each of the values could be in a specific order.
This is inspired from Nathan Willis's article in LWN.net; see https://lwn.net/Articles/651268/ which says, "Regrettably, the raw numbers that make up each package's score do not appear to be available. It would have been interesting to see the exact point values assigned for number of contributors, for example."
The text was updated successfully, but these errors were encountered: