From d6e3ed0287b275bc36c6677086e2d6d6852b20d9 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 31 Jan 2024 17:07:48 +0000 Subject: [PATCH 01/42] Create progress_report.md --- Reports/progress_report.md | 105 +++++++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+) create mode 100644 Reports/progress_report.md diff --git a/Reports/progress_report.md b/Reports/progress_report.md new file mode 100644 index 0000000..8cfd52d --- /dev/null +++ b/Reports/progress_report.md @@ -0,0 +1,105 @@ +# Data Safe Haven project report + +This document contains a summary of progress across all stories in the [project roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1). +It maps stories according to the (main) pillar and priority they contribute to. + +## Infrastructure as code +Running projects working with sensitive data safely +Running cutting edge data science projects effectively + + +### Manage codebase releases and testing +https://github.com/alan-turing-institute/data-safe-haven-team/issues/50 + +Contributes to: +- Running projects working with sensitive data safely +- Running cutting edge data science projects effectively + +#### Goal +Support for deployments of the Data Safe Haven at Turing and beyond + +#### Progress +- Pen testing done: little found +- Penetration tested arranged and will be done in September +- Preparation for release v4.1.0: Deployment of different SRE variants, Security checklist +- Reviewing v4.1.0: No significant problems is deployment logs, Problems found in security checklist relating to MSRDS +- Working on [Release 4.1.0](https://github.com/alan-turing-institute/data-safe-haven/issues/1544): fixes bugs and introduces necessary updates + + +### Codebase maintenance +https://github.com/alan-turing-institute/data-safe-haven-team/issues/47 + +Contributes to: +- Running projects working with sensitive data safely +- Running cutting edge data science projects effectively + +#### Goal +Ensure that codebase is kept up-to-date with bug fixes, security updates, external API changes etc. +- Ensure that DSH code is always deployable +- Ensure that known security issues are remediated/minimised as soon as possible +- Ensure that documentation is up-to-date with code base + +#### Progress + +- Working on debugging PostgreSQL permissions issues +- DBeaver driver fix https://github.com/alan-turing-institute/data-safe-haven/issues/1666 +- Improve handling of file paths [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1705) +- Checking out Azure feature retirement warnings [Issue](https://github.com/alan-turing-institute/data-safe-haven/issues/1697) +- Investigating issues with Julia on AMD processors: During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems +- Investigating issues with DBeaver on Tier 2+ SREs: DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. No problem on T1, but fails on T2. +- Testing solutions for cross-platform deployment: When deploying on Windows, some scripts fail if there are any spaces in the file path +- There has been work to address and improve issues and bugs related to last release while preparing for release 4.2.0. +- Factoring storage creation and account deployments out of main deployment script now allows for a more resilient process (not having to re-run everything when one fails) +- Also MS changing Azure Directory to Microsoft Entra ID has made necessary to spend time updating documentation and code, with the increased challenge that MS themsleves have not yet ocnsitently made the change. +- Name changing: [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1665) for changes to documentation - [Issue](https://github.com/alan-turing-institute/data-safe-haven/issues/1664) for changes to code +- Factor SHM storage creation out of main deployment script [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1673) +- 4.2.0 milestone related issues https://github.com/alan-turing-institute/data-safe-haven/milestone/21 +- Add all contributors table to project README and docs + - [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1649) + - Helps us better recognise contributors, especially those who do not appear in the commit history + - Will require maintainers to upkeep the list +- Fixed an issue where the user could provide an invalid name for storage accounts +- [Removal of MSRDS](https://github.com/alan-turing-institute/data-safe-haven/pull/1535) which reduces support burden and codebase complexity, instead Guacamole implementaiton is more robust and secure +- [Removal of CoCalc](https://github.com/alan-turing-institute/data-safe-haven/pull/1554) Reduces support burden for future releases by removing a largely unused feature +- Investigating adding arrow R package support +- Development/features + - [Drop Microsoft Remote Desktop](https://github.com/alan-turing-institute/data-safe-haven/issues/1159) primarly for increased security as it shows more issues than Guacamole, in doing this several other open issues are resolved +- Fixes/maintenance + - Documentation improvements alan-turing-institute/data-safe-haven/pull/1484 and updates https://github.com/alan-turing-institute/data-safe-haven/pull/1535 + +### Identify and implement core IAC changes +https://github.com/alan-turing-institute/data-safe-haven-team/issues/28 + +#### Goal +Make DSH deployment more robust and development easier through using IAC and configuration management. +- Take advantage of IAC and configuration management in the DSH codebase which will + - Make deployments faster + - Make deployments more reliable + - Make development easier +- Move away from non-idempotent, bespoke scripts (Powershell, bash, cloud-init) + +##### Definition of done +On the release of a new major version which removes legacy, script-based deployment. + +#### Progress +Arrived at a IAC MVP version of the code, available as a penetration tested [pre-release](https://github.com/alan-turing-institute/data-safe-haven/releases/tag/v5.0.0-rc.1). + +This new code is better and easier for users to deploy, however some incompatibilities with the old code would require extensive work. +As PowerShell heads to its final release it was decided not to work on fixing these. + +Since finishing migration a lot of the work is focusing on structuring the code, small improvements aimed at the user experience and robustness. + +These are main references and milestones, a more complete list is available on the [story issue](https://github.com/alan-turing-institute/data-safe-haven-team/issues/28) +- Codebase pre-release https://github.com/alan-turing-institute/data-safe-haven/releases/tag/v5.0.0-rc.1 +- Next version milestone https://github.com/alan-turing-institute/data-safe-haven/milestone/20 + +## Information governance & standards +Infrastructure adhering to the latest agreed upon standard +Identifying, co-creating and supporting a TRE standard used across TRE infrastructures + +## Community building +Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation +Creating and maintaining open and active communication spaces & workspaces (Slack, GH) +Identifying and documenting everything that can be openly documented + + From 3c8d6026462d3ab729479ba6d460b30b978c9678 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Thu, 1 Feb 2024 16:20:15 +0000 Subject: [PATCH 02/42] Update progress_report.md --- Reports/progress_report.md | 110 +++++++++++++++++++++++++++++++++++++ 1 file changed, 110 insertions(+) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 8cfd52d..b750089 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -3,6 +3,8 @@ This document contains a summary of progress across all stories in the [project roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1). It maps stories according to the (main) pillar and priority they contribute to. +Included stories are those that were scheduled and/or prioritised over this period (February 2023-February 2024), some not scheduled stories are included when there are updates for them regardless (indirect contirbutions from other stories, relevant work recently started, or something to report in general). + ## Infrastructure as code Running projects working with sensitive data safely Running cutting edge data science projects effectively @@ -97,9 +99,117 @@ These are main references and milestones, a more complete list is available on t Infrastructure adhering to the latest agreed upon standard Identifying, co-creating and supporting a TRE standard used across TRE infrastructures +### Co-create a TRE standard (SATRE) +https://github.com/alan-turing-institute/data-safe-haven-team/issues/23 + +Contributes to: +- Identifying, co-creating and supporting a TRE standard used across TRE infrastructures + +#### Goal +Develop the SATRE specification that UK TREs can evaluate themselves against + +##### Definition of done +SATRE specification published + +#### Progress +[SATRE specification](https://satre-specification.readthedocs.io/en/stable/) published, and available for contribution and reproducibility in its [open repository](https://github.com/sa-tre/satre-specification). + +Currently Turing and HIC have self-evaluated against it and evaluations are available openly, several conversations ongoing about other institutions doing the same and making them available. + +- Outputs: + - SATRE specification V1 and [associated technical paper](https://zenodo.org/records/10053383) + - Internal DARE report, link will be added and published openly + - [User report](https://zenodo.org/records/10066800): characterises users, with a wider notion than we started of what users are. Lays the fundation for futher usability work, going beyong technicla features and into training and documentation + - UK TRE Community - SATRE WG: the ongoing work and evolution of the specification is now a working group within the Uk TRE Community + +### Documentation management +https://github.com/alan-turing-institute/data-safe-haven-team/issues/32 + +Contributes to: +- Identifying, co-creating and supporting a TRE standard used across TRE infrastructures +- Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation +- Identifying and documenting everything that can be openly documented + +#### Goal +Comprehensive and clear documentation for the DSH, SATRE & TRESA will ensure open, reproducible outputs from this project. +- Ensure all relevant information is captured in documentation +- Test accessibility and discoverability of docs with relevant groups +- Iterate documentation in line with wider project work (e.g. TRESA processes, DSH updates) +- Determine what can/can't be documented (e.g. from an IG perspective). + +#### Definition of Done +When funding ends for the project and we have openly documented everything that we feel we can + +#### Progress +Documentation management have not been a story actively worked in, yet some processes have been updated and documented and needs identified. +While the story goes beyond Production processes it is worth noting that those have been handed over to TRESA, who are already suggesting and appliying changes. + + + ## Community building Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation Creating and maintaining open and active communication spaces & workspaces (Slack, GH) Identifying and documenting everything that can be openly documented +### Stakeholder landscape review +https://github.com/alan-turing-institute/data-safe-haven-team/issues/30 + +Contributes to: +- Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation +- Creating and maintaining open and active communication spaces & workspaces (Slack, GH) + +#### Goal +Across a lot of our work (DSH project, SATRE, UK TRE community) there has been a lot of discussion around who the impacted parties are, how they are categorised, what their interests/needs are etc. + +An effective stakeholder map showing all parties we think we should engage with will help us prioritise who to collaborate with, and strengthen our work in community building within the TRE space (which is kind of where this project is heading, above and beyond getting others to use the DSH). + +- [ ] Brainstorm and identify potential stakeholder groups +- [ ] Engage different groups through interviews/workshops to better understand them +- [ ] Create engagement pipeline & priority for different groups + +#### Definition of Done +- When we have an intended end-output from engagement with our established groups (e.g. by the end of the project, we want X group to be part of the UK TRE community, we want Y group to have contributed to the DSH repo...) + +#### Progress +The work done in [SATRE](https://github.com/alan-turing-institute/data-safe-haven-team/issues/23) and the [UK TRE Community](https://github.com/alan-turing-institute/data-safe-haven-team/issues/52) have directly contributed to estbalishing a relationship with key stakeholders, identify and characterise them. + +Direct and explicit work on this story have not been carried out (not scheduled in this period). + +We are now establishing the engagement pipleline by creating an internal CRM (sharepoint based currently). + +## Meta +Work and stories that do not belong directly in any pillars but are necessary for all + +### Project strategy and ways of work +https://github.com/alan-turing-institute/data-safe-haven-team/issues/43 + +#### Goal +The aim is to develop a project strategy and revise best ways of work to achieve it + +Through several strategy sessions we will: +- Define our north star (vision & mision) +- Establish the project pilars or areas, defining what success looks like for each +- Prioritise the measure of success, which are essential to consider the project succesful +- Identify work required to achieve success +- Allocate work by team +- Produce an initial roadmap +- Evaluate required effort for the work against team capacity +- Develop and agree new ways of work, including meeting structure and use of project's repositories and projects + +#### Progress + +##### Strategy + +Through several team wide sessions we jointly produced a [project strategy](https://thealanturininstitute.sharepoint.com/:p:/s/SafeHaven/Ebrp4Iyc9M1NpPTgpgHdj5kB7HPvH-2gM0oNd97jJu6oxw?e=eN0ZFw)https://thealanturininstitute.sharepoint.com/:p:/s/SafeHaven/Ebrp4Iyc9M1NpPTgpgHdj5kB7HPvH-2gM0oNd97jJu6oxw?e=eN0ZFw a long, medium and short term levels. + +This resulting in a clear Vision & Mision that have allowed internal alignment and improved external communications +< +To remove barriers to working safely and effectively with sensitive data,  +by promoting and demonstrating a culture of open, community-led development +of interoperable foundational infrastructure and governance. +> + +We also agreed the pillars of the project and estbalished a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1)https://github.com/orgs/alan-turing-institute/projects/111/views/1 of the necessary work for success. +##### Ways of work +Troughout this year we have also iterated our ways of work which are [openly available here](https://github.com/alan-turing-institute/data-safe-haven-team/blob/main/WaysofWork.md), they are focused in increased communication and work prioritisation. From ef95bdbe8aef7429ccbc3717815f069b03040b26 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Thu, 1 Feb 2024 16:36:09 +0000 Subject: [PATCH 03/42] Update progress_report.md --- Reports/progress_report.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index b750089..6f17771 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -177,6 +177,33 @@ Direct and explicit work on this story have not been carried out (not scheduled We are now establishing the engagement pipleline by creating an internal CRM (sharepoint based currently). +### UK TRE Community leadership +https://github.com/alan-turing-institute/data-safe-haven-team/issues/52 + +Contributes to: +- Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation +- Creating and maintaining open and active communication spaces & workspaces (Slack, GH) + +#### Goal +Provide a space for those involved in building, using and responsible for governance of TREs to discuss and reccomend best practices. +- [ ] Host online working spaces, events and workshops to support the UK TRE Community +- [ ] Share best practices i.e. for making radiology data available for researchers +- [ ] Empower the community to help influence policy decisions + +#### Progress +A lot of of effort has been put this year into the UK TRE Community, this year has seen the community mature and evolve from the original RSE TRE Community. +Currently we are delivering a funded project to ensure its sustainability which focuses one establishing the necessary spaces and governance processes. + +All work and progress during the funded phase can be consulted in [its board](https://github.com/orgs/uk-tre/projects/1) + +- The UK TRE Community event was held in Swansea on 4 September as a RSEcon23 satellite event. The event was very well attended with around 90 people in person and 50 online (figure to be revised), attendees were active on the day and had very positive feedback. + - [Report and notes](https://www.uktre.org/en/latest/events/wg_workshops/2023-09-04-september-meeting/index.html#provisional-schedule) +- We were awarded the DARE UK Community call. It was prepared and submitted to DARE UK community call, with full agreement and participation of the community itself +- Celebrated December community event (virtual). We presented the plans and work within this funded phase, which included a vision and mission for the community + - [Report and notes](https://www.uktre.org/en/latest/events/wg_workshops/2023-12-05-december-meeting/index.html) +- The first version of the Community Website is ready, it has been done using Hugo to balance quality and sustainability (being easily maintained and updated by the community after funding ends) +- Governance processes are being established, striving for simplicity in this phase. The conversation and work is open and welcomes all input and feedback. This is the [most active issue](https://github.com/uk-tre/community-management/pull/54) and a good starting point + ## Meta Work and stories that do not belong directly in any pillars but are necessary for all From 0b6b8bec180d51cd93171f699bfbaa830feb7781 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Thu, 1 Feb 2024 16:40:45 +0000 Subject: [PATCH 04/42] Update progress_report.md --- Reports/progress_report.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 6f17771..a3d08b1 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -144,7 +144,21 @@ When funding ends for the project and we have openly documented everything that Documentation management have not been a story actively worked in, yet some processes have been updated and documented and needs identified. While the story goes beyond Production processes it is worth noting that those have been handed over to TRESA, who are already suggesting and appliying changes. +### SATRE: stakeholder engagement and community buy out +https://github.com/alan-turing-institute/data-safe-haven-team/issues/66 +#### Goal +Ensure that institutions evaluate themselves against SATRE and that the momentum is maintained between funded phases + +At the end of the funded phase of SATRE there was a growing community interest, with institutions and stakeholders affirming they would evaluate themselves against it and contribute feedback. + +Without ongoing resources the necessary support to ensure that happens cannot be provided and SATRE may end up not being adopted. + +#### Definition of Done +There are a number of self evlauaitons completed, there is feedback on the spec repository and, ideally, there is an active WG within the TRE Community continuing to work on it. + +#### Progress +Work is folded into the [UK TRE Community](https://github.com/alan-turing-institute/data-safe-haven-team/issues/52), already SATRE is formally becoming a UK TRE Community WG. ## Community building Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation @@ -204,6 +218,7 @@ All work and progress during the funded phase can be consulted in [its board](ht - The first version of the Community Website is ready, it has been done using Hugo to balance quality and sustainability (being easily maintained and updated by the community after funding ends) - Governance processes are being established, striving for simplicity in this phase. The conversation and work is open and welcomes all input and feedback. This is the [most active issue](https://github.com/uk-tre/community-management/pull/54) and a good starting point + ## Meta Work and stories that do not belong directly in any pillars but are necessary for all From cb0bfba5e8ad4723ae7b14e806b9cfc8dc33be5f Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Thu, 1 Feb 2024 16:42:06 +0000 Subject: [PATCH 05/42] Update progress_report.md --- Reports/progress_report.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index a3d08b1..c7a23b9 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -245,11 +245,11 @@ Through several strategy sessions we will: Through several team wide sessions we jointly produced a [project strategy](https://thealanturininstitute.sharepoint.com/:p:/s/SafeHaven/Ebrp4Iyc9M1NpPTgpgHdj5kB7HPvH-2gM0oNd97jJu6oxw?e=eN0ZFw)https://thealanturininstitute.sharepoint.com/:p:/s/SafeHaven/Ebrp4Iyc9M1NpPTgpgHdj5kB7HPvH-2gM0oNd97jJu6oxw?e=eN0ZFw a long, medium and short term levels. This resulting in a clear Vision & Mision that have allowed internal alignment and improved external communications -< -To remove barriers to working safely and effectively with sensitive data,  + +>To remove barriers to working safely and effectively with sensitive data,  by promoting and demonstrating a culture of open, community-led development of interoperable foundational infrastructure and governance. -> +< We also agreed the pillars of the project and estbalished a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1)https://github.com/orgs/alan-turing-institute/projects/111/views/1 of the necessary work for success. From 1c37011416a4c6018fe9433724f46cc24414e806 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Thu, 1 Feb 2024 16:56:00 +0000 Subject: [PATCH 06/42] Update progress_report.md --- Reports/progress_report.md | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index c7a23b9..60c2336 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -218,6 +218,34 @@ All work and progress during the funded phase can be consulted in [its board](ht - The first version of the Community Website is ready, it has been done using Hugo to balance quality and sustainability (being easily maintained and updated by the community after funding ends) - Governance processes are being established, striving for simplicity in this phase. The conversation and work is open and welcomes all input and feedback. This is the [most active issue](https://github.com/uk-tre/community-management/pull/54) and a good starting point +### Communication and outreach +https://github.com/alan-turing-institute/data-safe-haven-team/issues/35 + +Contributes to: +- Creating and maintaining open and active communication spaces & workspaces (Slack, GH) +- Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation + +#### Goal +- Supporting the user community of the DSH codebase +- Publicising our work via blogposts, reports or papers +- Communicating our work through conference/workshop talks or posters + +#### Progress +This story has changed in scope along the year, work done here has been tha tof presenting DSH externally via events and talks. + +Yet we have identified work to be done within this story to define and establish a DSH community and user base, what this means and entails needs to be discussed and agreed yet. + +- We have established a shared slack channel with UCL to discuss common approaches to information governance processes +- [AI UK demonstration proposal](https://thealanturininstitute.sharepoint.com/:x:/s/SafeHaven/EfKD3w8Gi9NFv6JBshOkugsBOnn4v3ZdU-FTeIcy5obQcg?e=Rhq9w4) + - [proposal collaborative note](https://hackmd.io/AmcYdsyETU2dVgtIdfVL-g) + - We are following a similar format to last year but want to bring forward the community work and the satre specification. We want to have an interactive activity that blends role playing the different stakeholder groups and collectively deciding on specification features. The demo challenge last year did not work so the technical side this year will be demonstrated by a video and project members "touring" the repositories, docs and environment +- Met with Nottingham to support them as users of the DSH codebase +- The team worked together on the content for DSH activities on RSEcon as well as the UK TRE community satellite event #46 . +- The team visited the Bennett Institute for a show and tell about DSH and OpenSafely https://github.com/alan-turing-institute/tps-project-management/issues/157 + - No immediate collaboration but agreed to be involved in the specification and TRE community +- For discussion: this story needs to be redefined to include external engagement or a new one created + +## TRESA ## Meta Work and stories that do not belong directly in any pillars but are necessary for all @@ -249,7 +277,6 @@ This resulting in a clear Vision & Mision that have allowed internal alignment a >To remove barriers to working safely and effectively with sensitive data,  by promoting and demonstrating a culture of open, community-led development of interoperable foundational infrastructure and governance. -< We also agreed the pillars of the project and estbalished a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1)https://github.com/orgs/alan-turing-institute/projects/111/views/1 of the necessary work for success. From 01063da1147f9ecdf2362986c3b561efcbdff2d1 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Fri, 2 Feb 2024 09:56:38 +0000 Subject: [PATCH 07/42] Update progress_report.md --- Reports/progress_report.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 60c2336..8c9968d 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -246,6 +246,23 @@ Yet we have identified work to be done within this story to define and establish - For discussion: this story needs to be redefined to include external engagement or a new one created ## TRESA +Over the year TRESA have increased its autonomy from the DSH research project, in terms of work ownership and management. +Therefore TRESA stories have not been indepently updated and it is more comprenhensive to update on the service area as a whole. + +This warrants updating and reviewing the stories we keep under the DSH roadmap, focusing on communicating with the service area rahter than planning or prioritising for them. + +### Updates +A new team of have been onboarded, who have focused on learning the ropes while simultaneously supporting the December DSG. +With some support from the DSH team they were able to do so. + +We had a detailed[ handover meeting](https://hackmd.io/kh6siuZcTdCxcfYryAvypw) to go over each process, the idea is that moving forward TRESA directly owns processes and their improvement. + +We have also identified areas of work for TRESA to fully establish itself as a service area, these need to be elaborated into a full proposal with sprints and stories but main areas are: +- Data protection +- Cost and recovery model +- Acredditation: ISO 27001 and DSPT renewal +- Client projects management + ## Meta Work and stories that do not belong directly in any pillars but are necessary for all From 66615dfb006137f2a556487ab44f3a3e6acd1855 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Fri, 2 Feb 2024 10:20:56 +0000 Subject: [PATCH 08/42] Update progress_report.md version 1 ready --- Reports/progress_report.md | 31 +++++++++++++------------------ 1 file changed, 13 insertions(+), 18 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 8c9968d..f9ca8f0 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -43,31 +43,26 @@ Ensure that codebase is kept up-to-date with bug fixes, security updates, extern #### Progress -- Working on debugging PostgreSQL permissions issues -- DBeaver driver fix https://github.com/alan-turing-institute/data-safe-haven/issues/1666 +This year saw the [4.1.0 release](https://github.com/alan-turing-institute/data-safe-haven/releases/tag/v4.1.0) with notable fixes, security and documentaiton updates. + +We are currently working towards a final PowerShell [version 4.2](https://github.com/alan-turing-institute/data-safe-haven/milestone/21), aim to make the release in time for next DSG and then focus exclusively on Pulumi. + +A more complete summary of work done is available in the story, but some key updates through the year are: +- Database permission issue debugging as PostgreSQL user privileges were not correctly applied. Now fixed in [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1708) +- ClamAV On-access was not running + - On-access virus scanning is a DSPT requirement, and this process was not running correctly. + - Fixed by [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1725) - Improve handling of file paths [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1705) -- Checking out Azure feature retirement warnings [Issue](https://github.com/alan-turing-institute/data-safe-haven/issues/1697) - Investigating issues with Julia on AMD processors: During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems - Investigating issues with DBeaver on Tier 2+ SREs: DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. No problem on T1, but fails on T2. -- Testing solutions for cross-platform deployment: When deploying on Windows, some scripts fail if there are any spaces in the file path -- There has been work to address and improve issues and bugs related to last release while preparing for release 4.2.0. - Factoring storage creation and account deployments out of main deployment script now allows for a more resilient process (not having to re-run everything when one fails) -- Also MS changing Azure Directory to Microsoft Entra ID has made necessary to spend time updating documentation and code, with the increased challenge that MS themsleves have not yet ocnsitently made the change. -- Name changing: [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1665) for changes to documentation - [Issue](https://github.com/alan-turing-institute/data-safe-haven/issues/1664) for changes to code +- MS changed the name of Azure Directory to Microsoft Entra ID which made necessary to spend time updating documentation and code - Factor SHM storage creation out of main deployment script [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1673) -- 4.2.0 milestone related issues https://github.com/alan-turing-institute/data-safe-haven/milestone/21 -- Add all contributors table to project README and docs - - [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1649) - - Helps us better recognise contributors, especially those who do not appear in the commit history - - Will require maintainers to upkeep the list -- Fixed an issue where the user could provide an invalid name for storage accounts +- Add all contributors table to project README and docs [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1649) - [Removal of MSRDS](https://github.com/alan-turing-institute/data-safe-haven/pull/1535) which reduces support burden and codebase complexity, instead Guacamole implementaiton is more robust and secure - [Removal of CoCalc](https://github.com/alan-turing-institute/data-safe-haven/pull/1554) Reduces support burden for future releases by removing a largely unused feature -- Investigating adding arrow R package support -- Development/features - - [Drop Microsoft Remote Desktop](https://github.com/alan-turing-institute/data-safe-haven/issues/1159) primarly for increased security as it shows more issues than Guacamole, in doing this several other open issues are resolved -- Fixes/maintenance - - Documentation improvements alan-turing-institute/data-safe-haven/pull/1484 and updates https://github.com/alan-turing-institute/data-safe-haven/pull/1535 +- [Drop Microsoft Remote Desktop](https://github.com/alan-turing-institute/data-safe-haven/issues/1159) primarly for increased security as it shows more issues than Guacamole, in doing this several other open issues are resolved +- Documentation improvements and updates ### Identify and implement core IAC changes https://github.com/alan-turing-institute/data-safe-haven-team/issues/28 From 47c10e554116fd757c3512a9fbab7d627a1fab2e Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:47:25 +0000 Subject: [PATCH 09/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index f9ca8f0..e3028b5 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -3,7 +3,7 @@ This document contains a summary of progress across all stories in the [project roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1). It maps stories according to the (main) pillar and priority they contribute to. -Included stories are those that were scheduled and/or prioritised over this period (February 2023-February 2024), some not scheduled stories are included when there are updates for them regardless (indirect contirbutions from other stories, relevant work recently started, or something to report in general). +Included stories are those that were scheduled and/or prioritised over this period (February 2023-February 2024), some not scheduled stories are included when there are updates for them regardless (indirect contributions from other stories, relevant work recently started, or something to report in general). ## Infrastructure as code Running projects working with sensitive data safely From 51174476a7504d8db881ad81b647c0a0fc1f61d0 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:49:28 +0000 Subject: [PATCH 10/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index e3028b5..92ff504 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -10,8 +10,8 @@ Running projects working with sensitive data safely Running cutting edge data science projects effectively -### Manage codebase releases and testing -https://github.com/alan-turing-institute/data-safe-haven-team/issues/50 +### Manage codebase releases and testing: [#50](https://github.com/alan-turing-institute/data-safe-haven-team/issues/50) + Contributes to: - Running projects working with sensitive data safely From 8932bfc09dac6f63eca75c1d1e610d59e8e4247f Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:55:16 +0000 Subject: [PATCH 11/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 92ff504..9c99d22 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -28,8 +28,7 @@ Support for deployments of the Data Safe Haven at Turing and beyond - Working on [Release 4.1.0](https://github.com/alan-turing-institute/data-safe-haven/issues/1544): fixes bugs and introduces necessary updates -### Codebase maintenance -https://github.com/alan-turing-institute/data-safe-haven-team/issues/47 +### Codebase maintenance: [#47](https://github.com/alan-turing-institute/data-safe-haven-team/issues/47) Contributes to: - Running projects working with sensitive data safely From 9c6526fc7fa92db7c0f0024fd59ae66e11bf6aa6 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:55:37 +0000 Subject: [PATCH 12/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 9c99d22..e375dc0 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -44,7 +44,8 @@ Ensure that codebase is kept up-to-date with bug fixes, security updates, extern This year saw the [4.1.0 release](https://github.com/alan-turing-institute/data-safe-haven/releases/tag/v4.1.0) with notable fixes, security and documentaiton updates. -We are currently working towards a final PowerShell [version 4.2](https://github.com/alan-turing-institute/data-safe-haven/milestone/21), aim to make the release in time for next DSG and then focus exclusively on Pulumi. +We are currently working towards a final PowerShell version ([Release 4.2.0 Milestone](https://github.com/alan-turing-institute/data-safe-haven/milestone/21)). +The aim is to make the release in time for next DSG and then focus exclusively on Pulumi. A more complete summary of work done is available in the story, but some key updates through the year are: - Database permission issue debugging as PostgreSQL user privileges were not correctly applied. Now fixed in [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1708) From 5846f8af42dbbe562908168dddca6743409b9c75 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:55:54 +0000 Subject: [PATCH 13/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index e375dc0..d4b4017 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -48,7 +48,8 @@ We are currently working towards a final PowerShell version ([Release 4.2.0 Mile The aim is to make the release in time for next DSG and then focus exclusively on Pulumi. A more complete summary of work done is available in the story, but some key updates through the year are: -- Database permission issue debugging as PostgreSQL user privileges were not correctly applied. Now fixed in [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1708) +- Database permission issue debugging as PostgreSQL user privileges were not correctly applied. + - Now fixed in PR [#1708](https://github.com/alan-turing-institute/data-safe-haven/pull/1708). - ClamAV On-access was not running - On-access virus scanning is a DSPT requirement, and this process was not running correctly. - Fixed by [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1725) From f0b89ebd9685aaa3cbec9ed6ad7b2fdc6531227a Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:58:39 +0000 Subject: [PATCH 14/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index d4b4017..fbbaae9 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -52,7 +52,7 @@ A more complete summary of work done is available in the story, but some key upd - Now fixed in PR [#1708](https://github.com/alan-turing-institute/data-safe-haven/pull/1708). - ClamAV On-access was not running - On-access virus scanning is a DSPT requirement, and this process was not running correctly. - - Fixed by [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1725) + - Fixed by PR [#1725](https://github.com/alan-turing-institute/data-safe-haven/pull/1725). - Improve handling of file paths [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1705) - Investigating issues with Julia on AMD processors: During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems - Investigating issues with DBeaver on Tier 2+ SREs: DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. No problem on T1, but fails on T2. From 5e0bbfa30f5d5f6602b9d9de6b9a12b96601e29e Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 11:59:22 +0000 Subject: [PATCH 15/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index fbbaae9..53c25c7 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -53,7 +53,7 @@ A more complete summary of work done is available in the story, but some key upd - ClamAV On-access was not running - On-access virus scanning is a DSPT requirement, and this process was not running correctly. - Fixed by PR [#1725](https://github.com/alan-turing-institute/data-safe-haven/pull/1725). -- Improve handling of file paths [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1705) +- Improve handling of file paths PR [#1705](https://github.com/alan-turing-institute/data-safe-haven/pull/1705). - Investigating issues with Julia on AMD processors: During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems - Investigating issues with DBeaver on Tier 2+ SREs: DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. No problem on T1, but fails on T2. - Factoring storage creation and account deployments out of main deployment script now allows for a more resilient process (not having to re-run everything when one fails) From f3f08f5b9f5884d94087f775bff01647bca88f9a Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:00:17 +0000 Subject: [PATCH 16/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 53c25c7..937046a 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -55,7 +55,9 @@ A more complete summary of work done is available in the story, but some key upd - Fixed by PR [#1725](https://github.com/alan-turing-institute/data-safe-haven/pull/1725). - Improve handling of file paths PR [#1705](https://github.com/alan-turing-institute/data-safe-haven/pull/1705). - Investigating issues with Julia on AMD processors: During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems -- Investigating issues with DBeaver on Tier 2+ SREs: DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. No problem on T1, but fails on T2. +- Investigating issues with DBeaver on Tier 2+ SREs: + - DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. + No problem on T1, but fails on T2. - Factoring storage creation and account deployments out of main deployment script now allows for a more resilient process (not having to re-run everything when one fails) - MS changed the name of Azure Directory to Microsoft Entra ID which made necessary to spend time updating documentation and code - Factor SHM storage creation out of main deployment script [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1673) From e05871be95b7ab0c95f30a74498eec2c9452ce8c Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:01:15 +0000 Subject: [PATCH 17/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 937046a..bf5f23b 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -67,8 +67,7 @@ A more complete summary of work done is available in the story, but some key upd - [Drop Microsoft Remote Desktop](https://github.com/alan-turing-institute/data-safe-haven/issues/1159) primarly for increased security as it shows more issues than Guacamole, in doing this several other open issues are resolved - Documentation improvements and updates -### Identify and implement core IAC changes -https://github.com/alan-turing-institute/data-safe-haven-team/issues/28 +### Identify and implement core IAC changes: [#28](https://github.com/alan-turing-institute/data-safe-haven-team/issues/28) #### Goal Make DSH deployment more robust and development easier through using IAC and configuration management. From e5bc1e63024b2a7ef3b86e79324ad927254581e4 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:01:28 +0000 Subject: [PATCH 18/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index bf5f23b..9def36e 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -60,11 +60,11 @@ A more complete summary of work done is available in the story, but some key upd No problem on T1, but fails on T2. - Factoring storage creation and account deployments out of main deployment script now allows for a more resilient process (not having to re-run everything when one fails) - MS changed the name of Azure Directory to Microsoft Entra ID which made necessary to spend time updating documentation and code -- Factor SHM storage creation out of main deployment script [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1673) -- Add all contributors table to project README and docs [PR](https://github.com/alan-turing-institute/data-safe-haven/pull/1649) -- [Removal of MSRDS](https://github.com/alan-turing-institute/data-safe-haven/pull/1535) which reduces support burden and codebase complexity, instead Guacamole implementaiton is more robust and secure -- [Removal of CoCalc](https://github.com/alan-turing-institute/data-safe-haven/pull/1554) Reduces support burden for future releases by removing a largely unused feature -- [Drop Microsoft Remote Desktop](https://github.com/alan-turing-institute/data-safe-haven/issues/1159) primarly for increased security as it shows more issues than Guacamole, in doing this several other open issues are resolved +- Factor SHM storage creation out of main deployment script: PR [#1673](https://github.com/alan-turing-institute/data-safe-haven/pull/1673) +- Add all contributors table to project README and docs: PR[#1649](https://github.com/alan-turing-institute/data-safe-haven/pull/1649). +- Removal of MSRDS (PR: [#1535](https://github.com/alan-turing-institute/data-safe-haven/pull/1535)) which reduces support burden and codebase complexity, instead Guacamole implementation is more robust and secure. +- Removal of CoCalc (PR: [#1554](https://github.com/alan-turing-institute/data-safe-haven/pull/1554) Reduces support burden for future releases by removing a largely unused feature. +- Drop Microsoft Remote Desktop: (PR: [#1159](https://github.com/alan-turing-institute/data-safe-haven/issues/1159) primarily for increased security as it shows more issues than Guacamole, in doing this several other open issues are resolved. - Documentation improvements and updates ### Identify and implement core IAC changes: [#28](https://github.com/alan-turing-institute/data-safe-haven-team/issues/28) From b8997216b6a44d6ad7c29677f105286ddcebdade Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:05:11 +0000 Subject: [PATCH 19/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 9def36e..a3758c4 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -96,8 +96,7 @@ These are main references and milestones, a more complete list is available on t Infrastructure adhering to the latest agreed upon standard Identifying, co-creating and supporting a TRE standard used across TRE infrastructures -### Co-create a TRE standard (SATRE) -https://github.com/alan-turing-institute/data-safe-haven-team/issues/23 +### Co-create a TRE standard (SATRE): [#23](https://github.com/alan-turing-institute/data-safe-haven-team/issues/23) Contributes to: - Identifying, co-creating and supporting a TRE standard used across TRE infrastructures From 31723d4f4f7786ea3789e939af82e503802f1e2b Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:09:43 +0000 Subject: [PATCH 20/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index a3758c4..c8489bb 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -118,8 +118,7 @@ Currently Turing and HIC have self-evaluated against it and evaluations are avai - [User report](https://zenodo.org/records/10066800): characterises users, with a wider notion than we started of what users are. Lays the fundation for futher usability work, going beyong technicla features and into training and documentation - UK TRE Community - SATRE WG: the ongoing work and evolution of the specification is now a working group within the Uk TRE Community -### Documentation management -https://github.com/alan-turing-institute/data-safe-haven-team/issues/32 +### Documentation management [#32](https://github.com/alan-turing-institute/data-safe-haven-team/issues/32) Contributes to: - Identifying, co-creating and supporting a TRE standard used across TRE infrastructures From e0c6afd0a1089df471a613646b0e75834e1d69a1 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:11:02 +0000 Subject: [PATCH 21/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index c8489bb..235e6fb 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -139,8 +139,7 @@ When funding ends for the project and we have openly documented everything that Documentation management have not been a story actively worked in, yet some processes have been updated and documented and needs identified. While the story goes beyond Production processes it is worth noting that those have been handed over to TRESA, who are already suggesting and appliying changes. -### SATRE: stakeholder engagement and community buy out -https://github.com/alan-turing-institute/data-safe-haven-team/issues/66 +### SATRE: stakeholder engagement and community buy out [#66](https://github.com/alan-turing-institute/data-safe-haven-team/issues/66) #### Goal Ensure that institutions evaluate themselves against SATRE and that the momentum is maintained between funded phases From bc2e589e8199821955f15c6cd439789863c73f5a Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:17:42 +0000 Subject: [PATCH 22/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 235e6fb..bb26a47 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -159,8 +159,7 @@ Creating resources for all stakeholders (inc. Citizens) to engage in the TRE con Creating and maintaining open and active communication spaces & workspaces (Slack, GH) Identifying and documenting everything that can be openly documented -### Stakeholder landscape review -https://github.com/alan-turing-institute/data-safe-haven-team/issues/30 +### Stakeholder landscape review [#30](https://github.com/alan-turing-institute/data-safe-haven-team/issues/30) Contributes to: - Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation From a5e05524614c5f51d4ddc564bec732305287b911 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:19:23 +0000 Subject: [PATCH 23/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index bb26a47..ae9fc30 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -184,8 +184,7 @@ Direct and explicit work on this story have not been carried out (not scheduled We are now establishing the engagement pipleline by creating an internal CRM (sharepoint based currently). -### UK TRE Community leadership -https://github.com/alan-turing-institute/data-safe-haven-team/issues/52 +### UK TRE Community leadership [#52](https://github.com/alan-turing-institute/data-safe-haven-team/issues/52) Contributes to: - Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation From f65b8919d34de412b8c575e67c54d6d12ead8b8b Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:21:28 +0000 Subject: [PATCH 24/42] Update Reports/progress_report.md --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index ae9fc30..0228d39 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -203,7 +203,7 @@ Currently we are delivering a funded project to ensure its sustainability which All work and progress during the funded phase can be consulted in [its board](https://github.com/orgs/uk-tre/projects/1) - The UK TRE Community event was held in Swansea on 4 September as a RSEcon23 satellite event. The event was very well attended with around 90 people in person and 50 online (figure to be revised), attendees were active on the day and had very positive feedback. - - [Report and notes](https://www.uktre.org/en/latest/events/wg_workshops/2023-09-04-september-meeting/index.html#provisional-schedule) + - [Report and notes](https://www.uktre.org/en/latest/events/wg_workshops/2023-09-04-september-meeting/index.html) - We were awarded the DARE UK Community call. It was prepared and submitted to DARE UK community call, with full agreement and participation of the community itself - Celebrated December community event (virtual). We presented the plans and work within this funded phase, which included a vision and mission for the community - [Report and notes](https://www.uktre.org/en/latest/events/wg_workshops/2023-12-05-december-meeting/index.html) From 550b78a0f87cb09d5cfd52101a77cd5d56deb3d9 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:36:26 +0000 Subject: [PATCH 25/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 0228d39..9f930c0 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -259,8 +259,7 @@ We have also identified areas of work for TRESA to fully establish itself as a s ## Meta Work and stories that do not belong directly in any pillars but are necessary for all -### Project strategy and ways of work -https://github.com/alan-turing-institute/data-safe-haven-team/issues/43 +### Project strategy and ways of working [#43](https://github.com/alan-turing-institute/data-safe-haven-team/issues/43) #### Goal The aim is to develop a project strategy and revise best ways of work to achieve it From 3b56cd8e49c064a8ef56b8bac7480a568a6b66c0 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Mon, 5 Feb 2024 12:37:55 +0000 Subject: [PATCH 26/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 9f930c0..a3f5081 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -286,7 +286,7 @@ This resulting in a clear Vision & Mision that have allowed internal alignment a by promoting and demonstrating a culture of open, community-led development of interoperable foundational infrastructure and governance. -We also agreed the pillars of the project and estbalished a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1)https://github.com/orgs/alan-turing-institute/projects/111/views/1 of the necessary work for success. +We also agreed the pillars of the project and established a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1) of the necessary work for success. ##### Ways of work Troughout this year we have also iterated our ways of work which are [openly available here](https://github.com/alan-turing-institute/data-safe-haven-team/blob/main/WaysofWork.md), they are focused in increased communication and work prioritisation. From f987b862200657415131983a2031ce24ae68c0f3 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 12:50:15 +0100 Subject: [PATCH 27/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index a3f5081..033ddcc 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -50,7 +50,7 @@ The aim is to make the release in time for next DSG and then focus exclusively o A more complete summary of work done is available in the story, but some key updates through the year are: - Database permission issue debugging as PostgreSQL user privileges were not correctly applied. - Now fixed in PR [#1708](https://github.com/alan-turing-institute/data-safe-haven/pull/1708). -- ClamAV On-access was not running +- ClamAV On-access was not running. - On-access virus scanning is a DSPT requirement, and this process was not running correctly. - Fixed by PR [#1725](https://github.com/alan-turing-institute/data-safe-haven/pull/1725). - Improve handling of file paths PR [#1705](https://github.com/alan-turing-institute/data-safe-haven/pull/1705). From 1f75efa565169f416460921546e40c0be6a30bfc Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 12:56:09 +0100 Subject: [PATCH 28/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 033ddcc..8e6cc71 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -116,7 +116,7 @@ Currently Turing and HIC have self-evaluated against it and evaluations are avai - SATRE specification V1 and [associated technical paper](https://zenodo.org/records/10053383) - Internal DARE report, link will be added and published openly - [User report](https://zenodo.org/records/10066800): characterises users, with a wider notion than we started of what users are. Lays the fundation for futher usability work, going beyong technicla features and into training and documentation - - UK TRE Community - SATRE WG: the ongoing work and evolution of the specification is now a working group within the Uk TRE Community + - UK TRE Community - SATRE WG: the ongoing work and evolution of the specification is now a working group within the UK TRE Community ### Documentation management [#32](https://github.com/alan-turing-institute/data-safe-haven-team/issues/32) From cb52c71a7aaae8b10d916b8b087895b1824461d4 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 15:58:06 +0100 Subject: [PATCH 29/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 8e6cc71..f261fdd 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -155,7 +155,7 @@ There are a number of self evlauaitons completed, there is feedback on the spec Work is folded into the [UK TRE Community](https://github.com/alan-turing-institute/data-safe-haven-team/issues/52), already SATRE is formally becoming a UK TRE Community WG. ## Community building -Creating resources for all stakeholders (inc. Citizens) to engage in the TRE conversation +Creating resources for all stakeholders (inc. members of the public) to engage in the TRE conversation Creating and maintaining open and active communication spaces & workspaces (Slack, GH) Identifying and documenting everything that can be openly documented From d25e1438afb894063ea90506332d616661792aa3 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:00:04 +0100 Subject: [PATCH 30/42] Update Reports/progress_report.md Co-authored-by: Jim Madge --- Reports/progress_report.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index f261fdd..a540070 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -170,9 +170,9 @@ Across a lot of our work (DSH project, SATRE, UK TRE community) there has been a An effective stakeholder map showing all parties we think we should engage with will help us prioritise who to collaborate with, and strengthen our work in community building within the TRE space (which is kind of where this project is heading, above and beyond getting others to use the DSH). -- [ ] Brainstorm and identify potential stakeholder groups -- [ ] Engage different groups through interviews/workshops to better understand them -- [ ] Create engagement pipeline & priority for different groups +- Brainstorm and identify potential stakeholder groups +- Engage different groups through interviews/workshops to better understand them +- Create engagement pipeline & priority for different groups #### Definition of Done - When we have an intended end-output from engagement with our established groups (e.g. by the end of the project, we want X group to be part of the UK TRE community, we want Y group to have contributed to the DSH repo...) From 929af15794da787de71ad44cd36bc0608bb82fe6 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:08:02 +0100 Subject: [PATCH 31/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index a540070..a2b88bf 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -191,7 +191,7 @@ Contributes to: - Creating and maintaining open and active communication spaces & workspaces (Slack, GH) #### Goal -Provide a space for those involved in building, using and responsible for governance of TREs to discuss and reccomend best practices. +Provide a space for those involved in building, using and responsible for governance of TREs to discuss and recommend best practices. - [ ] Host online working spaces, events and workshops to support the UK TRE Community - [ ] Share best practices i.e. for making radiology data available for researchers - [ ] Empower the community to help influence policy decisions From 2cd4bb7ec4cda3c704d4c1b21cfaa7ed07671e3f Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:09:20 +0100 Subject: [PATCH 32/42] Update Reports/progress_report.md Co-authored-by: Jim Madge --- Reports/progress_report.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index a2b88bf..62a9f9d 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -192,9 +192,9 @@ Contributes to: #### Goal Provide a space for those involved in building, using and responsible for governance of TREs to discuss and recommend best practices. -- [ ] Host online working spaces, events and workshops to support the UK TRE Community -- [ ] Share best practices i.e. for making radiology data available for researchers -- [ ] Empower the community to help influence policy decisions +- Host online working spaces, events and workshops to support the UK TRE Community +- Share best practices i.e. for making radiology data available for researchers +- Empower the community to help influence policy decisions #### Progress A lot of of effort has been put this year into the UK TRE Community, this year has seen the community mature and evolve from the original RSE TRE Community. From d762ac35ee523a6acc2a4221729be23ef68f9a53 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:10:30 +0100 Subject: [PATCH 33/42] Update Reports/progress_report.md Co-authored-by: Jim Madge --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 62a9f9d..1eb7c22 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -200,7 +200,7 @@ Provide a space for those involved in building, using and responsible for govern A lot of of effort has been put this year into the UK TRE Community, this year has seen the community mature and evolve from the original RSE TRE Community. Currently we are delivering a funded project to ensure its sustainability which focuses one establishing the necessary spaces and governance processes. -All work and progress during the funded phase can be consulted in [its board](https://github.com/orgs/uk-tre/projects/1) +All work and progress during the funded phase can be consulted on [the community project board](https://github.com/orgs/uk-tre/projects/1) - The UK TRE Community event was held in Swansea on 4 September as a RSEcon23 satellite event. The event was very well attended with around 90 people in person and 50 online (figure to be revised), attendees were active on the day and had very positive feedback. - [Report and notes](https://www.uktre.org/en/latest/events/wg_workshops/2023-09-04-september-meeting/index.html) From 4774c65525f85c1afd8cb4e5da43a2e8d94ece0a Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:14:44 +0100 Subject: [PATCH 34/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 1eb7c22..fb0b560 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -210,8 +210,7 @@ All work and progress during the funded phase can be consulted on [the community - The first version of the Community Website is ready, it has been done using Hugo to balance quality and sustainability (being easily maintained and updated by the community after funding ends) - Governance processes are being established, striving for simplicity in this phase. The conversation and work is open and welcomes all input and feedback. This is the [most active issue](https://github.com/uk-tre/community-management/pull/54) and a good starting point -### Communication and outreach -https://github.com/alan-turing-institute/data-safe-haven-team/issues/35 +### Communication and outreach [#35](https://github.com/alan-turing-institute/data-safe-haven-team/issues/35) Contributes to: - Creating and maintaining open and active communication spaces & workspaces (Slack, GH) From 1df5a626acfaf44b3c235e7505acbbddfb19e3ec Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:19:09 +0100 Subject: [PATCH 35/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index fb0b560..8e94aa6 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -222,7 +222,7 @@ Contributes to: - Communicating our work through conference/workshop talks or posters #### Progress -This story has changed in scope along the year, work done here has been tha tof presenting DSH externally via events and talks. +This story has changed in scope along the year, work done here has been that of presenting DSH externally via events and talks. Yet we have identified work to be done within this story to define and establish a DSH community and user base, what this means and entails needs to be discussed and agreed yet. From 5f7b0ab9308a8150e2fa0ff76681ddf9272b3dfd Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:26:49 +0100 Subject: [PATCH 36/42] Update Reports/progress_report.md Co-authored-by: Jim Madge --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 8e94aa6..d05c390 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -240,7 +240,7 @@ Yet we have identified work to be done within this story to define and establish Over the year TRESA have increased its autonomy from the DSH research project, in terms of work ownership and management. Therefore TRESA stories have not been indepently updated and it is more comprenhensive to update on the service area as a whole. -This warrants updating and reviewing the stories we keep under the DSH roadmap, focusing on communicating with the service area rahter than planning or prioritising for them. +This warrants updating and reviewing the stories we keep under the DSH roadmap, focusing on communicating with the service area rather than planning or prioritising for them. ### Updates A new team of have been onboarded, who have focused on learning the ropes while simultaneously supporting the December DSG. From 815c4fea2edfab7820bd53c307e2122569036666 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:27:27 +0100 Subject: [PATCH 37/42] Update Reports/progress_report.md Co-authored-by: Jim Madge --- Reports/progress_report.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index d05c390..bfb4fb9 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -243,7 +243,8 @@ Therefore TRESA stories have not been indepently updated and it is more comprenh This warrants updating and reviewing the stories we keep under the DSH roadmap, focusing on communicating with the service area rather than planning or prioritising for them. ### Updates -A new team of have been onboarded, who have focused on learning the ropes while simultaneously supporting the December DSG. +A new team have been onboarded. +They have focused on learning the ropes while simultaneously supporting the December DSG. With some support from the DSH team they were able to do so. We had a detailed[ handover meeting](https://hackmd.io/kh6siuZcTdCxcfYryAvypw) to go over each process, the idea is that moving forward TRESA directly owns processes and their improvement. From 492a9798a29c96fdeed2ebeeac41ab4ed6978a44 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:31:50 +0100 Subject: [PATCH 38/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index bfb4fb9..4fc3d97 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -288,5 +288,5 @@ of interoperable foundational infrastructure and governance. We also agreed the pillars of the project and established a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1) of the necessary work for success. -##### Ways of work +##### Ways of working Troughout this year we have also iterated our ways of work which are [openly available here](https://github.com/alan-turing-institute/data-safe-haven-team/blob/main/WaysofWork.md), they are focused in increased communication and work prioritisation. From 1cf33f0d95eba38b3566c382adacb500868f0f3c Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:34:04 +0100 Subject: [PATCH 39/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 4fc3d97..9123941 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -247,7 +247,7 @@ A new team have been onboarded. They have focused on learning the ropes while simultaneously supporting the December DSG. With some support from the DSH team they were able to do so. -We had a detailed[ handover meeting](https://hackmd.io/kh6siuZcTdCxcfYryAvypw) to go over each process, the idea is that moving forward TRESA directly owns processes and their improvement. +We had a detailed [handover meeting](https://hackmd.io/kh6siuZcTdCxcfYryAvypw) to go over each process, the idea is that moving forward TRESA directly owns processes and their improvement. We have also identified areas of work for TRESA to fully establish itself as a service area, these need to be elaborated into a full proposal with sprints and stories but main areas are: - Data protection From 52fec13d46d6a21819634635c9a77415540d4efc Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:35:01 +0100 Subject: [PATCH 40/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 9123941..06f586a 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -238,7 +238,7 @@ Yet we have identified work to be done within this story to define and establish ## TRESA Over the year TRESA have increased its autonomy from the DSH research project, in terms of work ownership and management. -Therefore TRESA stories have not been indepently updated and it is more comprenhensive to update on the service area as a whole. +Therefore TRESA stories have not been independently updated and it is more comprehensive to update on the service area as a whole. This warrants updating and reviewing the stories we keep under the DSH roadmap, focusing on communicating with the service area rather than planning or prioritising for them. From 28a93b8e06d15de4c8d9587719050bc0fd0e6ab9 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:38:59 +0100 Subject: [PATCH 41/42] Update Reports/progress_report.md Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 06f586a..233ba57 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -289,4 +289,4 @@ of interoperable foundational infrastructure and governance. We also agreed the pillars of the project and established a [roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1) of the necessary work for success. ##### Ways of working -Troughout this year we have also iterated our ways of work which are [openly available here](https://github.com/alan-turing-institute/data-safe-haven-team/blob/main/WaysofWork.md), they are focused in increased communication and work prioritisation. +Throughout this year we have also iterated our ways of working which are openly available on GitHub in [WaysofWork.md](https://github.com/alan-turing-institute/data-safe-haven-team/blob/main/WaysofWork.md), they are focused in increased communication and work prioritisation. From 8f90a202246dafcbbd5ab27cbaf0b18a40926658 Mon Sep 17 00:00:00 2001 From: Davsarper <118986872+Davsarper@users.noreply.github.com> Date: Wed, 3 Apr 2024 16:50:35 +0100 Subject: [PATCH 42/42] Apply suggestions from code review committing my own suggestions, unsure it is best practice but they should not be controversial (they are direct applications of feedback) Co-authored-by: Kirstie Whitaker --- Reports/progress_report.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/Reports/progress_report.md b/Reports/progress_report.md index 233ba57..da3fd27 100644 --- a/Reports/progress_report.md +++ b/Reports/progress_report.md @@ -1,11 +1,13 @@ # Data Safe Haven project report +**Period: [February 2023-January 2024]** + This document contains a summary of progress across all stories in the [project roadmap](https://github.com/orgs/alan-turing-institute/projects/111/views/1). It maps stories according to the (main) pillar and priority they contribute to. -Included stories are those that were scheduled and/or prioritised over this period (February 2023-February 2024), some not scheduled stories are included when there are updates for them regardless (indirect contributions from other stories, relevant work recently started, or something to report in general). +Included stories are those that were scheduled and/or prioritised over this period (February 2023-January 2024), some not scheduled stories are included when there are updates for them regardless (indirect contributions from other stories, relevant work recently started, or something to report in general). -## Infrastructure as code +## Codebase development Running projects working with sensitive data safely Running cutting edge data science projects effectively @@ -54,7 +56,8 @@ A more complete summary of work done is available in the story, but some key upd - On-access virus scanning is a DSPT requirement, and this process was not running correctly. - Fixed by PR [#1725](https://github.com/alan-turing-institute/data-safe-haven/pull/1725). - Improve handling of file paths PR [#1705](https://github.com/alan-turing-institute/data-safe-haven/pull/1705). -- Investigating issues with Julia on AMD processors: During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems +- Investigating issues with Julia on AMD processors: + - During the building of VM images for deployment in SREs, Julia created and stored compiled versions of packages that were suitable only for Intel systems, causing crashes when users wanted to use AMD systems. - Investigating issues with DBeaver on Tier 2+ SREs: - DBeaver drivers were not installing correctly during VM building, so it tries to download them from the internet. No problem on T1, but fails on T2. @@ -112,6 +115,12 @@ SATRE specification published Currently Turing and HIC have self-evaluated against it and evaluations are available openly, several conversations ongoing about other institutions doing the same and making them available. +Organisations that have declared they are going through the self evaluation (at the time of reporting): +- KCL +- Sheffield +- North West NHS SNSDE +- NHS SDE technology group reviewing SATRE + - Outputs: - SATRE specification V1 and [associated technical paper](https://zenodo.org/records/10053383) - Internal DARE report, link will be added and published openly @@ -256,7 +265,7 @@ We have also identified areas of work for TRESA to fully establish itself as a s - Client projects management -## Meta +## Project management and strategy Work and stories that do not belong directly in any pillars but are necessary for all ### Project strategy and ways of working [#43](https://github.com/alan-turing-institute/data-safe-haven-team/issues/43)