Skip to main content

← Back to RSE-hackathon

An RSE learning environment

The flagship challenge of the hackathon is an open, discipline-overarching environment in which people learn research software engineering by doing it — with accounts, teams, submitted artefacts, feedback and peer review around the material, not just the material itself.

Parts of this exist. Oxford RSE’s Gutenberg is an open-source platform with accounts, courses and progress tracking, and it is the natural starting point rather than a competitor. What no platform yet does is close the loop between learners — group work, artefact submission, peer assessment — or run the exercise on the hardware RSE actually targets.

This page sets out what already exists, why general-purpose learning technology does not fit RSE, and the design questions we want to attack in Glasgow. None of them is settled — that is the point of the two days.

Why not just use a normal learning platform?

Learning technology has thirty years of standards and platforms behind it, and RSE should reuse every bit of it that fits. Three things do not fit.

Notebooks are not documents

The dominant RSE teaching format is the executable notebook — Jupyter, R Markdown, Quarto. Learning management systems assume a self-contained, assessable object: a page, a video, a quiz. A notebook is none of these; it is code that must run against a real environment before it means anything.

Compute is part of the exercise

An RSE assignment is frequently about the machine: a GPU kernel, an MPI job, a SLURM batch script, a container that has to build. You cannot embed “submit this to the cluster and account for your allocation” in a quiz engine.

Results must leave again

What a course produces — lessons, worked solutions, learner artefacts — should be publishable as open educational resources and as reusable notebooks. Today it is either locked inside a course shell or published as a static site with no environment around it.

What already exists — and what it does not cover

The offerings closest to ours, and the gap each one leaves.

Environment What it offers What it does not cover
Gutenberg · Oxford RSE for UNIVERSE-HPC — GitHub, live at train.rse.ox.ac.uk
RSE and HPC training
The closest thing that exists: BSD-3 platform, self-hostable, with accounts, enrolment, pathway syllabi and results for course leaders. Content lives as Markdown in separate CC-licensed repos The learner half of the loop: no group formation, submission or peer assessment. No execution back-end, no learning-object metadata
The Carpentries · Software, Data & Library Carpentry — GitHub
Foundational computing skills
Open community lessons, instructor training, a global workshop network Lessons and workshops, not a running environment: no accounts, teams, submission or assessment
RSE-Mentopolis · RWTH Aachen / Klaus Tschira Foundation
Sustainable research software
The closest in ambition: lifecycle and stakeholder models plus teaching modules Models and modules from one institution, not software others can deploy
KODAQS Toolbox · GESIS / Mannheim / LMU — built on andrew
Social sciences: data quality
Hands-on tutorials in an open aggregation hub, plus the blended KODAQS Academy One discipline and topic, data analysis over software engineering; no group work
iBOTS / iBehave · University of Bonn — GitHub
Neuroscience
Self-paced tracks from Python and NumPy to Git and DataLad, as a static notebook site One discipline, static: no accounts, groups, feedback or assessment

Landscape as surveyed for the CHARTED dRTP proposal; all links checked 3 August 2026.

Two gaps follow, and they are exactly what the hackathon attacks:

  1. Coverage is siloed. Where teaching is hands-on, it is usually tied to one discipline’s research process or to one technology stack. Gutenberg is the instructive exception: it is discipline-neutral precisely because the content lives in separate repositories and only the engine is shared.
  2. The loop is only half closed. Gutenberg gets furthest — accounts, enrolment, completion and exercise results — but stops at what the instructor sees. None of these offerings covers group formation → artefact submission → structured feedback → peer assessment, so learners still never review each other’s code.

We build on this rather than duplicating it. Carpentries lessons and the KODAQS and iBOTS course structures are directly reusable inside such an environment — and Gutenberg is a serious candidate for the base itself: BSD-licensed, self-hostable, already carrying the accounts and course model, and missing exactly the pieces the hackathon sets out to prototype. “Extend Gutenberg” is a legitimate outcome of the two days, and arguably the cheapest route to a working thin slice.

Open design questions for the two days

  1. Metadata standards. Is any learning-object metastandard (IEEE LOM, SCORM/xAPI, H5P) applicable to RSE content? What would an RSE application profile have to add?
  2. Architecture. Federated, so institutions keep and describe their own material — or component-based, with one platform and pluggable parts? Gutenberg has already picked an answer worth arguing with: shared engine, content in separate repositories.
  3. Runnable examples. Which languages must be supported, and in book-style or notebook-style form?
  4. Compute. Where do GPU and HPC examples run, and who pays for them?
  5. Integration. How does such an environment sit alongside the learning management systems universities already run — and alongside the GitLab/GitHub instances where the code already lives?
  6. Build on, or build new? Several groups have built their own platform — Gutenberg above all, and it is open source and self-hostable. What are their perks, can they be integrated rather than replaced, and is forking Gutenberg the fastest way to a working thin slice?

The modules page breaks these down into pieces small enough to build in two days, and says what we think the two days can realistically produce.

Bring an answer — or a better question

If you have built one of these, surveyed one of these, or have strong opinions about any of the six, come and say so on day 1.

Register on Eventbrite

Or join the Matrix room first.