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

closes #197 WGs blog #198

Merged
merged 10 commits into from
Aug 5, 2024
5 changes: 5 additions & 0 deletions inst/WORDLIST.txt
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,7 @@ AUT
AVAL
AVALU
Balu
barchart
basel
bayer
bb
Expand Down Expand Up @@ -199,6 +200,7 @@ doesn
doi
Dony
dplyr
dropdown
dS
dt
DT
Expand All @@ -209,6 +211,7 @@ DTHDT
DTHFL
dtm
DTM
DVOST
dy
EBGM
eclinical
Expand Down Expand Up @@ -294,6 +297,7 @@ IJ
iml
Ingelheim
init
initializer
insightsengineering
introR
io
Expand Down Expand Up @@ -393,6 +397,7 @@ orgs
ouR
packageVersion
pageID
pak
param
PARAM
PARAMCD
Expand Down
73 changes: 73 additions & 0 deletions posts/2024-07-24_working__groups_.../appendix.R
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
suppressMessages(library(dplyr))
# markdown helpers --------------------------------------------------------

markdown_appendix <- function(name, content) {
paste(paste("##", name, "{.appendix}"), " ", content, sep = "\n")
}
markdown_link <- function(text, path) {
paste0("[", text, "](", path, ")")
}



# worker functions --------------------------------------------------------

insert_source <- function(repo_spec, name,
collection = "posts",
branch = "main",
host = "https://github.com",
text = "Source",
file_name) {
path <- paste(
host,
repo_spec,
"tree",
branch,
collection,
name,
file_name,
sep = "/"
)
return(markdown_link(text, path))
}

insert_timestamp <- function(tzone = Sys.timezone()) {
time <- lubridate::now(tzone = tzone)
stamp <- as.character(time, tz = tzone, usetz = TRUE)
return(stamp)
}

insert_lockfile <- function(repo_spec, name,
collection = "posts",
branch = "main",
host = "https://github.com",
text = "Session info") {
path <- path <- "https://pharmaverse.github.io/blog/session_info.html"

return(markdown_link(text, path))
}



# top level function ------------------------------------------------------

insert_appendix <- function(repo_spec, name, collection = "posts", file_name) {
appendices <- paste(
markdown_appendix(
name = "Last updated",
content = insert_timestamp()
),
" ",
markdown_appendix(
name = "Details",
content = paste(
insert_source(repo_spec, name, collection, file_name = file_name),
# get renv information,
insert_lockfile(repo_spec, name, collection),
sep = ", "
)
),
sep = "\n"
)
knitr::asis_output(appendices)
}
Binary file added posts/2024-07-24_working__groups_.../hands.PNG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
61 changes: 61 additions & 0 deletions posts/2024-07-24_working__groups_.../working__groups__updates.qmd
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
---
title: "Working Groups Updates"
author:
- name: pharmaverse council
description: "An update from pharmaverse council around how packages will get included in pharmaverse in future."
date: "2024-07-24"
# please do not use any non-default categories.
# You can find the default categories in the repository README.md
categories: [Community]
# feel free to change the image
image: "pharmaverse.PNG"

---

<!--------------- typical setup ----------------->

```{r setup, include=FALSE}
long_slug <- "2024-07-24_working__groups_..."
# renv::use(lockfile = "renv.lock")
```

<!--------------- post begins here ----------------->

Hi community,

We wanted to share with you an update from council discussions around our
pharmaverse working groups. Up until now, these have been the main gatekeepers
of which packages are included/excluded from the pharmaverse. Although open for
all to join, they ended up being quite lean and likely not representative of the
true depth of this community. So we’ve decided to open up the package decisions
to our full community in future via our Slack workspace, to make for a more
rossfarrugia marked this conversation as resolved.
Show resolved Hide resolved
inclusive community where everyone has a voice. This is now updated on our
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that this is now a democratic process, i.e. with voting on the packages or something? Or how exactly will the community decide to include the packages under the pharmaverse?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't want to make it overly prescriptive and rules-based as we should be able to evolve this as we learn from how it goes, but general thinking:

  • we share a new package request to pharmaverse slack and ask community to either thumbs up on GH issue, or add a comment if any concerns
  • if any concerns tag the requestor so they get a chance to respond and potentially allay the concern
  • if any comment is not resolved and even just 1 member of our community still has an issue with a package being included then we'll take it to the council to adjudicate and a transparent decision with rationale will be added to the GH issue

So everyone has a voice... even 1 single member could stop a package being included if they have a good enough justification! If we don't hear any concerns (and the package fits scope of pharmaverse and inclusion criteria) then we'll go ahead and add it.

If at any time in future a member of the community raises a concern then we could re-visit and see if any package should be removed.

I'll add a little bit more to the blog but don't want to go over the top either with explaining this.

FYI @bms63

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind adding this to the blog as well?
Or maybe hint towards this, if it is not quite clear yet?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@StefanThoma which bit exactly?

sorry, i added the following as a more concise summary of the above but happy to add some extra lines for whichever bits missed which you feel i should add

We don't want to be overly prescriptive with how this process will work as it
might evolve over time, but we'll be openly sharing any future package
applications to pharmaverse via our Slack and we welcome your input to help make
the call on which to accept/decline. Any individual from our community could
express support via a thumbs up on the GitHub issue or add a comment with any
concerns. If the requestor is unable to resolve any concerns, then ultimately
any contentious applications will be raised to the pharmaverse council to
adjudicate. The final decision and rationale will then always be documented on
the issue.

website – see the FAQ section on the homepage.
rossfarrugia marked this conversation as resolved.
Show resolved Hide resolved

![pharmaverse is ours!](hands.PNG){fig-align="center"}

Moving forwards, instead of working groups we will maintain some
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @rossfarrugia
I don't quite understand what the council is now responsible for, if not deciding on which packages go into the pharmaverse.
Is there a list of responsibilities?
What do you mean exactly with:

[...] we plan
to channel any working group type energy towards
PHUSE DVOST
given our strong partnership with PHUSE.

Does this mean that any ro most future work done by the council will be done to support DVOST or in consultation with DVOST?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@StefanThoma the council always delegated the responsibility of package inclusion to the WGs which we are now disbanding in favour of letting the community decide.

Council responsibilities are explained on a separate page: https://pharmaverse.org/contribute/council/

The council is fully committed to continue to grow and strengthen pharmaverse independent of any PHUSE support. The blog is therefore not changing anything in the council - it's about our WGs where we see more potential by utilising PHUSE DVOST and channeling energy that way instead of starting our own pharmaverse WGs to solve specific industry OS challenges. This was already happening really - as although we gave our WGs freedom to decide their own scope they all only focused on pharmaverse package inclusion, as any other wider OS topics already have industry WGs that could be joined and supported.

I'll add a note to the blog to reiterate that none of this impacts council.

[sub-communities](https://pharmaverse.org/contribute/wg/)
for particular connected networks such as our package maintainers, but we plan
to channel any working group type energy towards
[PHUSE DVOST](https://advance.phuse.global/pages/viewpage.action?pageId=327777)
given our strong partnership with PHUSE.

So, please do look out for future package applications to pharmaverse that will
be shared in our Slack general channel and we welcome your input to help make
the call on which to accept/decline – after all pharmaverse belongs to us all!

On behalf of the pharmaverse council


<!--------------- appendices go here ----------------->

```{r, echo=FALSE}
source("appendix.R")
insert_appendix(
repo_spec = "pharmaverse/blog",
name = long_slug,
# file_name should be the name of your file
file_name = list.files() %>% stringr::str_subset(".qmd") %>% first()
)
```
Loading