Skip to content

Start writing down ADR's #1344

@norberttech

Description

@norberttech

With new contributors joining the project, it might be difficult to explain all the historical decisions we made over time.
It's also not easy to remember all of those decisions over time, at this point, Flow has 26 sub-repositories.
To solve that problem all major architectural decisions should be described in ADR documents that every single contributor must follow with no exceptions.
The only way to merge a code that is against an existing ADR is to write a new ADR that overrides the previous one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions