diff options
| author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2019-07-26 17:53:36 +0100 |
|---|---|---|
| committer | Carsten Schoenert <c.schoenert@t-online.de> | 2019-07-29 19:38:20 +0200 |
| commit | 046b4e1ac260f60c17fe0ef8688be0b9b92b933e (patch) | |
| tree | 9b3479b510da342e3dbff3a091cef480618689ae /english/legal | |
| parent | 787273489cc89eb024be64287018d9c54a81d476 (diff) | |
privacy: improve, correct, and expand discussion of git
Diffstat (limited to 'english/legal')
| -rw-r--r-- | english/legal/privacy.wml | 34 |
1 files changed, 28 insertions, 6 deletions
diff --git a/english/legal/privacy.wml b/english/legal/privacy.wml index 374d34b6bfe..bdef1cabc23 100644 --- a/english/legal/privacy.wml +++ b/english/legal/privacy.wml @@ -116,12 +116,34 @@ account.</p> <h2><a name="git">git</a></h2> -<p>Due to the technical nature of git contributions to the git repositories -held on salsa will contain the name and email address recorded within those git -commits. The chained nature of the git system means that any modification to -these commit details once they are incorporated into the repository is -extremely disruptive and in some cases (such as when signed commits are in use) -impossible.</p> +<p>Debian maintains multiple git servers, containing source code and +similar materials, and their revision and contribution histories. +Individual Debian contributors also typically +have information managed in git.</p> + +<p>git history contains the name and email address of contributors +(including bug reporters, authors, reviewers, and so on). +git retains this information permanently in an append-only history. +We use an append-only history because it has important integrity +properties, notably significant protection against untracked changes. +We retain it indefinitely so that we can always verify the copyright +and other legal status of contributions, and so that we can always +identify the originators for software integrity reasons. + +<p>The append-only nature of the git system implies that that any +modification to these commit details once they are incorporated into +the repository is extremely disruptive and in some cases (such as when +signed commits are in use) impossible. So we avoid this in all but +extreme cases. +Where appropriate, we use git features (eg <code>mailmap</code>) +to arrange that historical personal information, though it is retained, +can be elided or corrected when it is displayed or used. +</p> + +<p>Unless there are exceptional reasons to do otherwise, +Debian's git histories, +including the associated personal information about contributors, +are completely public.</p> <h2>Gobby (<a href="https://gobby.debian.org/">gobby.debian.org</a>)</h2> |