Hi.

i have created a module,

http://codecanyon.net/item/views-hierarchical-taxonomy-filter/3000280

now look.

http://drupal.org/node/1170192#comment-6647744

Sorry but I cannot work on this issue anymore. It costs to many time. Finally I bought the Views Hierarchical Taxonomy Filter module for $20.

http://drupal.org/node/1170192#comment-6648028

You can checkout the module here. Feel free to post patches and let us bring that module forward :)

my response
http://drupal.org/node/1170192#comment-6682832

@yannickoo, so, you have stolen my code from codecanyon and published it for free.. nice..

his response

That is absolutely okay....

module sandbox
http://drupal.org/sandbox/yan_nick/1822924

this is the license of codecanyon
http://codecanyon.net/licenses/regular_extended

can i do something at respect?

thank you.

Comments

dgastudio’s picture

Title: my module stolen » my code is stolen

upd. title

killes@www.drop.org’s picture

See http://drupal.org/licensing/faq#q7

By distributing Drupal modules that are not GPL-licensed, you are infringing Drupal's license.

I must ask you to cease this activity immediately.

dgastudio’s picture

If the whole, or part, of the Work has been created using materials which are the subject of a GNU General Public License (GPL), your use of the Work (or part Work) is subject to the specific terms of the GPL in place of the foregoing conditions (to the extent the GPL applies).

So, there are no problems with license. Th only problem now is the autorship of the module.

killes@www.drop.org’s picture

We consider all modules to be derived works of Drupal since they implement Drupals API and are compiled together by the PHP compiler. Read the FAQ.

dgastudio’s picture

Status: Active » Closed (won't fix)

Ok

killes@www.drop.org’s picture

Status: Closed (won't fix) » Active

This is not fixed, you are still distributing Drupal code under an incompatible license:

http://codecanyon.net/category/plugins/drupal

dgastudio’s picture

Again...

http://goaugust.com/blog/open-source-drawback-codecanyon/

If the module is gpl, the license is gpl too.

killes@www.drop.org’s picture

I am no lawyer, but the "regular extended" license by codecanyon looks not compatible with the GPL.

1) Terms 1-9 are in parts incompatible with the GPL

2) Term 10 says that the GPL if applicable overrides these 9 terms

3) Term 11 limits your rights again (and presumably is meant to apply to GPL parts too)

Sorry, but this is not fixed.

It is fine to try and sell GPLed code, but you can not try and limit the terms of the GPL as codecanyon tries to.

As you've found out, selling GPLed code is not free of problems.

dgastudio’s picture

3. Sorry, but about which components are you talking?

On codecanyon a lot of people are selling modules for wordpress (gpl) and jomla(gpl) without any restrictions.

As you said, you are not a lawyer, but for sure that people from cocanyon have created their license with help of lawyer to avoid possible demands and problems.

If you want, i can write to envato support with description of the problem.

But, and i'll repeat again, the problem is not the license. The problem is that in sandbox there are no any reference to me as author of module.

It's the same if tomorrow i'll make a sandbox with copy of views and delete are reference to merlinofchaos. This is normal?

killes@www.drop.org’s picture

On codecanyon a lot of people are selling modules for wordpress (gpl) and jomla(gpl) without any restrictions.

I care neither for wordpress nor joomla.

As you said, you are not a lawyer, but for sure that people from cocanyon have created their license with help of lawyer to avoid possible demands and problems.

If they did, these lawyers had no understanding of the GPL.

If you want, i can write to envato support with description of the problem.

Feel free to do so.

But, and i'll repeat again, the problem is not the license. The problem is that in sandbox there are no any reference to me as author of module.

There are two problems:

1) codecanyon distributes code or allows others to ditribute code in a way that is incompatible with the GPL.

This is the problem I care about. However I can't solve it by myself. That's why I'll ask the Drupal Association to send them a cease and desist letter.

2) you are not mentioned as the author of the plugin that user yanickoo uploaded to drupal.org.

That is indeed incorrect, however since I do not have and do not want access to the module as available from codecanyon, I cannot see where any such references were removed.

Therefore I'd like you to propose a patch that restores you being mentioned as the author in an appropriate way. Please create the patch, upload it to an issue at https://drupal.org/node/add/project-issue/1822924 and reference this here. I'll then get user yannickoo to apply it.

greggles’s picture

That is indeed incorrect

Does the GPL require attribution? I don't think it does.

dgastudio’s picture

http://stackoverflow.com/questions/4475319/how-to-rebrand-copyright-a-fo...

Even though attribution is not required by the GPL, it’s good manners, and good practice

greggles’s picture

@kervi #12 - if you are suggesting that copyright notice should be preserved that makes sense to me. As killes has pointed out we can't see the original code so I suggest provide a patch to add back the copyright as mentioned in #10.

dgastudio’s picture

i don't think that it's a good idea to loose time on this.

maybee it's better if i create a new sandbox and after that, promote the module to full project?

i don't think that yannickoo is going to discuss my authorship.

also, i can provide you the access to my codecanyon or ftp account, to make you sure that this module is mine.

dgastudio’s picture

o! nice, trying to create a project for Views Hierarchical Taxonomy Filter,

This project name is already in use.

now that? that i have to do? rename my own project?

killes@www.drop.org’s picture

I'Ve changed the title of the existing sandbox.

dgastudio’s picture

thank you.

Wim Leers’s picture

I stumbled upon this today.

You've essentially fixed compatibility bugs in *my* module (which was GPL'd and on d.o). You can do that, and you can even resell the end result.

However, since by definition it is still GPL, I hereby request the source code. You must comply with this request, since you derived the code from GPL code, hence anybody can do such a request. I will then merge your code back into the code on drupal.org.

You've made 39 sales at $20 a piece (minus some fees probably), so you probably covered your costs.

WorldFallz’s picture

I stumbled across another module that be being sold with an inappropriate license-- is there a 'standard' way of reporting this to the DA?

greggles’s picture

Damien Tournoud’s picture

However, since by definition it is still GPL, I hereby request the source code. You must comply with this request, since you derived the code from GPL code, hence anybody can do such a request. I will then merge your code back into the code on drupal.org.

Just for the record, @Wim Leers you are misunderstanding how the GPL works.

The GPL is a license. If you are granted that license, you are granted the rights that are specified in the license. Derivative works must be relicensed under the same license, but only "to anyone who comes into possession of a copy" (section 5 of the GPL v3).

The GPL doesn't grant rights to "anybody". It only grants you rights if you are licensed the work in the first place.

Wim Leers’s picture

#21: Thanks — and you're absolutely right of course :) Fortunately, some people who did buy it from him did exercise their right.

dddave’s picture

Issue summary: View changes
Status: Active » Closed (fixed)
apaderno’s picture

Project: Drupal.org site moderators » Drupal Licensing Working Group
Component: Licensing » Violation