From e6c1b9f09ab350c506bb8ccb479bc47426ca2291 Mon Sep 17 00:00:00 2001
From: mrodzis <weidling@sub.uni-goettingen.de>
Date: Wed, 10 Apr 2019 09:08:56 +0200
Subject: [PATCH] Mark undiscussed questions

---
 rdd-technical-reference.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rdd-technical-reference.md b/rdd-technical-reference.md
index 4d9846b..fd413b2 100644
--- a/rdd-technical-reference.md
+++ b/rdd-technical-reference.md
@@ -122,9 +122,9 @@ Call diagrams can be useful to follow code and service calls and should be exist
 
 - example for Java: <https://lab.sub.uni-goettingen.de/self-updating-docs.html>
 
-- links to callers? who is calling this method, and when?
+- TODO discuss: links to callers? who is calling this method, and when?
 
-- meet and write documentation together regularly (documentation sprint)?
+- TODO discuss: meet and write documentation together regularly (documentation sprint)?
 
 - document REST-APIs using [openAPI](https://github.com/OAI/OpenAPI-Specification) if possible. OpenAPI docs should be located at /doc/api on servers
 
-- 
GitLab