Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback on minutes from last month #2

Open
epijim opened this issue Nov 29, 2022 · 2 comments
Open

Feedback on minutes from last month #2

epijim opened this issue Nov 29, 2022 · 2 comments

Comments

@epijim
Copy link

epijim commented Nov 29, 2022

There was a question about how the GitHub repositories are organized under the R-universe project. Note that the package repos may be reached via https://pharmaverse.r-universe.dev/ui#packages or through https://github.com/pharmaverse/. SK said that he would confer with the pharmaverse council and provide more information about the project at a later time.

@joseph-rickert for:

There was a question about how the GitHub repositories are organized under the R-universe project

Github repos aren't organised under any banner by design - e.g. they can have a repo in the pharmaverse org, but right now that's more limited to a handful of repos. Some are developed in company owned repos (e.g. Roche's insightsengineering and Roche orgs, as well as Atorus' org, Merck's etc).

Right now we just track the packages that are part of the pharmaverse in r-universe as a convenience thing (e.g. if testing). I would assume no company would depend on r-universe (or CRAN) as we all have internal cran-like mirrors we distribute from internally (e.g. Roche uses RSPM). The FDA has also accepted OS packages from github repos (although may prefer CRAN).

@epijim
Copy link
Author

epijim commented Nov 29, 2022

Note Doug Kehlkoff and the Validation Hub work may also make the r-universe publishing redundant in a year or two.

@joseph-rickert
Copy link
Contributor

Thank you @epijim. This makes things much more clear with regards to access and organization.
However, I am still not clear about the purpose of the pharmaverse, the practical benefits of branding a package as part of the pharmaverse, and about guarantees that are conferred on packages because they are part of the pharmaverse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants