otto/rfc
R Tyler Croy cf53ae42dd Start working on providing steps with per-step cache that they can utilize
This is going to first be used with the `git` step to ensure that it can cache
clones between pipeline runs without hitting the network

See #40
2020-11-19 20:59:50 -08:00
..
.gitignore Sketching out my current thoughts on how the resource auction should work 2019-12-29 12:45:54 -08:00
0001-otto-systems-design.adoc Clean up some other RFCs 2020-11-04 21:15:02 -08:00
0002-execution-manifest.adoc Clean up some other RFCs 2020-11-04 21:15:02 -08:00
0003-resource-auctioning.adoc Add an RFC describing the decision to use JSON over HTTP for the data format and transport 2020-01-07 21:43:16 -08:00
0005-json-over-http.adoc Clean up some other RFCs 2020-11-04 21:15:02 -08:00
0010-eventbus.adoc Checkpointing some work in progress 2020-10-16 20:47:21 -07:00
0011-step-library-format.adoc Start working on providing steps with per-step cache that they can utilize 2020-11-19 20:59:50 -08:00
README.adoc Clean up some other RFCs 2020-11-04 21:15:02 -08:00
template.adoc Add an rfc/ directory for some design documents 2019-02-16 13:22:24 -08:00

README.adoc

<html lang="en"> <head> </head>

Otto RFCs

This directory contains design documents related to the design and implementation of Otto.

It loosely follows the process used for Python Enhancement Proposals.

RFCs

Below is the list of RFCs:

Number Title Status

0001

Otto System Design

Draft 💬

0002

Execution Manifest

Not Submitted

0003

Resource allocation by auction

Draft 💬

0005

JSON over HTTP for data serialization and transport

Draft 💬

0010

Eventbus design and implementation

Not Submitted

0011

Step library packaging format

Draft 💬

Statuses

  • Not Submitted - Still half-baked.

  • Draft 💬 - Mostly baked and needing review.

  • Deferred - Put on the back-burner.

  • Accepted 👌 - Officially canon.

  • Rejected

  • Withdrawn

  • Final 🔒

  • Replaced 🗡️ - superceded by a later RFC.

  • Active 😄 - Implemented.

</html>