-
Notifications
You must be signed in to change notification settings - Fork 279
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1902 from authzed/roadmap
ROADMAP: init
- Loading branch information
Showing
1 changed file
with
57 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# SpiceDB Roadmap | ||
|
||
This document provides direction for the contribution and discovery of functionality being built for SpiceDB. | ||
|
||
Because SpiceDB is a community project and has contributions beyond the core maintainers, this document does not attempt to dictate features an ordained timeline. | ||
Instead, this document outlines the project's development philosophy and gives readers the tools to discover on-going community efforts. | ||
|
||
## Proposal Process | ||
|
||
The development of SpiceDB follows a philosophy of identifying problems, proposing solutions, and reaching agreement across relevant stakeholders BEFORE any code is written. | ||
|
||
The complexity of the problem and proposal drive just how much planning work is done. | ||
Proposals loosely follow an [RFC-style] process where anyone in the community is free to represent their opinions and use cases. | ||
|
||
If you have any questions about this process, feel free [ask in our our Discord][discord]. | ||
|
||
[RFC-style]: https://en.wikipedia.org/wiki/Request_for_Comments | ||
[discord]: https://discord.gg/spicedb | ||
|
||
### 🟣 Functionality not represented by proposals | ||
|
||
Not all contributions require in-depth proposals, but they do require consensus and an opportunity for opinions to be raised before development begins. | ||
The rest of this document does not track the development of this type of functionality, but only the larger initiatives. | ||
You can find this functionality being discussed and developed in less structured GitHub issues that are not labeled as proposal. | ||
|
||
You can find a running list of non-proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aopen+is%3Aissue+-label%3Akind%2Fproposal). | ||
|
||
### ⚪ Open Proposals | ||
|
||
Proposals can be opened by anyone at any time. | ||
|
||
Although there is no required format, a good proposal contains: | ||
|
||
- Problem statement including use cases | ||
- One or more proposed solutions | ||
- Open problems with the solution | ||
- Links to any related proposals or issues | ||
|
||
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). | ||
|
||
### 🔵 Accepted Proposals | ||
|
||
Accepted proposals have reached consensus and are ready to have someone begin implementation. | ||
|
||
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). | ||
|
||
### 🟢 Completed Proposals | ||
|
||
Completed proposals have been implemented in the past. | ||
|
||
You can find a running list of completed proposals [here](https://github.com/authzed/spicedb/issues?q=is%3Aissue+label%3Akind%2Fproposal+reason%3Acompleted). | ||
|
||
### 🔴 Rejected Proposals | ||
|
||
Rejected proposals have not reached consensus or have reached consensus not to be implemented. | ||
|
||
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). |