PHUSE End-to-End OS Collaboration Guidance

2023-11-06 @ PHUSE EU 2023

James Black & Mike Stackhouse

Links to the guidance and slides

phuse-org.github.io/E2E-OS-Guidance/

phuse-org.github.io/E2E-OS-Guidance/slides/eu23

Why is guidance needed?

  • pharmaverse brings a new open source R-backbone to clinical reporting
  • most packages are collaborations
  • there is a shift towards more sharing of useful code

New territory for statistical programmers!

  • Can we rely on OS code?
  • What if these collaborations fall apart?
  • Are we at risk?
  • How can we influence development?

Our aim

Provide guidance tackling the core questions raised by PHUSE members around:

  1. Using OS ⚙️
  2. Releasing OS code 🚀
  3. Collaborating and governing OS 🤝
  4. Why OS’ing our code is important! 📣

While technically legacy propriety code could be OS, and other languages are present like python, to align with the pharmaverse we decided to frame the guidance around R packages.

PHUSE E2E OS Guidance Working Group

Name Company
James Black
Mike Stackhouse
Anders Bilgrau, Tobias Krøgholt
Estella Dong, Karl Brand1
Keaven Anderson
Phil Bowsher, Ryan Johnson
Samir Parmar
1 Estella has since moved to Lausanne University Hospital

Pan-industry group formed under the PHUSE Data Visualisation & Open Source Technology

Contributors spanned 5 Pharma companies and 2 vendors, all with experience both releasing and maintaining OS codebases.

The guidance is available now!

Guidance document

phuse-org.github.io/E2E-OS-Guidance/

This is a living document, please be vocal and contribute!

If you see something in this presentation you want to comment on, improve or challenge…

  • Talk to a working group member
  • Make an issue
  • Make a PR on the document repository

Getting deeper into the guidance 🤿

A brief overview

An intro as to why OS and collaborate

We are already deeply leveraging OS, and by pooling resources on pre/post we can focus more on generating value

Every external contribution offers the chance to get back more than we invested

Is it ethically ok to not have key scientific logic done in an open source license free language?

The why

Project health, risks and licences

Examples are given on how to assess how engaged and active the community are, and what resources are available to find packages - like the pharmaverse and openstatsware

A discussion of the risks, and tools to assess risk and the impact of different licences

Using OS

Releasing, collaborating and governing OS

Understanding pre-competitive, competitive, and post-competitive IP.

Guidance on robust and safe release processes.

Examples of different governance models.

Releasing

Demo navigating the guidance

The guidance is a quarto book hosted on the Github PHUSE organisation.

phuse-org.github.io/E2E-OS-Guidance/ 🔗