Review scoringutils 2.0.0

[nikosbosse]

Once the major update that's currently in progress is done it would be great to have another package review like the ones done in #121 and #179.
@Bisaloo would you be up for another review once the update is finished?

[Bisaloo]

Hi @nikosbosse, yes, I can do this 👍

[seabbs]

I think we are getting close to this being done. Should we set a date for this that works for everyone?

[seabbs]

Hi all. We are really very close to this now! @jamesmbaazam @Bisaloo would you have time you do this in the next few weeks? As a reminder the idea is to use the Ropensci review template and do a pseudo submission review. Ideally issues would be split into really needs to be done now and scored with some kind of urgency (so we can slot them into future releases in a way that makes sense and doesn't drive Nikos to post too many memes).

[seabbs]

Ping!!

[Bisaloo]

I can do this over the next two weeks if that works for you.

[seabbs]

That would be really great!

[seabbs]

For awareness when looking these are the outstanding issues: https://github.com/epiforecasts/scoringutils/issues?q=is:issue%20is:open%20sort:updated-desc%20project:epiforecasts/6

[Bisaloo]

Can I follow the steps documented here: https://epiverse-trace.github.io/blueprints/code-review.html#full-package-review to open a PR with the full codebase as diff, so I can comment directly on specific portions of the code using GitHub PR review infrastructure?