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
So, to further support the use case when orgs only rely more on specific metrics and package exploration for their review process, we should really consider de-emphasizing the risk score. After all, 30% of those who responded at our last all-hands meeting, said they don't even care about the risk score.
Proposal: we give users the option in the config file (and perhaps on the Admin Tools tab) to turn all displays of risk score off. I think we could continue to store the scores in the database in case they decide to turn them back "on" later. Right now, the risk score shows up in the following places:
Package Control Panel
Upload pkg summary
Dependency tab
We should disable the metric weights module and the mechanism that adds comments on the previous and current scores whenever the weights change. Note, we'll still need to give users the option to download the database on this tab.
The checkbox for risk score on the build report tab
Both decision automation modules
Database tab
Assessment Criteria Tab
The text was updated successfully, but these errors were encountered:
So, to further support the use case when orgs only rely more on specific metrics and package exploration for their review process, we should really consider de-emphasizing the risk score. After all, 30% of those who responded at our last all-hands meeting, said they don't even care about the risk score.
Proposal: we give users the option in the config file (and perhaps on the Admin Tools tab) to turn all displays of risk score off. I think we could continue to store the scores in the database in case they decide to turn them back "on" later. Right now, the risk score shows up in the following places:
The text was updated successfully, but these errors were encountered: