🤔 Problem

People want to use Jupyter in their built environment instead of VSCode (namely students, who are unfamiliar with VSCode).

🍴 Appetite

3 weeks

🎯 Solution

A Jupyter front end

• possible approaches (in priority order):
  1. build pack (poster child)
     • nicest long term solution
  2. run image with jupyter
     • config jupyter kernel at launch
     • fast to write run images
  3. “hacky way” (not a build pack) is an acceptable solution
     • Tell user that Jupyter needs to be in their dependencies
     • con: issues with jupyter not installing if dependency conflict

Other notes

• Part of this pitch is establishing our development process for build packs, in addition to the end products of the build products themselves.
• Figure out how to modify the build build strategy to use a custom build pack, that is in development
• publishing pipeline is in place, from Ralf
• Q: how to connect our build packs to our builder? -Ralf looking into this during cool down(?)

🚞 User stories / journeys

🐰 Rabbit Holes

🔐 Security Implications