Skip to content

Commit c50701a

Browse files
authored
Merge pull request #1902 from authzed/roadmap
ROADMAP: init
2 parents ac76892 + f7fcdbc commit c50701a

File tree

1 file changed

+57
-0
lines changed

1 file changed

+57
-0
lines changed

ROADMAP.md

+57
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# SpiceDB Roadmap
2+
3+
This document provides direction for the contribution and discovery of functionality being built for SpiceDB.
4+
5+
Because SpiceDB is a community project and has contributions beyond the core maintainers, this document does not attempt to dictate features an ordained timeline.
6+
Instead, this document outlines the project's development philosophy and gives readers the tools to discover on-going community efforts.
7+
8+
## Proposal Process
9+
10+
The development of SpiceDB follows a philosophy of identifying problems, proposing solutions, and reaching agreement across relevant stakeholders BEFORE any code is written.
11+
12+
The complexity of the problem and proposal drive just how much planning work is done.
13+
Proposals loosely follow an [RFC-style] process where anyone in the community is free to represent their opinions and use cases.
14+
15+
If you have any questions about this process, feel free [ask in our our Discord][discord].
16+
17+
[RFC-style]: https://en.wikipedia.org/wiki/Request_for_Comments
18+
[discord]: https://discord.gg/spicedb
19+
20+
### 🟣 Functionality not represented by proposals
21+
22+
Not all contributions require in-depth proposals, but they do require consensus and an opportunity for opinions to be raised before development begins.
23+
The rest of this document does not track the development of this type of functionality, but only the larger initiatives.
24+
You can find this functionality being discussed and developed in less structured GitHub issues that are not labeled as proposal.
25+
26+
You can find a running list of non-proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aopen+is%3Aissue+-label%3Akind%2Fproposal).
27+
28+
### ⚪ Open Proposals
29+
30+
Proposals can be opened by anyone at any time.
31+
32+
Although there is no required format, a good proposal contains:
33+
34+
- Problem statement including use cases
35+
- One or more proposed solutions
36+
- Open problems with the solution
37+
- Links to any related proposals or issues
38+
39+
You can find a running list of open proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aopen+label%3A%22state%2Fneeds+discussion%22%2C%22state%2Fgauging+interest%22).
40+
41+
### 🔵 Accepted Proposals
42+
43+
Accepted proposals have reached consensus and are ready to have someone begin implementation.
44+
45+
You can find a running list of accepted proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fproposal+label%3A%22state%2Fimplementation+ready%22).
46+
47+
### 🟢 Completed Proposals
48+
49+
Completed proposals have been implemented in the past.
50+
51+
You can find a running list of completed proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aissue+label%3Akind%2Fproposal+reason%3Acompleted).
52+
53+
### 🔴 Rejected Proposals
54+
55+
Rejected proposals have not reached consensus or have reached consensus not to be implemented.
56+
57+
You can find a running list of rejected proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aissue+label%3A%22state%2Fwon%27t+fix%22+label%3Akind%2Fproposal).

0 commit comments

Comments
 (0)