From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Changes to the website according to the new GDPR legislation
Date: Wed, 25 Apr 2018 11:03:47 +0100 [thread overview]
Message-ID: <1524650627.2479471.13.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Hello guys,
I guess you have seen it by now that there is a lot of fuzz and panic about the
new GDPR. We are slightly affected by this as well and therefore I have been
investigating what we need to do to be compliant.
The website needs the following things changed:
https://git.ipfire.org/?p=ipfire.org.git;a=commitdiff;h=77a085ed3f2e0444ba6f7d292ee039cc021664a9
This just updates the disclaimer and adds a few clauses about data protection
and what we are doing with the data. This applies mainly to the support forums.
This also needs to be ported to the new website design, which I can do shortly.
Sven's development branch unfortunately has a few merge issues with the master
branch and I need a little time to sort this out.
The other thing that we probably do not need to change because of legal
restrictions, but is a good idea anyways is to serve *all* additional JS, CSS
and fonts locally. That reduces the amount of data that is being collected by
Google Fonts and other CDNs so that we protect our users from that. The
additional time the website needs to load is not too bad and should be
acceptable over privacy.
Just wanted to keep you folks updated about this.
If anybody else knows anything that we are not doing right about GDPR yet and we
need to change, please let me know.
Best,
-Michael
next reply other threads:[~2018-04-25 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 10:03 Michael Tremer [this message]
2018-04-25 11:07 ` Horace Michael
2018-04-25 12:04 ` Michael Tremer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1524650627.2479471.13.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox