-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #56 from uk-tre/Davsarper-update-wg-oldweb
Update index.md
- Loading branch information
Showing
8 changed files
with
260 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Citizen agency | ||
|
||
## Charter | ||
|
||
This is the main document to refer to, it should contain all of the below and further detail: you can find it within this [summary document with information of all working groups](https://docs.google.com/document/d/1uvqALeVixK6PqdkzLFVwDVhc0fPUuBdddyfQzZsRtm4/edit?usp=sharing). | ||
|
||
(sorry for the lack of a direct link, but it lives in dropbox) | ||
|
||
## Overview | ||
|
||
The Citizen Agency Working group is focused on documenting and outlining possible roles for the citizen within the data research arena, | ||
with specific focus on the Secure Data Environment/Trusted Research Environment facilities. | ||
|
||
This Working Groups was set up to support delivery of these overall macro concerns and objectives. | ||
|
||
- To minimise Time-to-research and delay | ||
- To make combining datasets easy and reduce barriers to research project scope | ||
- To include Citizen’s agency into the “TRE landscape” and Information Governance | ||
|
||
## Co-chairs and contact | ||
|
||
**Chair:** This is Pete Barnsley, Francis Crick Institute, London [email protected] | ||
**Contact:** This is Pete Barnsley, Francis Crick Institute, London [email protected] | ||
|
||
## How to get involved | ||
|
||
(mailing list, slack channel, repositories…) | ||
|
||
Mailing list: [email protected] | ||
|
||
- Sign up form https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=WG-CITIZEN-AGENCY-UKTRE-COMM&A=1 | ||
|
||
Slack: #wg-citizen-agency channel on the [UK TRE Community slack](https://join.slack.com/t/uktrecommunity/shared_invite/zt-2gep86apc-QMLyIdrC2oIIsxTRzLxUqA) | ||
|
||
Dropbox: ask for the link to existing members or Pete Barnsley, | ||
you can also find it within this you can find it within this [summary document with information of all working groups](https://docs.google.com/document/d/1uvqALeVixK6PqdkzLFVwDVhc0fPUuBdddyfQzZsRtm4/edit?usp=sharing). | ||
|
||
People interested in supporting this work should contact the primary contact or chair, or just add to the slack channel discussions. | ||
The prime contact is Pete Barnsley, Francis Crick Institute, London [email protected] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# Cybersecurity risk | ||
|
||
## Charter | ||
|
||
This is the main document to refer to, | ||
it should contain all of the below and further detail: [CyberSec Risks Working Group Charter](https://docs.google.com/document/d/1KLIeB4uDDxwYT7pxj5ImHa5p_3wJ2KILsVKuAl7LQlM/edit?usp=sharing) | ||
|
||
## Overview | ||
|
||
This working group is an opportunity for the UK TRE Community to explore issues related to the management and communication of cyber security related risks in TREs. | ||
|
||
General guidance on cyber security management, risk identification and mitigation, and good cyber security practice for service providers and software developers is readily available. However, specific guidance in the context of TREs is not, and this group aims to provide that guidance by defining requirements such as type of tools to be used, and their purpose in a TRE. Concrete example implementations will be provided, but the principles will be more generally applicable. | ||
|
||
## Co-chairs and contact | ||
|
||
**Co-Chairs:** | ||
|
||
- Donald Scobbie (EPCC) | ||
- Martin O’Reilly (The Alan Turing Institute) | ||
|
||
**Contact:** Donald Scobbie ([email protected]) | ||
|
||
The main communication channels for the WG will be: | ||
|
||
- The WG email list (tbd) | ||
- The WG Slack channel | ||
- Regular UK TRE Community webinar events and presentations | ||
|
||
## How to get involved | ||
|
||
(mailing list, slack channel, repositories…) | ||
|
||
[Working Group repository](https://github.com/uk-tre/cybersec-wg) will be prioritized for involvement in this working group | ||
|
||
The main communication channels for the WG will be: | ||
|
||
- The WG email list (tbd) | ||
- The WG Slack channel | ||
- Regular UK TRE Community webinar events and presentations | ||
|
||
The working group will progress as a series of ‘task and finish’ exercises to complete specific work related to tools, processes and documents. Contributors will be encouraged to participate in the working group at task level so that contributions can be short term, focussed, and benefit from specific skills. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# Extending control | ||
|
||
## Charter | ||
|
||
This is the main document to refer to, it should contain all of the below and further detail: you can find it within this [summary document with information of all working groups](https://docs.google.com/document/d/1uvqALeVixK6PqdkzLFVwDVhc0fPUuBdddyfQzZsRtm4/edit?usp=sharing). | ||
|
||
(sorry for the lack of a direct link, but it lives in dropbox) | ||
|
||
## Overview | ||
|
||
The Extending Control Working group is focused on documenting and outlining possible ways in which data can be ‘shared’ across organisations - when it is not one organisation providing all parts (i.e. the data and trusted research environment). | ||
With modern IT in the cloud, | ||
with many new tools and architectures becoming mainstream, | ||
allows new options for datasets within a Secure Data Environment in the Data Zone to be made available to researchers working in the Research Zone within Trusted Research Environment facilities. | ||
|
||
This Working Groups was set up to support delivery of these overall macro concerns and objectives. | ||
|
||
- To minimise Time-to-research and delay | ||
- To make combining datasets easy and reduce barriers to research project scope | ||
- To include Citizen’s agency into the “TRE landscape” and Information Governance. | ||
|
||
## Co-chairs and contact | ||
|
||
**Chair:** This is Pete Barnsley, Francis Crick Institute, London [email protected] | ||
**Contact:** This is Pete Barnsley, Francis Crick Institute, London [email protected] | ||
|
||
## How to get involved | ||
|
||
(mailing list, slack channel, repositories…) | ||
|
||
Mailing list: [email protected] | ||
|
||
- Subscription form https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=WG-EXTENDING-CONTROL-UKTRE-COMM&A=1 | ||
|
||
Dropbox: ask for the link to existing members or Pete Barnsley, you can also find it within this you can find it within this [summary document with information of all working groups](https://docs.google.com/document/d/1uvqALeVixK6PqdkzLFVwDVhc0fPUuBdddyfQzZsRtm4/edit?usp=sharing). | ||
|
||
People interested in supporting this work should contact the primary contact or chair, or just add to the slack channel discussions. | ||
The prime contact is Pete Barnsley, Francis Crick Institute, London [email protected] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,32 @@ | ||
# Funding & Sustainability | ||
|
||
## Summary | ||
## Charter | ||
|
||
- The Funding & Sustainability working group aims to collect and share knwoledge and best practices around how to sustainably fund trusted research infrastructure. This includes making available costing models and use cases that serve as a reference. | ||
- We operate as a volunteer-based, community-driven initiative under the umbrella of the UK TRE Community Group relying on the expertise and resources contributed by our members from UK universities, research institutions, and other relevant bodies. | ||
Charter (this is the main document to refer to, it should contain all of the below and further detail): [Funding and sustainability WG](https://docs.google.com/document/d/1RMEbzt4SIeXqiYjHI-OVuDsPRJCEGThNdsnmKVmCxWE/edit?usp=sharing) | ||
|
||
## Focus areas | ||
## Overview | ||
|
||
1. Establish the UK TRE Community position on sustainable funding: through a position paper on behalf of the UK TRE Community Group towards sustained funding over adequate time horizons for TRE (software) engineering efforts and open source components supporting them | ||
2. Costing models: collect use cases and offer reference costing model(s) or benchmark(s). The WG will put together a comprehensive list of costings (at line item level), scenarios and considerations drawn from the WGs members' experience and the wider Community Group | ||
3. Charging and cost recovery models: the WG will start with existing experiences of different charging models (e.g. data access charges) and how they work in their specific environments, to try and bring this together as a reference knowledge base for the Community Group to draw on. | ||
To deliver to the UK TRE Community a summary of how different SDEs/TREs tackle these areas: | ||
|
||
## Roles and responsibilites | ||
1. Cost/charging remits for different organisations | ||
2. How important are costs and costs management currently? | ||
3. Cost categories being used | ||
4. Costing models | ||
5. Charging models - with the aim of covering costs or with a wider remit | ||
6. The value of data - how different organisations talk about the value of data, and with whom | ||
7. Monetisation / extra revenue stream ideas | ||
|
||
- Members are expected to actively participate in group discussions, share expertise and insights, propose ideas, and collaborate on initiatives. | ||
- Members are expected to commit best endeavours to completing actions for the benefit of the group as time and professional bandwidth allows. | ||
- Decisions within the group will be made collaboratively, with input from all members. Consensus-building and open dialogue will be encouraged to ensure inclusivity and transparency. | ||
## Co-chairs and contact | ||
|
||
## Duration and organisation | ||
Chairs: | ||
|
||
- This working group will operate indefinetely, although it may reassess its focus on a rolling basis and after delivery of initial outputs | ||
- The WG meets every three weeks on Friday afternoon from 13:00 - 14:00. | ||
- Rebecca Fox [email protected] | ||
- Lisa Scerri [email protected] | ||
|
||
## Get involved | ||
## How to get involved | ||
|
||
Email Fergus ([email protected]) if you would like to be part of this working group! | ||
Interested people should email [email protected] and/or request to join its mailing list | ||
|
||
Mailing list: [email protected] | ||
|
||
- Subscription form https://www.jiscmail.ac.uk/cgi-bin/wa-jisc.exe?SUBED1=FUNDING-SUST-UK-TRE-COMM&A=1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# SATRE | ||
|
||
## Charter | ||
|
||
This is the main document to refer to, it should contain all of the below and further detail: [SATRE Working group charter](https://docs.google.com/document/d/1ugd32Ki0ssZu42AWWoChE-Tb_sKggM3sfs-4ZzcYoBk/edit?usp=sharing) | ||
|
||
## Overview | ||
|
||
SATRE is a community-run group managing the Standardised Architecture for Trusted Research Environments specification. | ||
This includes developing and maintaining SATRE, | ||
working with the UK TRE community to ensure all views are taken into account, | ||
and working with institutions to evaluate their own infrastructure, or to implement SATRE. | ||
|
||
## Co-chairs and contact | ||
|
||
- Chris Cole (University of Dundee) | ||
- Martin O’Reilly (The Alan Turing Institute) | ||
- Simon Li (University of Dundee) | ||
- James Robinson (The Alan Turing Institute) | ||
- Andrew Payne (NHS England, (TBC)) | ||
- Michelle Amugi (DARE UK, TBC) | ||
|
||
**Contact** [email protected] | ||
|
||
## How to get involved | ||
|
||
(mailing list, slack channel, repositories…) | ||
|
||
Open community events advertised on the UK TRE and SDAP mailing lists, | ||
and other relevant channels. | ||
GitHub issues can be created and replied to by anyone at any time. | ||
|
||
Either open an issue on one of our GitHub repositories | ||
|
||
- https://github.com/sa-tre/satre-specification | ||
- https://github.com/sa-tre/satre-team | ||
|
||
or send an email to [email protected] | ||
|
||
Meetings and updates will be shared via the main UK TRE Community mailing list and events. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# SDE/TRE Terminology | ||
|
||
## Charter | ||
|
||
This is the main document to refer to, it should contain all of the below and further detail: you can find it within this [summary document with information of all working groups](https://docs.google.com/document/d/1uvqALeVixK6PqdkzLFVwDVhc0fPUuBdddyfQzZsRtm4/edit?usp=sharing). | ||
|
||
(sorry for the lack of a direct link, but it lives in dropbox) | ||
|
||
## Overview | ||
|
||
The SDE / TRE Definitions Working group is focused on clarifying the terms used WITHIN the UK TRE community especially when different parts are performed by different organisations. | ||
SDEs and TREs are different, but views on how and the extent to which they differ are varied. | ||
|
||
## Co-chairs and contact | ||
|
||
**Co-chair:** This is Madalyn Hardaker, Kings University, London [email protected] | ||
|
||
**Co-chair:** This is Pete Barnsley, Francis Crick Institute, London [email protected] | ||
|
||
**Contact:** This is Pete Barnsley, Francis Crick Institute, London [email protected] | ||
|
||
## How to get involved | ||
|
||
(mailing list, slack channel, repositories…) | ||
|
||
Slack: Join #wg-sde-tre-definitions in [Slack](https://join.slack.com/t/uktrecommunity/shared_invite/zt-2gep86apc-QMLyIdrC2oIIsxTRzLxUqA) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# TRE Glossary | ||
|
||
## Charter | ||
|
||
This is the main document to refer to, it should contain all of the below and further detail: [Glossary working group charter](https://docs.google.com/document/d/1Vow33Uw5FjipH2hshU_ZRfQDW-R06hosGiAWT9mp8HU/edit?usp=sharing) | ||
|
||
## Overview | ||
|
||
There is interest in a shared glossary across the TRE space to improve consistency of language, | ||
terminology and to document equivalencies of definitions and terms across organisations, | ||
although there are also plenty of existing ones out there. | ||
Our aim is to bring a number of these glossaries together, | ||
merging and reconciling as appropriate, and host the results at uktre.org. | ||
The importance of creating a unified lexicon across the TRE landscape is critical to a federated, | ||
interoperable data landscape. | ||
|
||
## Co-chairs and contact | ||
|
||
**Chairs:** | ||
|
||
- Rob Baxter (DARE UK) | ||
- Katherine (Kate) O’Sullivan (Grampian Data Safe Haven, University of Aberdeen) | ||
- Balint Stewart (DARE UK) | ||
|
||
Primary Contact: [email protected] | ||
|
||
## How to get involved | ||
|
||
(mailing list, slack channel, repositories…) | ||
|
||
Work group mailing list (open subscription, co-chair approval): [email protected] | ||
|
||
- Subscription requests should go to [email protected] | ||
|
||
To get involved, contact the co-chairs via [email protected] |