New Version Planning

As we're still getting started, please feel free to insert notes and comments where you like - just try to avoid changing or deleting things you yourself didn't write. We'll come up with a shared structure as we go. Also consider using the "discussion" tab at the top if you aren't sure where to comment or want to have a dialogue.

These items at the top are on the agenda for discussion, but don't have a clear place they belong yet:

• POST handler/API reachability
• Chat capability
• Containers
• NSJail, chroot?
• Physical systems: controlled via ordinary SSH, provisioned with PXE or other net boot methods?
• How to model shared resources and contention?
• Staged/prerequisite content in guide/scenario
• How to refer to observation/logging instruments

Functional requirements:

• 20-300 students simultaneously? Semi-simultaneously? ~150 concurrently, 500+ at large institutions?
• Telemetry layer for instrument/orchestration health
• Students are provided a learning environment that is safe to explore/attack without threatening the application host infrastructure

Ubiquitous language:

(See What is Ubiquitous Language? | Agile Alliance, Cosmic Python or DDD Resources - Domain Language)

• Scenario
• Learning objectives
  • e.g.
    • "Students will be able to use ls to list the contents of a directory"
    • "Students will be able to log in to the exercise via SSH"
  • Milestone
• Questions (are exercises distinct?)
• Guide
  • Guide section
• Student
• Instructor
• Hint
• Intervention
• Prediction
• Learning environment
• Observability/instrumentation? (Name?)