Page MenuHomePhabricator

Create rights / licensing policy for tech blog content
Closed, ResolvedPublic


In my opinion, in alignment with our free and open source mission all blog content should be licensed under public domain or a Creative Commons Attribution.

"This license lets others remix, tweak, and build upon your work non-commercially, as long as they credit you and license their new creations under the identical terms."


Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptWed, Mar 11, 12:06 AM
Aklapper renamed this task from Create rights / licsensing policy for tech blog content to Create rights / licensing policy for tech blog content.EditedWed, Mar 11, 9:25 AM

CC BY-NC-SA shall not be used. It is non-free (because NC) and will likely collide with licenses of free media used in blog posts.
I'd recommend CC BY-SA 4.0 International.

Fair enough. Let's use that license.

srodlund closed this task as Resolved.Wed, Mar 11, 10:52 PM
srodlund claimed this task.

Added this as preferred license to documentation for the blog.

Aklapper reopened this task as Open.Wed, Mar 11, 11:40 PM

I'll boldly reopen for two issues. Hope that's alright...

Maybe because I block 3rd-party content in my browser I've only found license info on the About page of the test site, and that link has a typo (trailing |).

The "About" page currently also says "or in the public domain" (as a second option). I'd prefer to avoid that. It is legally blurry as there are numerous public domain licenses and as interpretation of that term varies by country and jurisdiction.
If there was a need for explicitly offering a second license apart from CC-BY-SA 4.0 which is considered public domain, CC-0 1.0 might be an option.
However, given that we might use media not licensed under CC-BY-SA 4.0 (a lot of content on Commons uses older CC-BY-SA versions, or some GFDL version, or CC-0, or WTFPL, etc), I'd recommend "Except where otherwise noted, content on this site is licensed under CC-BY-SA 4.0". As I think we'll need that phrase anyway.

(PS: Wishlist item, can be ignored or be a separate low priority task: Is there some technical way to see the license also on the front page and when looking at a specific post? The harder it is to find out a license, the harder it is to reuse work usually. :)

Thanks for catching the error. I will make a note of it. I like the "except where otherwise noted" language. That would provide more room to use different licenses if needed.

Right now the rights information is on the About page, but we can add a link to the footer that will appear on every page if you think this would be adequate.

Aklapper closed this task as Resolved.Tue, Mar 24, 10:52 AM

IMHO this is resolved

Aklapper updated the task description. (Show Details)Tue, Mar 24, 2:12 PM