I am confused as to how this theme is licensed Creative Commons Attribution 2.5 by it's author, but you are releasing it as GPL v2+ on Drupal.org.

Here is the original theme URL, http://www.styleshout.com/templates/preview/Colourise11/index.html.

It's a great theme and all, and I use it on one of my sites even, but I just saw the theme available on the author's website and it's license.

Please explain.

Thanks

Comments

yashadev’s picture

Colourise is a free, W3C-compliant, CSS-based website template by styleshout.com. This work is distributed under the Creative Commons Attribution 2.5 License, which means that you are free to use and modify it for any purpose. All I ask is that you give me credit by including a link back to my website.

Also, it states

You are free:

to Share — to copy, distribute and transmit the work
to Remix — to adapt the work
to make commercial use of the work

I'm not sure how the whole licensing process works.. But does the above change anything? Or does this theme have to be removed?

yashadev’s picture

Status: Active » Fixed

I have contacted the maintainer of the project. The whole code is written from scratch, the only things that were "borrowed" from the original author of the theme, was the main central picture (in the header) and the idea of the theme. Also, the credit is given to the original author. There aren't many dark themes on Drupal that look nice and classy. So if having the picture would still be a problem, we could ask the user to download manually after downloading the theme. Let me know if that is needed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

avpaderno’s picture

Title: Is this really a GPL v2+ theme » Is this really a GPL v2+ theme?
Project: Colourise » Drupal Licensing Working Group
Version: 6.x-2.1 »
Component: Code » Violation
Issue summary: View changes
avpaderno’s picture

Status: Closed (fixed) » Active
kreynen’s picture

@kiamlaluno why are you re-opening this? It took years of banging our heads against the bureaucracy that Drupal has become to get https://www.drupal.org/git-repository-usage-policy changed to specifically state...

Any non-code content—including but not limited to assets like fonts, icons, images, etc—may be submitted to the repository under any license to which the user has the rights. The packaging or distribution of GPL-incompatible non-code assets "in aggregate" with GPL code is explicitly permitted in the final stipulation of Sec 3, Clause 2 of the GPL:

avpaderno’s picture

I simply moved the issue to the correct queue. If there isn't anything to do, it can be closed.

kreynen’s picture

Status: Active » Closed (works as designed)

You didn't just change the project queue. You changed the status of an issue that had been Closed (fixed) 6+ years ago to Active in https://www.drupal.org/project/drupal_lwg/issues/1136172#comment-12871632

Please stop moving issues from old, abandoned projects into the LWG queue. This is not helpful.

avpaderno’s picture

I apologize: I didn't know there was a time limit for support about possible violations on the code submitted on drupal.org repositories.

gisle’s picture

Component: Violation » Miscellaneous

kiamlaluno wrote:

I didn't know there was a time limit for support about possible violations on the code submitted on drupal.org repositories.

There isn't. For the record: You (and anyone else) are welcome to post (or move) reports here. It is the task of the LWG to sort these reports out. People should not be wary of posting here.

However, in this case, there is no license vialotation. As indicated in #2, the PHP-code is written from scratch and licensed here under GPL2+, and the non-code content is licensed under CC BY 2.5 - which is whitelisted as "GPL-friendly".

avpaderno’s picture

@gisle Thank you for your comment. I just wanted somebody else could check, since the issue was closed by a maintainer of the involved project, without anybody else really checking.