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
@wiligl@borgmaan@yannfeat@dgkf I need your help to assess the cost of running our pilot (see before last section in the gDoc). Please provide your input by end of day, or at the latest by March 24th.
On Monday, I plan to share our proposal to different stakeholders (ie. RVH Exec Committee) and submit it on April 1st (deadline).
Thanks
In "The Problem" - this seems to be speaking to an audience that comes from a regulatory background. I'd suggest a slight rephrasing of the opening questions. Since reviewers are probably unfamiliar with the healthcare specific needs and history, I rewrote these statements to be more explanatory than prompting.
Users of R in the pharmaceutical industry are often faced with:
• consistently and reproducibly assessing software quality
• evaluating quality for each piece of software - a problem exacerbated by a distributed R package ecosystem
• clearly recording the derivation of quality criteria and decisions in preparation for audits
• aligning with and showing evidence of industry expectations for software quality
I would also mention the related R-Consortium projects (R Consortium Repos Working Group, R-Hub (containers and repos), R-Universe) and emphasize our efforts to integrate with them.
Draft:
https://docs.google.com/document/d/14H27NxvzGxaaGgK8rFgZMtXAl6-sG2E7mJXr43WzpMo/edit?usp=sharing
The text was updated successfully, but these errors were encountered: