Skip to content

Commit

Permalink
Reorder table blur fragments
Browse files Browse the repository at this point in the history
  • Loading branch information
@JimMadge
JimMadge committed Aug 28, 2023
1 parent 0763c87 commit 29d2255
Showing 1 changed file with 61 additions and 64 deletions.
125 changes: 61 additions & 64 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -236,22 +236,21 @@ <h3>Contribution Governance</h3>
- Why we made those decisions, how they support contribution
- Careful for overlap with Community cocreation
-->
<ul>
<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>
<section>
<ul>
<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>
</section>
<section>
<iframe src="https://satre-specification.readthedocs.io/en/latest/contributing/index.html" height="500" width="1000"></iframe>
</section>
<aside data-markdown class="notes">
- Build consensus through discussion and review
- Discussion issues
- PRs require approval
<!--
- Non-PR/Markdown ways to contribute
- Change issue template
- Form
- Collaboration Cafés
-->
- CoC standards reassure and welcome contributors
- Consensus mechanism
- avoids disputes or strong personalities controlling the process
Expand All @@ -261,43 +260,7 @@ <h3>Contribution Governance</h3>
- Link:
- This kind of governance enables contribution
- However, it does not guarantee it
- You can help by supporting contributors
</aside>
</section>
<section>
<h3>Community Cocreation</h3>
<!--
- How contributions from the community are supported and welcomed
- Could also fit with PIE
-->
<section>
<ul>
<li><span class="highlight">Enabled</span> by working in the open</li>
<li><span class="highlight">Support and recognise</span> other contribution routes</li>
<li>Team members <span class="highlight">translate</span> non-GitHub contributions to Markdown</li>
<li>Contributions all end up on <span class="highlight">GitHub and the site</span></li>
</ul>
</section>
<section>
<iframe src="https://satre-specification.readthedocs.io/en/latest/contributing/index.html" height="500" width="1000"></iframe>
</section>
<aside data-markdown class="notes">
- Enabled by working in the open
- Critical for us to support those who don't use GitHub
- Other ways to contribute
- Form
- Email
- Collaboration Cafés (shared note taking)
- Public engagement events
- Team members/community members translate to GH items
- Contributions ultimately appear in GitHub and the specification site
- Contribution routes are all valid
- Maintains history
<!--
- Link:
- Providing routes and supporting contributors is critical
- We can enhance this by actively engaging people
-->
- We have spoken about the rules, but not how we work
</aside>
</section>
<section>
Expand All @@ -324,7 +287,40 @@ <h3>Collaborative Work</h3>
- Reply when you are available
- Different time zones and commitments
- Link:
- None
- Events and asynchronous tools, particularly collaboration cafés, help us engage people
- Many of these people will want to contribute
- We need to support them contributing
- In particular, many are unfamiliar with GitHub
</aside>
</section>
<section>
<h3>Community Cocreation</h3>
<!--
- How contributions from the community are supported and welcomed
-->
<ul>
<li><span class="highlight">Enabled</span> by working in the open</li>
<li><span class="highlight">Support and recognise</span> other contribution routes</li>
<li>Team members <span class="highlight">translate</span> non-GitHub contributions to Markdown</li>
<li>Contributions all end up on <span class="highlight">GitHub and the site</span></li>
</ul>
<aside data-markdown class="notes">
- Enabled by working in the open
- Critical for us to support those who don't use GitHub
- Not everyone is 'technical' and knows how
- Not reasonable to expect everyone to learn
- Other ways to contribute
- Form
- Email
- Collaboration Cafés (shared note taking)
- Public engagement events
- Team members/community members translate to GH items
- Contributions ultimately appear in GitHub and the specification site
- Contribution routes are all valid
- Maintains history
- Link:
- We have engaged and enabled collaborations from enthusiastic people
- We also worked to actively approach important stakeholder groups
</aside>
</section>
<section>
Expand All @@ -337,18 +333,18 @@ <h3>Stakeholder Focus</h3>
<th style="text-align: center">strategic stakeholders</th>
<th style="text-align: center">builders and operators</th>
<th style="text-align: center">users</th>
</tr><tr class="fragment custom blur">
<td style="text-align: center">influential organisations</td>
<td style="text-align: center">make or run TREs</td>
<td style="text-align: center">work in TREs</td>
</tr><tr class="fragment custom blur">
<td style="text-align: center">set requirements</td>
<td style="text-align: center">technical and process experts</td>
<td style="text-align: center">focus on productivity</td>
</tr><tr class="fragment custom blur">
<td style="text-align: center">direct engagement</td>
<td style="text-align: center">collaboration cafés, GitHub</td>
<td style="text-align: center">user testing sessions</td>
</tr><tr>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="1">influential organisations</td>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="4">make or run TREs</td>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="7">work in TREs</td>
</tr><tr>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="2">set requirements</td>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="5">technical and process experts</td>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="8">focus on productivity</td>
</tr><tr>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="3">direct engagement</td>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="6">collaboration cafés, GitHub</td>
<td style="text-align: center" class="fragment custom blur" data-fragment-index="9">user testing sessions</td>
</tr>
</table>
<aside data-markdown class="notes">
Expand Down Expand Up @@ -424,9 +420,10 @@ <h3>Leading by Example</h3>
</div>
</div>
<aside data-markdown class="notes">
- We follow the governance and contribution guidelines (maybe not the real point of this slide)
- We follow the governance and contribution guidelines
- We should collaborate on an equal footing with others
- Dundee and Turing are completing self evaluations
- Demonstrate how evaluation works
- Demonstrate how evaluation works (to help others)
- Holding ourselves to our own standards
- Being honest about our strengths and weaknesses
- Commitment to reduce the gap between our TREs and the standard
Expand Down

0 comments on commit 29d2255

Please sign in to comment.