aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMichael Muré <batolettre@gmail.com>2022-05-31 20:20:25 +0200
committerGitHub <noreply@github.com>2022-05-31 20:20:25 +0200
commit96327c3371ca762d906209c6114092bbf552c0f4 (patch)
treecc236674c3ba003654e8708f24242a43c161644d /doc
parentd94df634667146ff854c6da04c5f22bd513c3612 (diff)
parent1c219f67698771ae3b0d1d08205263e5ba280a71 (diff)
downloadgit-bug-96327c3371ca762d906209c6114092bbf552c0f4.tar.gz
Merge pull request #806 from MichaelMure/docs
doc: more discoverable docs
Diffstat (limited to 'doc')
-rw-r--r--doc/README.md15
-rw-r--r--doc/model.md2
2 files changed, 17 insertions, 0 deletions
diff --git a/doc/README.md b/doc/README.md
new file mode 100644
index 00000000..cf9fd845
--- /dev/null
+++ b/doc/README.md
@@ -0,0 +1,15 @@
+# Documentation
+
+## For users
+
+- [data model](model.md) describe how the data model works and why.
+- [query language](queries.md) describe git-bug's query language.
+- [How-to: Read and edit offline your Github/Gitlab/Jira issues with git-bug](howto-github.md)
+
+## For developers
+
+- :exclamation: [data model](model.md) describe how the data model works and why.
+- :exclamation: [internal bird-view](architecture.md) gives an overview of the project architecture.
+- :exclamation: [Entity/DAG](../entity/dag/example_test.go) explain how to easily make your own distributed entity in git.
+- [query language](queries.md) describe git-bug's query language.
+- [JIRA bridge de v notes](jira_bridge.md) \ No newline at end of file
diff --git a/doc/model.md b/doc/model.md
index de0de42a..0aad4789 100644
--- a/doc/model.md
+++ b/doc/model.md
@@ -3,6 +3,8 @@ Entities data model
If you are not familiar with [git internals](https://git-scm.com/book/en/v1/Git-Internals), you might first want to read about them, as the `git-bug` data model is built on top of them.
+In a different format, see how you can easily make your own [distributed data structure](../entity/dag/example_test.go).
+
## Entities (bug, author, ...) are a series of edit operations
As entities are stored and edited in multiple processes at the same time, it's not possible to store the current state like it would be done in a normal application. If two processes change the same entity and later try to merge the states, we wouldn't know which change takes precedence or how to merge those states.