python-tuf/docs/adr
Lukas Puehringer b5252fed65 ADR0005: Decide on python code style guide
Use Google style guide with refinements, because the Google style
guide is a comprehensive, well-established style guide that is
mostly based on PEP-8 and was accepted by everyone on the TUF team.

There is no need to replicate these recommendations. However, we do
provide a very slim document with additional refinements, in order
to emphasize on items the we consider especially important, want to
be handled differently, or in one specific way, where the Google
guide would allow multiple.

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Co-authored-by: Joshua Lock <jlock@vmware.com>
2020-12-04 10:39:24 +01: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 ADR0005: Decide on python code style guide 2020-12-04 10:39:24 +01:00
index.md ADR0005: Decide on python code style guide 2020-12-04 10:39:24 +01:00
template.md docs/adr: start to keep ADRs in MADR format 2020-10-26 16:26:52 +00:00