Marly Gotti

This is how the new site looks:

Hi @topepo, let me know if you think we should take this in a different direction.

I don't think this is a good idea. We should incorporate package versions. Doing so, we will get rid of issues with out-of-date packages.

Since the metrics are different by version of riskmetric, what do you think if we use: `release-v0.1.1`?. That would be ```devtools::install_github("pharmaR/riskmetric", ref = "release-v0.1.1")```

These are the metrics of v0.1.1: 1. "assess_news_current" 2. "assess_has_vignettes" 3. "assess_has_bug_reports_url" 4. "assess_last_30_bugs_status" 5. "assess_license" 6. "assess_export_help" 7. "assess_downloads_1yr" 8. "assess_has_website" 9. **"assess_r_cmd_check"** 10. **"assess_remote_checks"** 11. "assess_has_maintainer" 12. "assess_has_news"...

Ditto. It is better to assign weight of zero to these new metrics on another PR.

``` [1] "----------- pkg_assess -----------" # A tibble: 1 × 1 news_current 1 TRUE [1] "----------- pkg_score ------------" # A tibble: 1 × 1 news_current 1 1 [1] "----------------------------------------------------" [1]...

Need from `riskmetric`: - beautified metric name (instead of "news_current"), - beautified output text, e.g., "The package has 9 vignettes", - a way to handle metrics `bugs_status` and `export_help` for...

Decided to send email to `riskmetric` team.