path: root/wiki/src/blueprint/GitLab.mdwn
diff options
authorintrigeri <>2019-11-20 13:31:38 +0000
committerintrigeri <>2019-11-20 13:36:09 +0000
commit7b70007a7e9d6f770ebf31541477935186bf8a7c (patch)
tree228171de11e26cfca2d5f11d9722d47694edf2c0 /wiki/src/blueprint/GitLab.mdwn
parent088de2df96f2ca12d73b02872ccbaea47808c153 (diff)
GitLab: plans for private notes
Diffstat (limited to 'wiki/src/blueprint/GitLab.mdwn')
1 files changed, 15 insertions, 0 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index dd7d1e8..f88abd5 100644
--- a/wiki/src/blueprint/GitLab.mdwn
+++ b/wiki/src/blueprint/GitLab.mdwn
@@ -466,6 +466,21 @@ Tails community.
It looks like GitLab does not support private comments.
+ XXX (intrigeri): check if it's OK to publicly leak the fact that
+ someone (unspecified) posted a private note on an issue, along with
+ the corresponding timestamp. To list all private notes, grouped by
+ user:
+ ./redlab discuss --verbose -C --private-notes
+ - 2019-11-20: asked the 10 affected users if they consent with leaking
+ this information publicly.
+ If folks don't consent to this infoleak, we'll add a link from the
+ GitLab issue description to the privately archived Redmine, and to
+ follow an old discussion, one may want to systematically follow this
+ link to ensure they did not miss a private note.
* Preserve issue assignee
It is acceptable to require assignees to manually create their