From: A L <mail@lechevalier.se>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs wiki lincese and GDPR notices?
Date: Tue, 22 Sep 2020 15:49:44 +0200 [thread overview]
Message-ID: <fe9dc70f-25fc-978d-eab8-c40d5e2105b0@lechevalier.se> (raw)
In-Reply-To: <20200921181834.GO6756@twin.jikos.cz>
On 2020-09-21 20:18, David Sterba wrote:
> Hi,
>
> On Sun, Sep 20, 2020 at 11:03:07AM +0200, A L wrote:
>> Under what license are the content and uploaded images and documents on
>> https://btrfs.wiki.kernel.org/
> I think nobody has asked this question until now, so I don't know.
No worries. I was curious because I had an idea to re-use some text and
images on a personal blog.
I think it is common for MediaWiki platforms to be setup so that
user-provided content is under the Creative Commons
Attribution-ShareAlike Licence unless otherwise stated. For example an
image might be uploaded with CC0 or some other license while the text is
CC-BY-SA or GPL. For example, the XFS wiki ( https://xfs.wiki.kernel.org
) is using this approach.
Perhaps it is worth considering adding this to the Btrfs wiki?
>> For example, file have no copyright or license information:
>> https://btrfs.wiki.kernel.org/index.php/File:Send_subvol_command.png
>> https://btrfs.wiki.kernel.org/index.php/File:Fs-tree.svg
>>
>> Currently the "Privacy Policy" and "About" pages are empty. There is
>> also no GDPR information.
> All the wikis fall under the Linux foundation policies regarding
> accounts, so the GDPR questions better be directed there
> (https://korg.docs.kernel.org/wiki.html,
> https://korg.docs.kernel.org/support.html).
Thanks for the links. I note that in general, it seems that GDPR
implementations, and especially GDPR info for FOSS is lacking in a many
communities and projects. kernel.org does not have a GDPR notice, for
example.
prev parent reply other threads:[~2020-09-22 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 9:03 Btrfs wiki lincese and GDPR notices? A L
2020-09-21 18:18 ` David Sterba
2020-09-22 13:49 ` A L [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe9dc70f-25fc-978d-eab8-c40d5e2105b0@lechevalier.se \
--to=mail@lechevalier.se \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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