diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2018-01-19 22:46:26 -0800 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2018-01-19 22:46:26 -0800 |
| commit | f60c8465ad0eb12ac1b08e7f55a5b4b9922f605d (patch) | |
| tree | a41f8ac6d27e08ce2ed8bb5c951ecfb3b1f82210 | |
| parent | 8a264d3393e226f13e220ac9185b946d6d69129b (diff) | |
| download | dat-deps-f60c8465ad0eb12ac1b08e7f55a5b4b9922f605d.tar.gz dat-deps-f60c8465ad0eb12ac1b08e7f55a5b4b9922f605d.zip | |
clarify unresolved status
| -rw-r--r-- | proposals/0001-dep-process.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/proposals/0001-dep-process.md b/proposals/0001-dep-process.md index 6d3dae9..75051d2 100644 --- a/proposals/0001-dep-process.md +++ b/proposals/0001-dep-process.md @@ -293,18 +293,18 @@ designing the DEP process: # Unresolved questions [unresolved]: #unresolved-questions -What is the specific decision making process for accepting or rejecting a given -DEP? Optimistically, it would be clear from reading a PR discussion thread -whether "consensus" has been reached or not, but this might be ambiguous or -intimidating to first-time contributors ("Tyrany of the Structureless"). +How is Working Group membership defined in the long run? This could be the +topic of a follow-on Process DEP while this DEP is in Draft status.. The intention is to retroactively document the entire Dat protocol in the form -of DEPs, but a specific plan for this hasn't been worked out yet. +of DEPs, but a specific plan for this hasn't been worked out yet. This is +expected to be tackled by the Working Group while this DEP is in Draft status. How mutable should Draft Standards DEPs be over time? What about Process DEPs? Should there be an additional status ("Living"?) for DEPs that are expected to evolve, or is this against the whole philosophy of having specific stable -documents to reference? +documents to reference? This is expected to be decided while this DEP is in +Draft status. # Changelog [changelog]: #changelog |