|author||intrigeri <firstname.lastname@example.org>||2019-12-26 18:36:25 +0000|
|committer||intrigeri <email@example.com>||2019-12-26 18:36:25 +0000|
A month later: - Everybody agreed, except one person whom I don't expect a reply from. - We realized that Redmine already leaks "the fact that someone (unspecified) posted a private note on an issue", so the question was actually only about the timestamp.
Diffstat (limited to 'wiki/src/blueprint/GitLab.mdwn')
1 files changed, 2 insertions, 14 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index 85f4e7d..417d083 100644
@@ -471,20 +471,8 @@ 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
- ./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.
+ It's OK to publicly leak the fact that someone (unspecified) posted
+ a private note on an issue, along with the corresponding timestamp.
* Preserve issue assignee