Hi guys, I have some questions about the drupal license and, more in particular, about the license of a custom module.

Drupal use the GPL 2.0 license, that as far as I know should "force" all the code written _for_ drupal to be published under the same license (or an equivalent one), but this is applicable also on custom modules?

Im planning to sell a drupal module on some marketplace, but those require another license and I dont know what I can or cant do; but there are a lot o drupal modules on different marketplaces, so I guess there is a solution..

My idea is to release the module with GLP 2.0 and free of charge, and just sell a "preconfigured" and ready-to-go version on those marketplace.

Comments

nevets’s picture

The Licensing FAQ may help.

Strae’s picture

Thanks, #7 and #8 was exactly what I was looking for.

You HAVE to assume your visitor is a maniac serial killer, out to destroy your application. And you have to prevent it.

WorldFallz’s picture

Drupal modules are derivative works and so you cannot relicense them in a way incompatible with the GPLv2: https://www.drupal.org/licensing/faq#q7.

Most of the marketplaces I've seen use terms completely incompatible with the GPL (ie envato). That people choose to do so anyway doesn't mean there's 'a solution'-- it means that there are unscrupulous people that will violate the terms of the GPL for personal gain. A rather risky way of conducting business imo. Not to mention completely antithetical to the open source community.

My idea is to release the module with GLP 2.0 and free of charge, and just sell a "preconfigured" and ready-to-go version on those marketplace.

This gets a little murky-- it depends on what you mean by "preconfigured". You could actually be selling your services rather than the code.

Most successful drupal business models are either ASP or services in nature.

of course, all the usual IANAL disclaimers apply and you should really consult a lawyer familiar with the issues of GPL before embarking on a business.

Strae’s picture

Hello WorldFallz, thanks for the reply!
My module purpose is to create "storyboards" from pictures - like google+ "stories" based on picture from automatic backup; So with "preconfigured" i mean to sell "assets" where the user have only to add his own photos and the "storyboard" is ready to go.
Instead in the "open-source" release, the user has to configure the animations, maps types, etc... as long as adding his own images... I dont see this as an antithetical act! (but probably you wasn't referencing at me with that sentence)

Btw i've used a couple of times some themes bought on envato, and I remember a "visual shortcode" module that's never been released (and if I remember right, there were no license file) - you're telling me I can take this module license for granted as GPL 2.0, reuse, resell and distribute it under the GPL license?

Im just a small developer and I dont want to go in legal trouble with envato or the company who created it, so I dont think i'll do it.. but just to know

p.s: sorry for my very bad english ;)

You HAVE to assume your visitor is a maniac serial killer, out to destroy your application. And you have to prevent it.

WorldFallz’s picture

No, I wasn't referring to you in anything I said above! Just those folks that knowingly violate the GPL for personal gain. You're here asking questions in earnest-- if that were applicable to you, you wouldn't even bother posting here.

And I have no clue about the legal ramifications of ignoring a license that is itself an illegal re-license, lol. Personally, I just don't use illegally licensed works and don't reward such behavior with anything in the way of recommendations or open source collaboration. I've even reported some them.

If one can't work within the confines of the GPL then they should use another product (no, I'm not referring to you, lol). You don't get to disobey the law because you don't like it. You don't get to re-license the work of thousands of drupal contributors just because you want to.

I'm not too happy about the amount of taxes I pay-- that doesn't mean I get to decide I can pay less tax.

The GPL is no different.

Jaypan’s picture

To be honest, I don't think their violation of the GPL matters, as their own terms are invalid, seeing as they are not compatible with the GPL. So they are unscrupulous for trying to push unenforceable terms, but they can't actually do anything to you if you 'violate' them.