README.md
1# Blueprint Process
2
3Design docs are now known as blueprints. We do not intend to keep blueprints up to date once
4the implementation has been completed. The final step of a blueprint is to update documentation
5elsewhere, such as:
6 * https://github.com/storj/docs
7 * https://docs.storj.io/node
8 * https://docs.storj.io
9 * https://pkg.go.dev/storj.io/uplink
10 * Other godoc documentation, etc.
11
12Blueprints will be checked in as Markdown files in `docs/blueprints` folder.
13
14Blueprints should have an editor, at least one discussion meeting, and at least two reviewers from the architecture board.
15
16The editor is responsible for:
17* soliciting authors or authoring the document themselves,
18* scheduling discussion meetings,
19* finding reviewers,
20* posting the document in our [forum](https://forum.storj.io/c/engineer-amas/design-draft), and
21* getting the document finalized and merged
22
23The editor is also responsible for making a list of epics and tickets after the blueprint is finalized and merged. These should include archiving the blueprint when completed and updating appropriate documentation.
24
25The reviewers are responsible for reviewing the clarity and reasonableness of the document.
26
27The discussion meeting should have at least three people present. Invitees should familiarize with the document prior to the discussion. The reviewers should be present. If there are open problems after the meeting, then the meeting should be repeated.
28
29One of the reviewers must be an architecture owner, currently:
30
31* Egon (@egonelbre),
32* Kaloyan (@kaloyan-raev),
33* JT (@jtolds),
34* Jens (@littleskunk),
35* unless agreed otherwise
36
37The other reviewer should be someone with significant distributed systems expertise, currently:
38
39* Paul (@thepaul),
40* Simon (@simongui),
41* Jeff (@zeebo),
42* Matt (@brimstone),
43* unless agreed otherwise.
44
45However, it is expected that there should be feedback from the engineering team, DevOps team, data science team, UX team, QA team, and the community.
46
47## Template
48
49The blueprint uses `TEMPLATE.md` as a guide. However, it can be modified when necessary.
50
51The template has the following sections:
52
53* **Abstract** gives an overview of the blueprint and what it accomplishes. It does not go into details about the problem.
54
55* **Background** gives an overview of the background why this blueprint exists. It describes the problems the blueprint tries to solve. It describes the goals of the design.
56
57* **Design** contains the solution and its parts. The level of detail should correspond to the level of risk. The more problems a wrong solution would cause, the more detailed should be the description. The design should describe the solution to the degree it is usable by the end-user.
58
59* **Rationale** section describes the alternate approaches and trade-offs. It should be clear why the proposed design was chosen among the alternate solutions.
60
61* **Implementation** describes the steps to complete this blueprint. It should contain a rough outline of tasks. If necessary, there can be additional details about the changes to the codebase and process.
62
63* **Wrap up** describes the steps needed
64
65* **Open Issues** contains open questions that the author did not know how to solve.
66
67## Format
68
69The blueprint is intended to be read by developer contributors outside of Storj, but not the wider public. It is okay to assume some familiarity with the Storj project. Try to avoid acronyms that aren't common in the general developer community. Prefer simple sentences. Active voice is usually easier to read. Overall, be clear.
70