Given your description, I think A and B is irrelevant to the question, what matters is C and D, and the question comes down to whether or not GPL allows dynamic linking. If anyone may violate the GPL, it is C if it is not under GPL.
After some digging around, I found that the Wikipedia GPL article has a good summary of the issue. The answer is: it is disputed. The three existing standpoints, according to this article:
Both dynamic and static linking violates1 the GPL. This is the standpoint of the makers of the GPL (the Free Software Foundation), and they created the LGPL for this reason (to allow dynamic linking without violation).
Static linking violates, but the GPL is not clear about dynamic linking: It is hard to tell since the GPL does not provide clear instruction about what is considered derivative work.
Linking is irrelevant: GPL should only apply to source code-level. In my opinion this is the most sane option, since linking to a software to access its functionality is akin to pushing a button on a GUI to do the same thing.
Since the FSF says its intention with the GPL is to disallow both, I think it is wiser to either
respect that intention and use GPL on your own work if you link to GPL, even if the wording is not clear
or stay away from GPL software
Ironically, the GPL is not as free/libre as one would think. I know there is a reason for that, but my point is: don't put GPL on your software without thinking. If you are looking for a free and permissive license, the MIT or BSD licenses might represent your intentions better.
1: when I say "violates" I mean it violates iff the "consumer" of the linking is not under GPL.
Joshua Gay's edit looks sloppy at best: I found at least 2 clauses and a section in http://creativecommons.org/licenses/by/4.0/legalcode that look incompatible with any GPL.
I've written a letter to the FSF asking them to clarify this matter and the properties of the edit.
This is what I just got in reply, from none other than Joshua himself (nested blocks are his quotes from my letter):
Hello,
Thank you for writing.
- It doesn't mark the license as "compatible with the GNU GPL or FDL"
with the left-side line.
The color doesn't specify a version number of the GPL. I have been
waiting for confirmation from our general counsel that CC BY is
incompatible with GPLv2 and the FDL before updating the color on the
left hand side. Hopefully that will be soon.
- It doesn't comment on this decision as if it's something obvious.
Which it is not:
First note that both licenses make use of words like reasonable and
within reason. Interpretation should be done with that in mind. Here is
our position on this as I understand it. You are right that we should
have a more formal statement and I will try to get one prepared that
we publish on the site.
GPLv3 7(b) states that you can add terms "Requiring preservation of
specified reasonable legal notices or author attributions in that
material or in the Appropriate Legal Notices displayed by works
containing it;"
The FSF interprets this as to include a licensor doing something such
as removing certain parts of the reasonable legal notices or marking
them in ways as different from the original.
How are they unclear? I do not see what is unclear.
A person does not need to relicense a work to create a combined work
with the GPL. A CC BY licensed work that is incorporated into a GPL
licensed work would retain a copy of the CC BY license and all CC BY
notices. One would simply add to the work as a whole and in relevant
plces notices about the GPL and a copy of the GPL.
CC BY does not restrict adding additional terms so long as those
additional terms do not restrict "exercise of the Licensed Rights by
any recipient of the Licensed Material."
I will see about adding these clarifications somewhere.
Thanks again for emailing us.
Joshua Gay
Licensing & Compliance Manager
Free Software Foundation
This is the reply I got on further clarification of CC#s3a3. He believes it's compatible by doing a narrow interpretation:
The incompatibility as it appears to me is that GPL gives no right to
change any terms
for a licensee who has already received a license (or receives it from
an older copy) -
since a license is irrevocable and is granted on the terms that
accompany a specific copy.
So, your interpretation of this CC clause is that it only applies
to the moment one receives a copy from the copyright holder, not to
any later moment
or receiving it from any other party?
That is my current understanding. Do I have a reason to think it would
mean at a later date? I assumed such a request would need to be made
alongside the license itself. I will ask Creative Commons what their
interpretation is.
I am not a lawyer and I have no ideas how courts would interpret this.
But, I'm not sure how one could reasonable expect a work to be put
into the wild, modified and remixed for a period of 75 or 80 years and
then it be reasonable that a licensor could come along and ask for all
of those notices to be removed.
And here's the final update, right from the horse's mouth. The "reference removal"
CC clause is an obstacle. But as of now, Joshua doesn't consider it a strong enough one
to condemn CC-BY as incompatible. (diff to the current licenses.html as of this writing)
I suspect the clause does have such a use in mind. Its intended use
appears to be the case where a copyright holder sees their work used
in
a context that they deem inappropriate - so they wish any reference to
them
removed so that their perceived reputation doesn't suffer.
Creative Commons sent me a clarification and it is the case that the
intent of the license is so that a user could ask after the fact.
However, they explained that "to the extent reasonably practicable" gives a person a lot of flexibility in being able to simply deny the
request of the original licensor. I am interested in finding out some
other legal opinions on how strong the language "to the extent
reasonably practicable". Like how easy it is to make that argument as
a licensee. I believe this is will be the next question in the public
discussion mailing list. I will also open up an internal discussion at
the FSF and with our lawyers to make sure they think the language
"reasonably practicable" is sufficiently strong.
Why did he make the edit when he did? Perhaps because that's when he checked the compatibility. He actively participates in the CC-BY-SA - GPLv3 compatibility effort - that could very well be the reason that drew his attention to that matter.
The "transitive" compatibility of the earlier versions of the CC-BY has already been well explained by apsillers:
Earlier licenses are incompatible on their own but are compatible if the work's license allows relicensing to a compatible version. As you can see, this is a general principle not specific to a license.
Best Answer
Many of these questions are answered in the Drupal Licensing FAQ.
That's only correct if you didn't author the software in the first place.
If you did author the software, you hold the copyright to it by default. You can assign to others any rights you like, but unless you place it in the public domain (not possible everywhere) then you still have rights that anyone who is just licensing your software will not have.
Copyright holders will often dual license their software, providing a no commercial use public license and a commercial license. Often the former comes with no support, while the latter comes with a price tag and after sales service.
The problem with Drupal is that they assert that any Drupal modules constitute a derived work and thus must be licensed under GPL. While this may be the case for modules hosted on the drupal website, due to their terms and conditions, I am not convinced it is the case for software hosted elsewhere. Thanks kiamlaluno.
That's not always the case. Different projects handle these things differently. We have seen how Drupal judges this one way, but Eclipse has a different approach to plugins to their software. According to the Eclipse Public License FAQ:
In other words, if you write a program that modifies the Eclipse framework then it must be covered by the Eclipse public license, but if you write modules which use the public interface of the framework, you can license it in any way you like.
In the case of a GPL program however, the situation is different:
From Frequently Asked Questions about the GNU Licenses. Thanks Philip
If you hold the copyright and they are using it in a manner not covered by the license attached to that software then they are guilty of copyright infringement. If they have been given access to GPL software then the software has been distributed to them and they can do anything allowed by the GPL.
As it is, you are probably covered by your employment contract with your employees. For contractors then you will probably need to talk to a lawyer about getting everyone to sign up to an NDA, if you haven't already. Thanks craig.
No, this is the so called application service provider "loophole" in the ordinary GPL that the AGPL was designed to plug.
Again, the Drupal specifically mentioned AGPL in it's licensing FAQ:
You will have to be careful about AGPL modules sourced elsewhere though.