Licensing a Drupal distro to accomodate multiple component licenses

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
TomDude48's picture

Over the last several years we have built a fairly sophisticated internal Drupal distro we sell to clients as our secrete sauce. We have had several agencies inquire about us selling or licensing it to them. I am trying to figure out the best / proper way to do this.

I have spent a lot of time researching this on d.o. and other sites. I may be more confused now that when I started ;-).

The distro is of course a lot of Drupal which is under the GPL. There are some libraries from 3rd parties. They are all under some sort of open source license or are public domain. But I am not sure they are all GPL compatible – mostly likely at least one of them is not.

We have added a bunch of modules/features of our own creation. These, of course, are derivatives of Drupal and fall under GPL also.

But there are three components that we have developed ourselves that are not currently licensed under GPL.

The first is a set of JavaScript plugins. They are in a separate library.

The second is a PHP library to support the Intelligence system we have been working on. The library is designed to be platform agnostic and stand on its own, i.e. does not use any Drupal hooks, so it can be used with multiple systems.

The third component is a set of premium themes we have built. The PHP code in these themes is GPL, but the JavaScript, CSS/LESS, and images are not covered by the GPL.

Question: Can we even put these things together in a distribution? Or do we have to break out everything that is not GPL into separate downloads?

I know we can't post non-GPL to d.o. But what about a off d.o. package we maintain ourselves?

Legal

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: