CW21 Outputs and Outcomes¶
Outputs¶
Recordings of the sessions shared via the SSI Youtube channel
Blog posts from the discussion session
- Implementing FAIR for research software: attitudes, advantages and challenges (part one)
- Implementing FAIR for research software: attitudes, advantages and challenges (part two)
- What are the formats, tools and techniques for harvesting metadata from software repositories?
- A path to the light: stopping ‘secret’ software, managing maintenance and evidencing impact
- Top tips for teaching what’s REALLY important
- Nudging towards a better default for open source project ownership
- Evolving the office work culture
- How do we improve data management in machine learning?
- Coding Clubs For Research Software Communities: Questions to Consider (Part One)
- Coding Clubs For Research Software Communities: Questions to Consider (Part Two)
- Six tips for building communities of practice
- How do you help build intermediate software engineering skills and help people go beyond the basics?
- Talk to each other!
Collaborative Ideas documents
- User centred design principles for research apps / citizen science
- Research Software Sustainability Concordat
- Dugnads for Research
- Escape room: Translating between RSEs and Arts & Humanities Researchers (Part 1) (3rd place winners)
- Coding Confessions
- Acknowledging maintenance and software retirement: Software End of Project Plans (1st place winners)
- DEPTH: Developer error/problem treasure hunt!
- Improving data visualization literacy
- Using Raspberry Pis to deliver Carpentries training in remote locations (tied 2nd place winners)
- Software citation videos (to understand why and how to make your software citable)
- The Adventurous Architect - A Blueprinter for Research Software Skills
- ConnECT ProjECT - an Exciting Collaboration Tool for discovering project similarities!
- Skills wheel for RSEs
- Bursting the Bubble: Teaching PIs the value of good code (tied 2nd place winners)
- Open Source Covid Analysis of References (OSCAR)
Mini-workshop and demo session documents
- 1.1 Interactive Introduction to the FAIR Research Software discussion
- 1.2 The RSE landscape: Central, service, embedded, academic - what is your RSE type, and how do you want to develop it?
- 1.3 README tips to make your project more approachable
- 1.4 How FAIR is your research software?
- 1.5 (Do not) make it new: On Reusing Research Software and Tools in Digital Humanities Scholarship
- 2.1 Tips and traps on the road to FAIR software principles
- 2.2 Good Practices for Designing Software Development Projects (The Turing Way)
- 2.3 Promoting code review for research software: feedback from the Oxford Code Review Network
- 2.4 PresQT – Services to Improve Re-use and FAIRness of Research Data and Software
- 2.5 Opening Closed Data - Exploring new models for stewardship of sensitive data
Hack Day projects
- HowDescribedIs
- Coding Confessions (2nd place winners)
- Research Dugnads (tied 3rd place winners)
- Escape room
- CarpenPi (1st place winners)
- Habeas Corpus (tied 3rd place winners)
- Software Twilight
- GitHub repository (spawn a Binder session to see it in action)
- Collaborative notes
- Credit All
- Exploring past CW ideas (special mention)
All slides and other outputs shared via the Figshare conference portal
- Keynote presentation slides
- Panel presentation slides
- Lightning talk slides (x20)
- Mini-workshop and demo session presentation slides or outputs (x5)
Collaborative notes documents and other unconference infrastructure resources shared
Feedback into Event Organisation Guide (this In Practice on CW21)
Any sponsor outputs (e.g. Tweets, videos, etc.)
Outcomes¶
Facilitation of new collaborations between participants
- Feedback from CW21 participants included that 28.6% of respondants met more than 15 new people at the workshop, 68.6% of respondants started 1-2 collaborations based on conversations at the workshop, and 80% of respondants intend to carry on working on the idea they developed at the CW21 Hack Day.
Increased accessibility and inclusion
- Feedback on the use of live transcription and captioning from participants included: “I am an non-native english speaker; reading helps with understanding”, “I have a slight hearing impairment which sometime makes it difficult for me to follow a conversation. I like being able to use the transcription.” and “It is super helpful to be able to go back to a sentence if I misheard anything”.
Community members who are unable to attend the event are still able to engage with the discussion
Impact on virtual events run by others through influencing and informing how they run their virtual events and reuse of infrastructure resources
- After experiencing the use of Gather.Town at CW21, SSI Fellow Emma Rand used the platform to facilitate Software Sustainability training for Bioscience Postgraduate students
Ease of running a virtual CW again in the future
- We are able to run CW22 following the same process detailed within this In Practice on CW21 and reuse organisational and infrastructure resources with minor modifications