From: Jelle Licht <jlicht@posteo.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
43796@debbugs.gnu.org
Subject: bug#43796: Privacy policy
Date: Mon, 05 Oct 2020 12:57:20 +0200 [thread overview]
Message-ID: <868scl3ppr.fsf@posteo.net> (raw)
In-Reply-To: <20201004153419.kyacfjdwmok6yybg@pelzflorian.localdomain>
Hello,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> IANAL but I think Guix needs a privacy policy for both its website and
> the Guix software in general.
Thanks for looking into this.
IANAL but I do not think it makes sense to have such a privacy policy at
this moment in time. I'd rather have a person with legal expertise look
at this situation and do the following:
1. Notice that we do need such a policy
2. Draft (or at least proof read) this policy.
The reason for this is two-fold: I think there are enough 'legal' texts
on the Internet of questionable enforcability/applicability, and doing
things this way creates a cargo-cult mentality.
Compare to the questionable habit of unconditionally adding the "The
content of this email is confidential ..."-esque spam outgoing email
(even if that mail is addressed to a public mailing list).
If others disagree in principle or in practice with me on this, that is
fine too of course :-)
- Jelle
prev parent reply other threads:[~2020-10-05 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 15:34 bug#43796: Privacy policy pelzflorian (Florian Pelz)
2020-10-04 15:56 ` Julien Lepiller
2020-10-05 9:54 ` pelzflorian (Florian Pelz)
2020-10-05 11:14 ` Julien Lepiller
2020-10-05 14:14 ` Ludovic Courtès
2020-10-05 7:09 ` bug#43796: (no subject) Tomás Ortín Fernández via Bug reports for GNU Guix
2020-10-05 13:16 ` pelzflorian (Florian Pelz)
2020-10-05 15:29 ` Tomás Ortín Fernández via Bug reports for GNU Guix
2020-10-05 19:53 ` pelzflorian (Florian Pelz)
2020-10-05 10:57 ` Jelle Licht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868scl3ppr.fsf@posteo.net \
--to=jlicht@posteo.net \
--cc=43796@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).