Skip to content

Commit

Permalink
Incorporate feedback
Browse files Browse the repository at this point in the history 
Co-authored-by: James Robinson <[email protected]>
Co-authored-by: Hari Sood <[email protected]>
  • Loading branch information
@JimMadge @jemrobinson @harisood
3 people committed Aug 23, 2023
1 parent a4c0dbb commit df681d3
Showing 1 changed file with 63 additions and 25 deletions.
88 changes: 63 additions & 25 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ <h2>Lessons Learned</h2>
<h4>The need for TREs</h4>
<!-- Why TREs? -->
<ul>
<li>The outputs of research with sensitive data could be <span class="highlight">signficiant</span></li>
<li>Huge potential<span class="highlight">benefits</span></li>
<li><span class="highlight">Enabling</span> researchers to work with sensitive data</li>
<li><span class="highlight">Enforcing</span> and <span class="highlight">encouraging</span> good security
<li>Keeping the <span class="highlight">confidence</span> of data controllers, subjects and the public</li>
Expand All @@ -75,7 +75,7 @@ <h4>The current TRE landscape</h4>
<li>Fragmented</li>
<li>Diverse approaches</li>
<li>Narrow focus</li>
<li>Beginnings of community groups</li>
<li>No TRE standard</li>
</ul>
<aside data-markdown class="notes">
- Fragmented, not coordinated
Expand All @@ -84,23 +84,23 @@ <h4>The current TRE landscape</h4>
- Variety of approaches
- TREs may be fairly bespoke, focused on a particular use or domain
- Some community groups to share expertise, coordinate, unify
- Existing standards (ISO27001, DSPT, DEA) do not make your infrastructure a TRE
</aside>
</section>
<section>
<h4>A standard architecture</h4>
<!-- Why SATRE? -->
<ul>
<li>A standard of <span class="highlight">quality</span></li>
<li>Existing standards do not define TREs</li>
<li>Owned by the <span class="highlight">community</span></li>
<li>Encourage <span class="highlight">interoperability</span></li>
<li>Define a TRE <span class="highlight">baseline</span></li>
<li>Cocreated by the <span class="highlight">community</span></li>
<li>Move towards <span class="highlight">interoperability</span></li>
</ul>
<aside data-markdown class="notes">
- A mark of quality for UK TREs
- Enable comparison across TREs
- Encourage all TREs to raise standards
- Existing standards (ISO27001, DSPT, DEA) do not make your infrastructure a TRE
- Designed by the community
- Ensure buy in
- Includes designers, operators, users
- What is important
- Balance productivity and security
Expand All @@ -113,7 +113,7 @@ <h2 class="fragment custom highlight-my-green">Our Approach</h2>
<h2>Lessons Learned</h2>
</section>
<section>
<h4>Cross-institution collaboration</h4>
<h4>Diverse collaboration</h4>
<!--
- Name the "core" institutions
- Include detail of how we make this work?
Expand All @@ -137,7 +137,7 @@ <h4>Cross-institution collaboration</h4>
<!--
Perhaps split this into cross-institutional collaboration and skill/role diversity
-->
- Lay participants
- Members of the public (Lay participants)
- Expertise in PIE
</aside>
</section>
Expand Down Expand Up @@ -175,9 +175,10 @@ <h4>Contribution governance</h4>
- Careful for overlap with Community cocreation
-->
<ul>
<li>Encourage building consensus through <span class="highlight">discussion</span> and <span class="highlight">feedback</span></li>
<li>Code of conduct to <span class="highlight">enforce</span> community standards</li>
<li>Consensus through <span class="highlight">discussion</span> and <span class="highlight">feedback</span></li>
<li>Code of conduct to enforce <span class="highlight">community standards</span></li>
<li>Clear <span class="highlight">consensus mechanism</span>
<li>Open to contributions from <span class="highlight">anyone</span></li>
</ul>
<aside data-markdown class="notes">
- Build consensus through discussion and review
Expand All @@ -188,7 +189,11 @@ <h4>Contribution governance</h4>
- Form
- Collaboration Cafés
- CoC standards reassure and welcome contributors
- Consensus mechanism avoids disputes or strong personalities controlling the process
- Consensus mechanism
- avoids disputes or strong personalities controlling the process
- helps coordinate many contributors
- lazy consensus
- explicit approval
</aside>
</section>
<section>
Expand All @@ -198,54 +203,61 @@ <h4>Community cocreation</h4>
-->
<section>
<ul>
<li><span class="highlight">Enabled</span> by working in the open and governance</li>
<li>Contributions all end up in <span class="highlight">GitHub</span></li>
<li><span class="highlight">Enabled</span> by working in the open</li>
<li>Support and recognise <span class="highlight">other</span> contribution routes</li>
<li>Team members <span class="highlight">translate</span> non-GitHub contributions to Markdown</li>
<li>Contributions all end up in <span class="highlight">GitHub</span></li>
</ul>
</section>
<section>
<iframe src="https://satre-specification.readthedocs.io/en/latest/contributing/index.html" height="450" width="800"></iframe>
</section>
<aside data-markdown class="notes">
- Enabled by working in the open
- Contributions ultimately appear in GitHub
- Contribute directly to GitHub (auditable, history, open discussions)
- Other ways to contribute
- Form
- Email
- Collaboration Cafés
- Team members/community members translate to GH items
- Contributions ultimately appear in GitHub
- Contribute directly to GitHub (auditable, history, open discussions)
- Link to next slide, events to support community contributions
</aside>
</section>
<section>
<h4>Collaborative events</h4>
<h4>Collaborative work</h4>
<!--
- How we work together, more directly
- The importance of events to promote collaboration across institutions and with the community
-->
<ul>
<li>Synchronous events help <span class="highlight">focus</span></li>
<li>Collaboration Cafés, coworking, work package meetings</li>
<li>Synchronous events help <span class="highlight">focus</span> and <span class="highlight">reach agreement</span></li>
<li>Can <span class="highlight">directly support</span> community involvement</li>
<li><span class="highlight">Collaboration Cafés</span></li>
<li>Synchronous events help <span class="highlight">forge agreement</span></li>
<li>Regular work package meetings and ad-hoc coworking</li>
<li>Asynchronous work <span class="highlight">respects time</span></li>
<li>We do <span class="highlight">both</span></li>
</ul>
<aside data-markdown class="notes">
- Collaboration Cafés foster discussion on narrow topics
- Weekly team and work package meetings
- Frequent ad-hoc coworking sessions
- Synchronous events can help focus effort on a particular topic
- Particularly important when engaging the community
- Limited time
- Unfair and unrealistic to expect long term dedication
- Weekly team and work package meetings
- Frequent ad-hoc coworking sessions
- Asynchronous work saves time
- Reply when you are available
- Different time zones and commitments
</aside>
</section>
<section>
<h4>Public engagement</h4>
</section>
<section>
<h4>Stakeholder focus</h4>
<!--
- Key stakeholders we identified, what they can bring, how we engage them
- Too much information, use transitions or multiple slides
-->
<table>
<tr>
<th>strategic stakeholders</th>
Expand Down Expand Up @@ -313,6 +325,12 @@ <h4>Leading by example</h4>
</section>
<section>
<h4>Sustainability</h4>
<!--
- We are setting ourselves up as best we can
- Open, established governance
- Established community
- However, without future funding no clear way to fund time
-->
</section>
<section>
<h2>The need for SATRE</h2>
Expand Down Expand Up @@ -381,7 +399,7 @@ <h4>Effective engagement takes effort</h4>
<li>Provide <span class="highlight">scope and context</span></li>
<li>Make <span class="highlight">good use</span> of people's time</li>
<li>Lead by example</li>
<li>Value roles like PIE, community managers, RAMs</li>
<li>Value roles like PIE officer, community managers, RAMs</li>
</ul>
<aside data-markdown class="notes">
- Our initial approach was "participant-driven", asking attendees what they wanted to talk about at events
Expand Down Expand Up @@ -423,8 +441,28 @@ <h4>Get feedback early</h4>
- Overall it saves effort as we do not invest in the wrong things
</aside>
</section>
<section>
<h3>Conclusion</h3> <!-- change this -->
<!--
- There is a need for better standardisation in TREs
- We need community consensus and buy in for this to work
- We thought hard about how to achieve this
- We designed the project to enable this
- We have learned from mistakes
- We learned what works particular well
- We encourage any project to adopt what worked well whenever community involvement is important
-->
</section>
<section>
<h3>Acknowledgements</h3>
<!--
- DARE UK
- UKRI via the DARE UK Phase 1 driver projects programme (SATRE)
- Turing ELA funds for DSH redirected
- Same for Dundee?
- The project team
- ALL contributors
-->
</section>
</div>
</div>
Expand Down

0 comments on commit df681d3

Please sign in to comment.