WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#27104 closed defect (bug) (invalid)

Twenty Fourteen: Add Proper Copyright/License Attribution in style.css

Reported by: philiparthurmoore Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9
Component: Bundled Theme Keywords:
Focuses: docs Cc:

Description

Currently Twenty Fourteen lacks proper documentation to show that it has come from either _s or Further, which are both Copyrighted to Automattic Inc. The WordPress Theme Review Team makes it clear that any themes submitted to the repository that are child themes or derivative works of some sort should include proper attribution, for example:

Theme Name, Copyright 2014 Company Name,
distributed under the terms of the GNU General Public License v2 or later,
based on "Parent" Work Name (Copyright 2014 "Parent" Company Name)

Currently Twenty Fourteen doesn't include proper attribution for _s, or Further (which was based on _s), which is Copyrighted to Automattic:

/*
Theme Name: Twenty Fourteen
Theme URI: http://wordpress.org/themes/twentyfourteen
Author: the WordPress team
Author URI: http://wordpress.org/
Description: In 2014, our default theme lets you create a responsive magazine website with a sleek, modern design. Feature your favorite homepage content in either a grid or a slider. Use the three widget areas to customize your website, and change your content's layout with a full-width page template and a contributor page to show off your authors. Creating a magazine website with WordPress has never been easier.
Version: 1.0
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Tags: black, green, white, light, dark, two-columns, three-columns, left-sidebar, right-sidebar, fixed-layout, responsive-layout, custom-background, custom-header, custom-menu, editor-style, featured-images, flexible-header, full-width-template, microformats, post-formats, rtl-language-support, sticky-post, theme-options, translation-ready, accessibility-ready
Text Domain: twentyfourteen

This theme, like WordPress, is licensed under the GPL.
Use it to make something cool, have fun, and share what you've learned with others.
*/

At a minimum the theme should include Automattic's name with _s and/or Further.

Change History (9)

#1 follow-up: @obenland
6 years ago

I wonder where that chain end, too. :) Twenty Fourteen > Further > _s > Toolbox, and I'm sure it goes on beyond that.

#2 in reply to: ↑ 1 @philiparthurmoore
6 years ago

Replying to obenland:

I wonder where that chain end, too. :) Twenty Fourteen > Further > _s > Toolbox, and I'm sure it goes on beyond that.

ian-support: Anyway, so Twenty Ten > Toolbox > Duster > Twenty Eleven and then I reviewed Toolbox for improvements after Twenty Eleven launched and then Toolbox > _s

Link for the curious.

#3 @philiparthurmoore
6 years ago

Relevant commit for the explicit mention of Further: [24832].

#4 follow-up: @iandstewart
6 years ago

It goes MUCH further, Philip and Konstantin. I won't even list it, it's almost silly how long it would be. If we did add this to Twenty Fourteen somewhere I would only go one level in.

#5 in reply to: ↑ 4 @philiparthurmoore
6 years ago

Replying to iandstewart:

It goes MUCH further...

I see what you've done here.

Completely agreed about one level in.

#6 @jenmylo
6 years ago

Technically, _s is not a parent theme, and themes built using it as a starting point are not child themes (I have heard that so many times I say it in my sleep).

I think this opens a bigger debate about crediting earlier work, forking, and putting private company attributions into WordPress.org files (the overlap of personnel is not lost on me). Did we credit Theme Foundry when Drew designed a default theme? Did we credit Ian's Kirby when Ian was asked to contribute it to core? I would argue that in this case, a decision was made to contribute the use of _s to core/the project because that's what the folks working on the theme wanted to work on, and did it knowing how contributing to the default theme works (i.e., you get credit as a contributor, but if you reuse code you made before, your company doesn't get credit for that).

Default themes are special, and a little bit different (IMO) than privately created themes that we host in the directory.

#7 @philiparthurmoore
6 years ago

_s isn't a parent theme but works created using it are absolutely derivative works.

See: https://github.com/Automattic/_s/issues/10

Commit [24832] is very explicit about Twenty Fourteen being a derivative work of Further, which is (C) Automattic.

I think this is a matter of adhering to clear rules set forth by the GPL, not about themes being special or not.

Last edited 6 years ago by philiparthurmoore (previous) (diff)

#8 @jcastaneda
6 years ago

So why limit to just Twenty Fourteen and add the other core themes as well? Curious.

#9 @lancewillett
6 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Default themes aren't parent works. They are a mix of original code, derivative work from previous default themes — and cases like Twenty Fourteen, Twenty Eleven, and Twenty Ten — derivative work of another theme for which the copyright holder has directly contributed to the WordPress project under GPLv2, like any other patch or contribution.

Note: See TracTickets for help on using tickets.