[taler-taldir] branch master updated: start pp generation

[gnunet]

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository taldir.

The following commit(s) were added to refs/heads/master by this push:
     new 21bc8c3  start pp generation
21bc8c3 is described below

commit 21bc8c34d91005d75f66f5080064996947dbbe1c
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Tue Jul 12 17:59:29 2022 +0200

    start pp generation
---
 contrib/Makefile     |  26 ++++++
 contrib/pp/Makefile  | 109 +++++++++++++++++++++++++
 contrib/pp/README    |  58 ++++++++++++++
 contrib/pp/pp.rst    | 222 +++++++++++++++++++++++++++++++++++++++++++++++++++
 contrib/update-pp.sh |  28 +++++++
 5 files changed, 443 insertions(+)

diff --git a/contrib/Makefile b/contrib/Makefile
new file mode 100644
index 0000000..ffbeadf
--- /dev/null
+++ b/contrib/Makefile
@@ -0,0 +1,26 @@
+# This Makefile.am is in the public domain
+# Process this file with automake to produce Makefile.in
+
+SUBDIRS = .
+
+# English (en)
+tosendir=$(datadir)/anastasis/tos/en
+
+# English (en)
+ppendir=$(datadir)/anastasis/pp/en
+
+# Change the set of supported languages here. You should
+# also update tos'XX'data and EXTRA_DIST accordingly.
+TOS_LANGUAGES="en"
+PP_LANGUAGES="en"
+
+# Change the terms-of-service version (Etag) to generate here!
+# This value should be incremented whenever there is a substantive
+# change in the original text (but not for the translations).
+TOS_VERSION=0
+PP_VERSION=0
+
+update-tos:
+       VERSION=$(TOS_VERSION) ./update-tos.sh $(TOS_LANGUAGES)
+update-pp:
+       VERSION=$(PP_VERSION) ./update-pp.sh $(PP_LANGUAGES)
diff --git a/contrib/pp/Makefile b/contrib/pp/Makefile
new file mode 100644
index 0000000..ab29543
--- /dev/null
+++ b/contrib/pp/Makefile
@@ -0,0 +1,109 @@
+# Makefile for Sphinx documentation
+#
+# You can set these variables from the command line.
+SPHINXOPTS    =
+SPHINXBUILD   = sphinx-build
+PAPER         =
+BUILDDIR      = _build
+
+# User-friendly check for sphinx-build
+ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
+$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx 
installed, then set the SPHINXBUILD environment variable to point to the full 
path of the '$(SPHINXBUILD)' executable. Alternatively you can add the 
directory with the executable to your PATH. If you don't have Sphinx installed, 
grab it from http://sphinx-doc.org/)
+endif
+
+# Internal variables.
+PAPEROPT_a4     = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+# the i18n builder cannot share the environment and doctrees with the others
+I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+
+.PHONY: help clean html json epub latex latexpdf text man doctest gettext
+
+help:
+       @echo "Please use \`make <target>' where <target> is one of"
+       @echo "  html       to make a single large HTML file"
+       @echo "  json       to make JSON files"
+       @echo "  epub       to make an epub"
+       @echo "  latex      to make LaTeX files, you can set PAPER=a4 or 
PAPER=letter"
+       @echo "  pdf        to make LaTeX files and run them through pdflatex"
+       @echo "  txt        to make text files"
+       @echo "  man        to make manual pages"
+       @echo "  texinfo    to make Texinfo files"
+       @echo "  info       to make Texinfo files and run them through makeinfo"
+       @echo "  gettext    to make PO message catalogs"
+       @echo "  xml        to make Docutils-native XML files"
+       @echo "  pseudoxml  to make pseudoxml-XML files for display purposes"
+       @echo "  doctest    to run all doctests embedded in the documentation 
(if enabled)"
+
+clean:
+       rm -rf $(BUILDDIR)/*
+
+
+# The html-linked builder does not support caching, so we
+# remove all cached state first.
+html:
+       $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
+       @echo
+       @echo "Build finished. The HTML page is in $(BUILDDIR)/html."
+
+json:
+       $(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
+       @echo
+       @echo "Build finished; now you can process the JSON files."
+
+epub:
+       $(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
+       @echo
+       @echo "Build finished. The epub file is in $(BUILDDIR)/epub."
+
+latex:
+       $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+       @echo
+       @echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
+       @echo "Run \`make' in that directory to run these through (pdf)latex" \
+             "(use \`make latexpdf' here to do that automatically)."
+
+pdf:
+       $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/pdf
+       @echo "Running LaTeX files through pdflatex..."
+       $(MAKE) -C $(BUILDDIR)/pdf all-pdf
+       @echo "pdflatex finished; the PDF files are in $(BUILDDIR)/pdf."
+
+txt:
+       $(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/txt
+       @echo
+       @echo "Build finished. The text files are in $(BUILDDIR)/txt."
+
+man:
+       $(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+       @echo
+       @echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+texinfo:
+       $(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+       @echo
+       @echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
+       @echo "Run \`make' in that directory to run these through makeinfo" \
+             "(use \`make info' here to do that automatically)."
+
+info:
+       $(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/info
+       @echo "Running Texinfo files through makeinfo..."
+       make -C $(BUILDDIR)/texinfo info
+       @echo "makeinfo finished; the Info files are in $(BUILDDIR)/info."
+
+gettext:
+       $(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
+       @echo
+       @echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
+
+doctest:
+       $(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
+       @echo "Testing of doctests in the sources finished, look at the " \
+             "results in $(BUILDDIR)/doctest/output.txt."
+
+xml:
+       $(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
+       @echo
+       @echo "Build finished. The XML files are in $(BUILDDIR)/xml."
diff --git a/contrib/pp/README b/contrib/pp/README
new file mode 100644
index 0000000..5aae822
--- /dev/null
+++ b/contrib/pp/README
@@ -0,0 +1,58 @@
+This directory contains the privacy policy (template) for TalDir
+operators.
+
+
+Dependencies
+============
+
+Generating a new Privacy Policy requires Sphinx, LaTeX with babel
+packages for all supported languages.  On Debian, you should
+at least install:
+
+$ apt install python3-sphinx sphinx-intl texlive-lang-german 
texlive-lang-english
+
+(NOTE: List may be incomplete.)
+
+
+Updating the Privacy Policy
+===========================
+
+The master file with the Privacy Policy is 'pp.rst'.
+
+If you make substantial changes, you MUST change the "PP_VERSION"
+in contrib/Makefile.am to the new Etag.
+
+To begin the translation into other languages after editing the master
+file, run
+
+$ make gettext
+
+to generate the master PO file. Then, run
+
+$ sphinx-intl update -p _build/locale/ -l de -l fr -l it
+
+to update the PO files for the various languages (extend the list of
+languages as necessary). The PO files for the translators are kept
+at locale/$LANG/LC_MESSAGES/pp.po for the language $LANG.
+
+Once all PO files have been updated with new translations, run
+
+$ make update-pp
+
+in the "contrib/" directory to generate all of the formats.  The
+respective make rule calls the '../update-pp.sh' script in the
+contrib/ directory, which calls the 'Makefile' in the pp/
+directory for the various supported languages and file formats
+and then moves the generated files to the target directory
+('contrib/pp/$LANG/$VERSION.$FORMAT')
+
+
+Adding a new language
+=====================
+
+To add a new language $LANG, add $LANG to "PP_LANGUAGES" in
+'contrib/Makefile.am' and run
+
+$ sphinx-intl update -p _build/gettext -l $LANG
+
+to generate the PO template.
diff --git a/contrib/pp/pp.rst b/contrib/pp/pp.rst
new file mode 100644
index 0000000..acb2d8c
--- /dev/null
+++ b/contrib/pp/pp.rst
@@ -0,0 +1,222 @@
+Privacy Policy
+==============
+
+Last Updated: 12.07.2022
+
+This Privacy Policy describes the policies and procedures of GNUnet e.V.
+(“we,” “our,” or “us”) pertaining to the collection, use, and
+disclosure of your information on our sites and related mobile
+applications and products we offer (the “Services”). This Privacy
+Statement applies to your personal data when you use our Services, and
+does not apply to online websites or services that we do not own or
+control.
+
+
+Overview
+--------
+
+Your privacy is important to us. We follow a few fundamental
+principles: We don’t ask you for personally identifiable information
+(defined below). That being said, your contact information, such as
+your phone number, social media handle, or email address (depending on
+how you contact us), may be collected when you communicate with us,
+for example to report a bug or other error related to TalDir. We
+don’t share your information with third parties except when strictly
+required to deliver you our Services and products, or to comply with
+the law. If you have any questions or concerns about this policy,
+please reach out to us at taldir@gnunet.org.
+
+
+How you accept this policy
+--------------------------
+
+By using our Services or visiting our sites, you agree to the use, disclosure,
+and procedures outlined in this Privacy Policy.
+
+
+What personal information do we collect from our users?
+-------------------------------------------------------
+
+The information we collect from you falls into two categories: (i) personally
+identifiable information (i.e., data that could potentially identify you as an
+individual) (“Personal Information”), and (ii) non-personally identifiable
+information (i.e., information that cannot be used to identify who you are)
+(“Non-Personal Information”). This Privacy Policy covers both categories and
+will tell you how we might collect and use each type.
+
+We do our best to not collect any Personal Information from TalDir
+users.  The detailed Personal Information TalDir asks from you
+during the regular registration process at the beginning is
+processed to verify that your are actually the holder of a certain account.
+The information is never stored in plain text and only used to create a
+cryptographic account identifier which does not allow us to recover any of your
+details.
+
+That being said, when using our Services to register a mapping from your
+identity to a wallet, we may inherently receive the following information
+(depending on your choice of authentication method):
+
+   * Your phone number when using SMS authentication. We rely on third party 
providers (such as your mobile network operator) to deliver the SMS to you. 
These third parties will see the SMS message sent to you and could thus learn 
that you are using TalDir. SMS is inherently insecure, and you should expect 
many governments and private parties to be able to observe these messages.  
However, we do not store your phone number for SMS communication on our 
systems, except maybe in short-term  [...]
+
+   * Your e-mail address when using E-mail authentication. We rely on the 
Internet and your E-mail provider to deliver the E-mail to you. Internet 
service providers will see the E-mail message sent to you and could thus learn 
that you are using TalDir. E-mail is inherently insecure, and you should expect 
many governments and private parties to be able to observe these messages.  
However, we do not store your E-mail address on our systems, except maybe in 
short-term logs to diagnose errors.
+
+   * Your twitter handle when using Twitter authentication. We rely on Twitter 
to deliver a message to you. Twitter will see the message sent to you and could 
thus learn that you are using TalDir. Twitter is inherently insecure, and you 
should expect many governments and private parties to be able to observe these 
messages.  However, we do not store your twitter handle on our systems, except 
maybe in short-term logs to diagnose errors.
+
+   * When you contact us. We may collect certain information if you choose to 
contact us, for example to report a bug or other error with the Taler Wallet. 
This may include contact information such as your name, email address or phone 
number depending on the method you choose to contact us. We strictly only use 
the information provided by you in these instances to answer your request or to 
deliver the services requested by you.
+
+
+How we collect and process personal data
+--------------------------------------
+
+We may process your personal data for the following reasons:
+
+   * to authenticate you during registration
+   * to support you using Taldirs when you contact us
+
+
+How we share and use the information we gather
+----------------------------------------------
+
+We may share your authentication data with other providers that assist
+us in performing the authentication. We will try to use providers that
+to the best of our knowledge respect your privacy and have good
+privacy practices.  We reserve the right to change authentication
+providers at any time to ensure availability of our services.
+
+We primarily use the limited information we receive directly from you to
+enhance TalDir. Some ways we may use your Personal Information are
+to: Contact you when necessary to respond to your comments, answer your
+questions, or obtain additional information on issues related to bugs or
+errors with the TalDir application that you reported.
+
+
+Agents or third party partners
+------------------------------
+
+We may provide your Personal Information to our employees, contractors,
+agents, service providers, and designees (“Agents”) to enable them to perform
+certain services for us exclusively, including: improvement and maintenance of
+our software and Services.
+
+
+Protection of us and others
+---------------------------
+
+We reserve the right to access, read, preserve, and disclose any information
+that we reasonably believe is necessary to comply with the law or a court
+order.
+
+
+What personal information can I access or change?
+-------------------------------------------------
+
+You can request access to the information we have collected from
+you. You can do this by contacting us at taldir@gnunet.org. We will
+make sure to provide you with a copy of the data we process about
+you. To comply with your request, we may ask you to verify your
+identity. We will fulfill your request by sending your copy
+electronically. For any subsequent access request, we may charge you
+with an administrative fee. If you believe that the information we
+have collected is incorrect, you are welcome to contact us so we can
+update it and keep your data accurate. Any data that is no longer
+needed for purposes specified in the “How We Use the Information We
+Gather” section will be deleted after ninety (90) days.
+
+
+What are your data protection rights?
+-------------------------------------
+
+GNUnet e.V. would like to make sure you are fully aware of all of your
+data protection rights. Every user is entitled to the following:
+
+**The right to access**: You have the right to request GNUnet e.V. for
+ copies of your personal data. We may charge you a small fee for this
+ service.
+
+**The right to rectification**: You have the right to request that
+GNUnet e.V. correct any information you believe is inaccurate. You also
+have the right to request GNUnet e.V. to complete information you
+believe is incomplete.  The right to erasure - You have the right to
+request that GNUnet e.V. erase your personal data, under certain
+conditions.
+
+**The right to restrict processing**: You have the right to request
+ that GNUnet e.V. restrict the processing of your personal data, under
+ certain conditions.
+
+**The right to object to processing**: You have the right to object to
+ GNUnet e.V.'s processing of your personal data, under certain
+ conditions.
+
+**The right to data portability**: You have the right to request that
+ GNUnet e.V. transfer the data that we have collected to another
+ organization, or directly to you, under certain conditions.
+
+If you make a request, we have one month to respond to you. If you
+would like to exercise any of these rights, please contact us at our
+email: taldir@gnunet.org
+
+You can always contact your local data protection authority to enforce
+your rights.
+
+
+Data retention
+--------------
+
+Information entered into our bug tracker will be retained indefinitely
+and is typically made public. We will only use it to triage the
+problem.  Beyond that, we do not retain personally identifiable
+information about our users for longer than one week.
+
+
+Data security
+-------------
+
+We are committed to making sure your information is protected. We employ
+several physical and electronic safeguards to keep your information safe,
+including encrypted user passwords, two factor verification and authentication
+on passwords where possible, and securing connections with industry standard
+transport layer security. You are also welcome to contact us using GnuPG
+encrypted e-mail. Even with all these precautions, we cannot fully guarantee
+against the access, disclosure, alteration, or deletion of data through
+events, including but not limited to hardware or software failure or
+unauthorized use. Any information that you provide to us is done so entirely
+at your own risk.
+
+
+Changes and updates to privacy policy
+-------------------------------------
+
+We reserve the right to update and revise this privacy policy at any time. We
+occasionally review this Privacy Policy to make sure it complies with
+applicable laws and conforms to changes in our business. We may need to update
+this Privacy Policy, and we reserve the right to do so at any time. If we do
+revise this Privacy Policy, we will update the “Effective Date” at the top
+of this page so that you can tell if it has changed since your last visit. As
+we generally do not collect contact information and also do not track your
+visits, we will not be able to notify you directly. However, TalDir clients
+may inform you about a change in the privacy policy once they detect that the
+policy has changed. Please review this Privacy Policy regularly to ensure that
+you are aware of its terms. Any use of our Services after an amendment to our
+Privacy Policy constitutes your acceptance to the revised or amended
+agreement.
+
+
+International users and visitors
+--------------------------------
+
+Our Services are (currently) hosted in Germany. If you are a user
+accessing the Services from Switzerland, Asia, US, or any other
+region with laws or regulations governing personal data collection,
+use, and disclosure that differ from the laws of Germany, please be
+advised that through your continued use of the Services, which is
+governed by the law of the country hosting the service, you are
+transferring your Personal Information to Germany and you consent to
+that transfer.
+
+
+Questions
+---------
+
+Please contact us at taldir@gnunet.org if you have questions about our
+privacy practices that are not addressed in this Privacy Statement.
diff --git a/contrib/update-pp.sh b/contrib/update-pp.sh
new file mode 100755
index 0000000..db31ba1
--- /dev/null
+++ b/contrib/update-pp.sh
@@ -0,0 +1,28 @@
+#!/bin/sh
+# This file is in the public domain
+
+# Should be called with the list of languages to generate, i.e.
+# $ ./update-pp.sh en de fr it
+
+# Error checking on
+set -eu
+echo "Generating PP for ETag $VERSION"
+
+rm -f sphinx.log sphinx.err
+# We process inputs using Makefile in tos/ directory
+cd pp
+for l in $@
+do
+    mkdir -p $l
+    echo Generating PP for language $l
+    # 'f' is for the supported formats, note that the 'make' target
+    # MUST match the file extension.
+    for f in html txt pdf epub xml
+    do
+        rm -rf _build
+        echo "  Generating format $f"
+        make -e SPHINXOPTS="-D language='$l'" $f >>sphinx.log 2>>sphinx.err < 
/dev/null
+        mv _build/$f/pp.$f $l/${VERSION}.$f
+    done
+done
+cd ..

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.