Goal

Enso has been designed with support for extensible

• library repositories
• editions

These features aren't however used when releasing recent versions of Enso. Instead, libraries like Strava support are being stuffed into Standard namespace of libraries. Such a system doesn't scale as delivering high quality APIs for every niché problem is too time consuming and requires too high effort.

Instead: Let's get (existing) system for delivering non-Standard libraries working!

Step 1: Local Deployment

• create a project to compute something simple - factorial?
• package it and expose it via HTTP(S) server running on local machine
• create another pristine project
  • use editor to import the factorial functionality
• verify the imported function can be invoke and computes the right result
  • do this for CLI as well as GUI
• document necessary code changes and exact steps needed to reproduce the demo

Step 2: Changes to the Release Process

• once the "local scenario" is working propose what needs to be changed to make a library like that part of release
  • perform necessary changes
  • built nightly release
• demonstrate a library missing on disk can be downloaded and used as in the "local scenario" case
• Step 2 is tracked in Change release process to upload custom edition #14469