closes #197 WGs blog

inst/WORDLIST.txt

@@ -95,6 +95,7 @@ AUT
 AVAL
 AVALU
 Balu
+barchart
 basel
 bayer
 bb
@@ -200,6 +201,7 @@ doesn
 doi
 Dony
 dplyr
+dropdown
 dS
 dt
 DT
@@ -210,6 +212,7 @@ DTHDT
 DTHFL
 dtm
 DTM
+DVOST
 dy
 EBGM
 eclinical
@@ -295,6 +298,7 @@ IJ
 iml
 Ingelheim
 init
+initializer
 insightsengineering
 introR
 io
@@ -394,6 +398,7 @@ orgs
 ouR
 packageVersion
 pageID
+pak
 param
 PARAM
 PARAMCD
@@ -837,3 +842,9 @@ pak
 Pavel
 shinyApp
 sparkline
+strived
+accountabilities
+curation
+requestor
+pageId
+viewpage

posts/2024-07-24_working__groups_.../appendix.R

@@ -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)
+}

posts/2024-07-24_working__groups_.../working__groups__updates.qmd

@@ -0,0 +1,74 @@
+---
+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 decision-holders 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](https://pharmaverse.slack.com/),
+to make for a more inclusive community where everyone has a voice. This is now
+updated on our website – see the FAQ section on the [homepage](https://pharmaverse.org/).
+
+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.
+
+![pharmaverse belongs to us all!](hands.PNG){fig-align="center"}
+
+Moving forwards, instead of working groups we will maintain some
+[sub-communities](https://pharmaverse.org/contribute/wg/)
+for particular connected networks such as our package maintainers, or those
+teams powering pharmaverse-specifics such as our blog and website.
+Additionally, for any wider open source industry challenges we would recommend
+any would-be contributors towards
+[PHUSE DVOST](https://advance.phuse.global/pages/viewpage.action?pageId=327777),
+given our strong and continued partnership with PHUSE.
+
+Note that the above does not impact the role of the pharmaverse council - all
+our accountabilities are still explained [here](https://pharmaverse.org/contribute/council/).
+Now only we delegate the responsibility for "curation" of pharmaverse packages
+to our entire community.
+
+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()
+)
+```