Skip to content

Commit

Permalink
remove ADR files from the server
Browse files Browse the repository at this point in the history
Signed-off-by: R.I.Pienaar <[email protected]>
  • Loading branch information
ripienaar committed Jul 13, 2021
1 parent 16b4206 commit 0601a36
Show file tree
Hide file tree
Showing 11 changed files with 1 addition and 1,024 deletions.
20 changes: 1 addition & 19 deletions doc/README.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,3 @@
# Architecture Decision Records

The directory [adr](adr) hold Architecture Decision Records that document major decisions made
in the design of the NATS Server.

A good intro to ADRs can be found in [Documenting Architecture Decisions](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions) by Michael Nygard.

## When to write an ADR

Not every little decision needs an ADR, and we are not overly prescriptive about the format.
The kind of change that should have an ADR are ones likely to impact many client libraries
or those where we specifically wish to solicit wider community input.

## Format

The [adr-tools](https://github.com/npryce/adr-tools) utility ships with a template that's a
good starting point. We do not have a fixed format at present.

## ADR Statuses

Each ADR has a status, let's try to use `Proposed`, `Approved` `Partially Implemented`, `Implemented` and `Rejected`.
The NATS ADR documents have moved to their [own repository](https://github.com/nats-io/nats-architecture-and-design/)
155 changes: 0 additions & 155 deletions doc/adr/0001-jetstream-json-api-design.md

This file was deleted.

183 changes: 0 additions & 183 deletions doc/adr/0002-nats-typed-messages.md

This file was deleted.

Loading

0 comments on commit 0601a36

Please sign in to comment.