Workshops Guidance

Workshops can be on any topic of interest to the research software engineering community. We welcome both hands-on and discussion-only workshops. Last year’s conference included workshops as varied as a hands-on tutorial in profiling GPU code with NVVP, an introduction to using Jupyter Notebooks for reproducible research and a discussion about the international RSE community – see the full list of 2017 workshops.

Each session will be assigned a volunteer who will be available to provide technical assistance and an extra pair of hands during the session. All attendees will be bringing their own laptops, and there will be virtual machines created for the conference that will allow the hands-on tutorials to be run across all of their different operating systems.

Themes

Good practice for software development

Topics relevant to developing maintainable, verifiable and accessible software for reproducible research — code documentation & user guides, maintainability, version control, testing, etc

Researcher-developer partnership

Topics related to the critical close collaboration between developers and researchers to facilitate relevant, novel and reproducible research from software solutions — conceptualising software solutions from specifications, meeting user requirements, validation & verification, communication skills, etc.

Software engineering toys, tips and tricks

Sessions introducing a new language, library, module, approach, methodology etc. For example new techniques or tools for data processing and analysis, HPC systems and parallel programming.

Community and careers

Discussions around the RSE community and how we can grow and improve it. An opportunity to learn from RSE groups worldwide and share your own experiences.

 

Workshop format

Timing

All workshops will be 90 minutes long. It is important to get the right balance between establishing the background for the workshop and leaving enough time for the attendees to have a go (hands-on workshops) or make their contribution (discussion workshops). We recommend setting  aside 5-10 minutes at the start to introduce the workshop and 10 minutes at the end to wrap-up and, where appropriate, point to other resources. The bulk of the workshop should be focused on attendees participation — if you would plan to spend more than half of the time talking to the audience then consider submitting as a talk instead. If required, plan for not more than 5 minutes at the start of the workshop for preparing attendees’ laptops (downloads, registering for accounts online, etc).

Resources

The attendees are expected to use their own laptops for the hands-on workshops and VMs including required software will be provided at the conference. Any software or material you provide for the tutorial must be compatible with the Linux distribution and aim to use less than 250 MB of space. If it is possible to do so, keep materials local rather than requiring continuous access to network resources during the workshop.

Planning your submission

When submitting your proposal, you will need to specify the following details

Topic and abstract

  • Both the topic and the abstract will be published on the conference website.

Audience

  • Would your target audience be required to have any prerequisite skills/background knowledge e.g. knowledge of a particular language?
  • What size audience can your workshop accommodate? The rooms can accommodate between 10 and 60 people. Note there will be one conference volunteer assigned to each workshop, but you may need to find additional helpers for a large class. We recommend at least one person per 15 attendees.

Outcomes

  • How will your attendees benefit from the workshop? It might be useful to include a list of skills that your users will be able to perform by the end of the workshop.
  • Will there be anything generated as a result of the workshop? For example, a google doc/blog post for a discussion workshop or a set of answers or reference for a hands on workshop.

Resources

  • Hands-on workshops:
    • Will your workshop be able to run locally off the VM with no internet requirement?
    • Will continuous access to a networked resource be required for the workshop? If so, will you need specific ports open on the firewall? These must be supplied at least 8 weeks before the conference.
    • Will the attendees need to perform any action before the workshop (download, register for an account etc)
  • Discussion workshops:
    • Does the workshop require any stationery (Flipcharts, etc.)
    • Does the workshop require a specific room layout?

How to submit a proposal

Just a short form

The initial proposal submission is via this form and follows the format outlined above.