🤔 Problem

In order to support teaching on Renku 2.0, we need a way for an instructor to create a task template, and for a student to take that template and work on it.

More specifically, this pitch is targetting teaching use cases where:

graph TD
  Save[Do student need to be able to save their work?]
  Git[Are students comfortable using git branches?]
  UCNoSave[Single Renku project, students start sessions but don't save work]
  UCBranches[Single project, shared repo, students work on branches]
  Pitch[This pitch!]
  Save -->|no| UCNoSave
  Save -->|yes| Git
  Git -->|yes| UCBranches
  Git -->|no| Pitch

If you’d like to read more context about the teaching use cases we are working with, please see the user flows described in ‣.

🍴 Appetite

6 weeks

🎯 Solution

The core of the solution here is to provide a way for a student to make their own copy of an instructor’s Renku project so they can modify it. We imagine the following flow:

What does copying a project do exactly?

Copying a project makes a new Renku project in the namespace of the user’s choice.

The copied project links together all the same components as the original:

User Selected: