[theme-reviewers] Proper Copyright/License Attribution in style.css

Philip Arthur Moore philip at pressbuild.com
Sat Feb 8 21:47:37 UTC 2014

I've been mulling over a
made to _s close to a year ago that included proper copyright and
attribution in style.css.

If I recall correctly--I'm getting old so memory is fading!--a big reason for
this change was to make it
easier<https://github.com/Automattic/_s/issues/10>for the Theme Review
Team to enforce proper copyright/license attribution
for derivative works in Extend; I believe it was also done so that _s
stayed in line with GNU-recommended copyright/license attribution.

I have some questions, though:

   1. If a theme is built off of _s and submitted to Extend does the Theme
   Review Team require a notice to be put on its stylesheet that it's a
   derivative work of _s? If so, how would this look? (i.e. "Child Theme,
   Copyright 2014 Company Name, distributed under the terms of the GNU General
   Public License v2 or later, based on Underscores (Copyright 2012-2014
   Automattic, Inc.))
   2. Along the lines of the first question, what are the bare minimum
   requirements for style.css license declarations for Extend with regard to
   derivative works and/or child themes?
   3. I just read Obenland's post on Twenty
(he's awesome) and he wrote that Twenty Ten was ported over from
   Kirby, Twenty Eleven was ported over from Duster, and Twenty Fourteen was
   ported over from Further, which was developed using _s and an Automattic
   premium theme before being released to Core for inclusion. Wouldn't this
   require that Twenty Fourteen have a notice in it that it's based on _s and
   mention the Automattic copyright?

Can one of you fine folks shed some light on this for me?

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140208/b2e12db2/attachment.html>

More information about the theme-reviewers mailing list