moar why #1
moar why #1
Conversation
| ### breaking down the problem | ||
|
|
||
| There are five major sets of problems that need to be addressed: | ||
|
|
||
| 1. Framing and hermetic execution and fileset-slinging core |
There was a problem hiding this comment.
This sentence doesn't make a lot of sense and needs more clarity.
What is framing? I'm going to make an assumption that it means the composability of file sets
| 1. Framing and hermetic execution and fileset-slinging core | |
| 1. Fileset transport: Content addressable filesets can be discovered, fetched, and verified. | |
| 2. Framing: File sets can be composed together into a working tree. | |
| 3. Hermetic execution: Transformations to the working tree are executed with minimal side-effects. The primary side-effect should be the specified file set export. |
There was a problem hiding this comment.
Yeah something like this change is getting closer... the "slinging" part in particular is a hangover from an earlier flippant draft >.<
The idea I had in mind with "Framing" is to start building up a contrast between "build tools" and "framing tools" -- maybe "framing" aka "workspace" -- generally trying to get at the idea that we want to make general purpose contains-anything systems rather than getting into the nitty-gritty of every individual thing that gets built. Urban planning vs pouring concrete, maybe; some idea like that. So composing filesets is part of it, but I'd like to make it more general as well.
(Maybe this is a lot of work to try to make one word do, so early in this intro-audience document...)
I'll cook on this in the back of my mind for a while longer and then probably take most of this diff you propose, but if you get additional ideas, also jot em :)
| There are five major sets of problems that need to be addressed: | ||
|
|
||
| 1. Framing and hermetic execution and fileset-slinging core | ||
| 2. Coordination systems for connecting graphs of executions and outputs -- both for authoring graphs of intent, and then precipitating graphs of actual outcome (which can be repeated). |
There was a problem hiding this comment.
Would calling this "pipelines" be useful here? I feel it's a good word that people should know in the context of existing CI systems already in use.
No description provided.