minor Greek updates

1 files changed, 51 insertions, 7 deletions

diff --git a/greek/legal/privacy.wml b/greek/legal/privacy.wml
index 0e77271213a..896c5027cbd 100644
--- a/greek/legal/privacy.wml
+++ b/greek/legal/privacy.wml
@@ -1,5 +1,5 @@
 #use wml::debian::template title="Privacy Policy" NOCOMMENTS="yes"
-#use wml::debian::translation-check translation="3c6ffb2bcd885b73ca6311b72caa3ab54fdaeea1" maintainer="galaxico"
+#use wml::debian::translation-check translation="ff33ae94f697922cdcdc5ed2b51cb697838b8eb9" maintainer="galaxico"
 
 ## Translators may want to add a note stating that the translation 
 ## is only informative and has no legal value, and people
@@ -113,12 +113,38 @@ system, but guests may also register for an account and will have to provide
 name and email details in order to facilitate the setup and use of that
 account.</p>
 
-<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>salsa's primary purpose is to manage our git history.  See below.<p>
+
+<h2><a name="git">git</a></h2>
+
+<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>
 
@@ -222,6 +248,24 @@ address is required for the purposes of providing a mechanism for account
 password reset, and notifying the user of any changes on pages they are
 subscribed to.</p>
 
+<h2>dgit git server (<a href="https://browse.dgit.debian.org/">*.dgit.debian.org</a>)</h2>
+
+<p>The dgit git server is the repository of the git (revision control)
+histories of packages uploaded to Debian via <code>dgit
+push</code>, used by <code>dgit clone</code>.
+It contains similar information to the Debian
+archive and the Salsa gitlab instance: copies of (and past snapshots
+of) of the same information - in git format.
+Except for packages which are being first-time reviewed by Debian
+ftpmasters for inclusion in Debian: all this git information is always
+public, and retained forever.
+See <a href="#git">git</a>, above.<p>
+
+<p>For access control purposes, there is a hand-maintained list of the
+ssh public keys of Debian Maintainers who have asked to be added.
+This manually maintained list is not public.  We hope to retire it and
+instead use complete data maintained by another Debian service.</p>
+
 <h2>Echelon</h2>
 
 <p>Echelon is a system used by the Project to track member activity; in