python-tuf/docs/adr
Joshua Lock 3877e24346
ADR-0009: document purpose of ref implementation (#1547)
Capture discussion around the purpose of the reference implementation.
That we prioritise being an exemplary implementation over being a
pedagogical implementation.

Signed-off-by: Joshua Lock <jlock@vmware.com>
2021-08-30 13:27:45 -04:00
..
0000-use-markdown-architectural-decision-records.md docs/adr: start to keep ADRs in MADR format 2020-10-26 16:26:52 +00:00
0001-python-version-3-6-plus.md ADR0001: clarify when/where Python 3.6+ is expected 2020-10-27 11:25:42 +00:00
0002-pre-1-0-deprecation-strategy.md ADR0002: document deprecation strategy post 1.0 2020-11-24 15:26:51 +00:00
0003-where-to-develop-TUF-1-0-0.md ADR003: Add pros and cons of the options 2020-11-27 12:26:52 +02:00
0004-extent-of-OOP-in-metadata-model.md ADR0004: Justify extent of OOP in metadata model 2020-11-30 14:59:56 +01:00
0005-use-google-python-style-guide.md Add style guide usage instructions to ADR0005 2020-12-04 10:50:36 +01:00
0006-where-to-implemenent-model-serialization.md ADR0006: Where to implement model serialization 2021-03-18 10:57:27 +01:00
0008-accept-unrecognised-fields.md Document ADR 0008 about unrecognized fields 2021-04-14 13:51:55 +03:00
0009-what-is-a-reference-implementation.md ADR-0009: document purpose of ref implementation (#1547) 2021-08-30 13:27:45 -04:00
index.md ADR-0009: document purpose of ref implementation (#1547) 2021-08-30 13:27:45 -04:00
template.md docs/adr: start to keep ADRs in MADR format 2020-10-26 16:26:52 +00:00