linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: (re)licensing the wireless wiki
Date: Mon, 12 Jan 2015 12:16:00 +0100	[thread overview]
Message-ID: <1421061360.1891.21.camel@sipsolutions.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Hi,

I've been working on moving the wireless wiki over to kernel.org
infrastructure (https://wireless.wiki.kernel.org/), and we're going to
need to tag the content with an explicit license there.

As the previous wiki didn't have an explicit license, we can't do so
easily. For the new license we've selected the creative commons "by" 4.0
license: http://creativecommons.org/licenses/by/4.0/ which should have
adequate permission and protection for the existing content.

As noted on the website, this license does not apply to pages/files that
have a different explicit license, for example GPL code or firmware
tarballs uploaded to the website.

I've emailed every contributor who I could find an email address for,
but some (~40) don't have an email address and I already have a bunch of
bounces (~50). If you have contributed and haven't received a direct
email from me, please let me know separately (reply privately to the
reply-to please) - but make sure to include the username that you used.

Thanks,
Johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2015-01-12 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 11:16 Johannes Berg [this message]
2015-01-12 15:26 ` (re)licensing the wireless wiki Johannes Berg
2015-01-12 18:57   ` Pat Erley
2015-01-13 23:43     ` Nick Kossifidis
2015-01-14  7:56       ` Lorenzo Bianconi

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=1421061360.1891.21.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wireless-wiki@sipsolutions.net \
    /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;
as well as URLs for NNTP newsgroup(s).