aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2018-01-24 23:02:31 -0800
committerBryan Newbold <bnewbold@robocracy.org>2018-01-24 23:02:31 -0800
commit1042de34b2cc25ea02eeb3ede39e7c8146c4b9c0 (patch)
treee5b02c535282d8c663d9a87cf41a768456704da3
parentaaea50f2248d4f7e013b01d27b0972cd8fa25d8c (diff)
downloaddat-deps-1042de34b2cc25ea02eeb3ede39e7c8146c4b9c0.tar.gz
dat-deps-1042de34b2cc25ea02eeb3ede39e7c8146c4b9c0.zip
add version changes as a motivation
-rw-r--r--proposals/0001-dep-process.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/proposals/0001-dep-process.md b/proposals/0001-dep-process.md
index d0ccf40..963ed14 100644
--- a/proposals/0001-dep-process.md
+++ b/proposals/0001-dep-process.md
@@ -43,6 +43,11 @@ which requires better coordination (process) and communication of technical
details (standards). There is also an increasing need to be legible to and
accessible to parties outside the existing Dat ecosystem.
+With growing use, the logistics of rolling out protocol changes and
+backwards-incompatible changes becomes more difficult, but at the same time
+more important to coordinate smoothly. Planning requires clear communication of
+change ahead of time.
+
A public DEP process is expected to improve coordination and planning by
setting clear expectations for documentation of protocol changes and
extensions. The technical quality of the protocol itself should be improved by