UKTRE24: combined writeups

.github/workflows/build.yml

@@ -9,19 +9,21 @@ jobs:
     name: Lint
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-python@v4
-      - uses: pre-commit/[email protected]
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - uses: pre-commit/[email protected]
 
   build:
     name: Build docs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v5
         with:
-          python-version: "3.10"
+          python-version: "3.12"
           cache: pip
           cache-dependency-path: "**/requirements.txt"
 
@@ -36,4 +38,4 @@ jobs:
       - name: Link check
         run: |
           cd docs
-          make linkcheck
+          make SPHINXOPTS="--color --keep-going" linkcheck

docs/conf.py

@@ -60,9 +60,13 @@
     r"https://www.turing.ac.uk/.*",
     r"https://www.hpe.com/.*",
     r"https://csrc.nist.gov/.*",
-    # Currently down
+    r"https://digital.nhs.uk/services/secure-data-environment-service",
+    # Redirects to Confluence which seems to block the linkchecker
+    r"https://www.dundee.ac.uk/corporate-information/standard-operating-procedures-hic",
+    # Currently down or broken
     r"https://www.goldacrereview.org/",
     r"https://www.rd-alliance.org/trusted-research-environments-sensitive-data-fairness-closed-data-and-processes",
+    r"https://www.datashield.org/about/about-datashield-collated",
 ]
 
 # These pages use in-page JavaScript anchors which aren't seen by the link checker

docs/events/wg_workshops/2024-09-02-september-meeting/discussion-accelerating-digital-science.md

@@ -0,0 +1,15 @@
+# Breakout Discussion: Accelerating digital science
+
+## Summary of discussions from the breakout rooms.
+
+The discussions were positive, people were energised by the recognition of the importance of TREs and the emerging priority of federation. Logically this made sense to attendees.
+
+But federation is not the focus of TREs at present. The TREs are focussed on their own local problems: for example delivering siloed project specific facilities and data.
+
+Another key theme is the focus on TRE costs, each looking to monetise their data to offset their operations costs. This is often part of TREs strategies. Such business models are not supporting a move towards federation and the separation of Data Zone and Research Zone.
+
+The heterogeneous solution world causes complexity and as a result people cannot see how federation could work. The data is not standardised so how will that work? The systems are different technologies so how will they integrate? There is not a way of discovering data so who will be able to find and use it in a federated world?
+
+In addition, the governance processes are different and not trusted between TREs. No TRE has enough trust in any other part to enable the connection of the entities delivering data zone facilities with each other let alone one delivering Research Zone facilities to researchers. The stakeholder space was very full, and no incentives for governance to become involved and change.
+
+People could see all this complexity but felt they had no way of navigating it or seeing a way through. Many groups commented on how complicated a solution to this would have to be (which they could not see). Having a few projects to lead the way would be very helpful and help encourage the community that federation would come and be something to help make happen.