What should be included in val.repo?

[saenzile]

@dgkf @llrs @yannfeat let's have a discussion here

[llrs-roche]

Introduction

val.repo currently includes only the repository itself:

src/contrib/PACKAGES
src/contrib/Meta/

But to update PACKAGES files and the reports on src/contrib/Meta we need some functions to generate metrics and reports on the the github actions.

Scope

We are considering another repository because then it will make easier to merge and reuse the tools.
It will make it easier to know what is the purpose of each task so a git repository doesn't have two purposes: repository and github actions/merger/ sync work, ... (?).
The scope of the package would be to have all the functions to generate a validated CRAN-like R repository with reports and metrics.

For example:

• there are requests to merge/have different scores
• to make it easier to update specific packages (so updated packages can be added).

Name

Name of the potential new repository:

• val.setup
• val.blueprints
• val.workflow

[yannfeat]

Thank you for opening this. I am in favor of having things split.

In the past, I had trouble getting onboarded to pharmapkgs because it was trying to do too many things at once. Therefore, I would like to stay true to the modular restructuring initiated by @saenzile, which has helped me understand the purpose of each component quickly. This experience shows that having small, focused repositories with clear goals makes it easier for new contributors to get involved without being overwhelmed by complexity.

This kind of separation would also benefit companies that might want to reuse the tooling (e.g., the pipeline function of pharmapkgs for use with internal CI/CD tools) independently of the repository itself. Keeping those utilities in a dedicated repo (I like val.setup for the name) makes them more discoverable and easier to integrate elsewhere.

Overall, this approach improves clarity, reusability, and collaboration. Happy to support the move!