summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/GitLab.mdwn
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2019-12-27 19:32:26 +0000
committerIkiWiki <ikiwiki.info>2019-12-27 19:32:26 +0000
commit51828b65f6ab4d012abc812c76c29eb27ff2149b (patch)
tree6bd5b4f243d923a27f55304d694b2c953b70486a /wiki/src/blueprint/GitLab.mdwn
parent82dbbd4b21c91476d3d9d7835dbcac6ed9f78137 (diff)
This reverts commit 49a62720ff88c1f0c52fb14a9ff1551b8b733f88
Diffstat (limited to 'wiki/src/blueprint/GitLab.mdwn')
-rw-r--r--wiki/src/blueprint/GitLab.mdwn16
1 files changed, 14 insertions, 2 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index 417d083..85f4e7d 100644
--- a/wiki/src/blueprint/GitLab.mdwn
+++ b/wiki/src/blueprint/GitLab.mdwn
@@ -471,8 +471,20 @@ Tails community.
It looks like GitLab does not support private comments.
- It's OK to publicly leak the fact that someone (unspecified) posted
- a private note on an issue, along with the corresponding timestamp.
+ 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 config.py --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