From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 85212C4363D for ; Tue, 22 Sep 2020 13:49:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D96132395B for ; Tue, 22 Sep 2020 13:49:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lechevalier.se header.i=@lechevalier.se header.b="up4bh/6P" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726623AbgIVNts (ORCPT ); Tue, 22 Sep 2020 09:49:48 -0400 Received: from mailrelay3-3.pub.mailoutpod1-cph3.one.com ([46.30.212.12]:23996 "EHLO mailrelay3-3.pub.mailoutpod1-cph3.one.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726473AbgIVNtr (ORCPT ); Tue, 22 Sep 2020 09:49:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lechevalier.se; s=20191106; h=content-transfer-encoding:content-type:in-reply-to:mime-version:date: message-id:from:references:to:subject:from; bh=O/uMd1a9X1pttMwgLjT++HiEl2Pjj+FDCTlVIDGKfCs=; b=up4bh/6PEKQoflydw54bt9oeBxG+NP11gLJJGG+LR4aH0ARkC7liuHuy5kP0sXCtsFQc6upTPnSXe ZYYc6CVHnXe2FcwSS/6/W0MkYFktI7hOQs6rkuqremZXbcR0MfW0h4MmlQpGpR50uDwq1MC4lgBjBH cHbdVmSQ0j8BJrvtzNKH+zFfzfV10wPi13bzrJaxt73SBymxlgqleWWaJk36UUZfYJo1pFbDQf5Yd4 xlOEsrhLUSZxEKOjUHoQbimxI42ffsCrLz2riHAJ5P5tVumWasxNH3oViNsxUuDcJG+eRySpQ0lu06 zfsOLS4mi5NjF2RNU4ZB7EMFbTf8g9g== X-HalOne-Cookie: 2e5b11af2cd89f12ff83e50b613da05dc3b01a88 X-HalOne-ID: 78a908d0-fcda-11ea-a7fd-d0431ea8bb03 Received: from [10.0.155.198] (unknown [98.128.186.115]) by mailrelay3.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id 78a908d0-fcda-11ea-a7fd-d0431ea8bb03; Tue, 22 Sep 2020 13:49:44 +0000 (UTC) Subject: Re: Btrfs wiki lincese and GDPR notices? To: dsterba@suse.cz, linux-btrfs@vger.kernel.org References: <20200921181834.GO6756@twin.jikos.cz> From: A L Message-ID: Date: Tue, 22 Sep 2020 15:49:44 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20200921181834.GO6756@twin.jikos.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org 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.