GPL

I know this is getting cross posted everywhere, but it's big news (for people who follow both code and content licensing) As of today, CC BY-SA 4.0 is now one-way compatible with the GPLv3. This is the result of extensive collaboration and analysis with the Free Software Foundation and the Creative Commons community.

http://creativecommons.org/weblog/entry/46186
https://wiki.creativecommons.org/wiki/ShareAlike_compatibility_analysis:...
http://creativecommons.org/compatiblelicenses

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 ;-).

I have some questions about this scenario:

1 - If I distribute a development in drupal using MSSQL as Database Server (http://drupal.org/projects/sqlsrv) that is not under GPL licence, the functions and/or procedures stored in that database can be encrypted? Notice that in this case I didn't encrypt the drupal code.
2 - If I use Drupal to interact with data generated and managed from a propietary software (which can't be redistributed), can I via contract or other negate the possibility of a redistribution.

I'm seeking some advice around licensing for my software and Drupal. Thanks in advance to those who offer their opinion!

1.) I created and own a standalone, commercial, script. It can run as a php web application in its own right (no linking to any 3rd party software).

How strict is Drupal's GPLv2+ licensing policy? I've read numerous threads and reviewed lots of code, but it's still unclear.

Points of confusion:

• I see lots of code that's GPLv3-only or GPLv2-only in core and in contrib modules and themes. Yet http://drupal.org/licensing/faq/#q13 seems to indicate that such code is not in compliance.
• How is the MIT license interpreted by the Drupal-sphere in terms of compatibility and integration? I'm specifically wondering about versions of the MIT license that permit sublicensing.

Drupal Design sub site will allow uploading of design files for sharing with other users. There are three main sections to the site:

• Challenges - where users contribute and collaborate on design problems for drupal.org, drupal projects, drupal core and so on.
• Assets - where users can upload and download high quality layered design files such as icons, templates, textures and so on.
• Discussion - where users can post comps for discussion, collaboration, feedback and so on.

Hi! I read the FAQ and found a post that is a similar case to ours but just wanted to confirm.

My question is simply does managed hosting constitute conveyance? I imagine a lot of folks will have similar questions as computing moves more toward a virtual and cloud hosting context.

In our case, we host our own Drupal instance, which contains custom modules and theme extensions we developed to meet the specific needs of our audience. We plan to release parts of the work we have developed to the open source community, but on a schedule we can support.

There has been much discussion through the years about the automatic GPL status of Themes and Modules, and I will weigh in on that topic itself in another post (see the bottom of this post). But for now suffice it to say that I see an argument in favor of requiring GPL for Modules but I see a very different and very compelling argument in favor of excluding Themes from the GPL mandate. This post is to address a pre-cursor to that argument ...

I was searching around for licensing policy on Drupal, specifically, releasing patches and modules from copyright (into public domain). I came across http://drupal.org/licensing/faq#q7 where item seven states "Drupal modules and themes are a derivative work of Drupal" and additionally implies that this is true for all works, hosted by Drupal.org or not.

This topic will be of interest to many people across various organizations today who are deliberating on whether to adopt drupal or not and if so to what extent.

We are a group of Drupal enthusiasts within a large IT services provider interested in using the drupal platform to configure and create simple tools to help the various teams within the organization in day to day activities.