Can I license my specs/tests differently than my actual library/application source code? [closed] - licensing

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've written a Ruby gem that I've licensed under the MIT license, but I think I could greatly improve the test coverage by using an AGPL library in my specs. The actual library code I've written (that would be executed by people using the gem) would never use this AGPL library, it would just be for running the tests in a development environment when running the gem specs.
Is it legal for me to then license my spec code under AGPL while still licensing my library/application code under MIT? Is there anything special I would have to do with regard to my GitHub repository (e.g. a separate repo for the specs) or my .gemspec file (e.g. not bundling the specs and AGPL library with the gem)?

First of all, I am not a lawyer.
Let's assume that the library you're going to use is named L.
Since your application code is not a derivative work of L it is not affected by AGPL's licensing. Therefore you're free to choose rules under which it is distributed.
Your test code is a derivative work of L in the sense of AGPL and as a result if you publish it you have to use terms of AGPL.
Storing files with different licenses in a single repository is not an issue. What is important is to clearly and unambigously state what is the license of each file. The best idea is to put relevant notes both in files' headers and a README or LICENSE file. What I mean is something like
All files in the test directory are published under terms of (...). All remaining files are published under terms of (...) unless otherwise stated.
Remember to add this information in each form of distribution of your project, i.e. a gem file, a tarball and so on. If you have to specify terms under which your whole gem is published you have to provide both licenses. In the terms of a gemspec it would mean
spec.licenses = ['MIT', 'AGPL']

Related

Distributing free software (Qt) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I have built a small program for plotting data from serial port using Qt and QCustomPlot. I am an engineering student, and I had a project that required me to manipulate data from the ADC of an mbed, so I built this app for my convenience and for experience. I would like to share it with other people who need such a tool (will put it on the mbed website).
I am not a programmer and I do not know a thing about licenses. The QCustomPlot is under GPL. I read that I cannot use static linkage with the GPL licence for QT; I do not intend to, (I will post the source too), but would like to include a statically built version of the program for people who would rather just use the program.
So without going in too much detail, what can I do? Also, do I need to include any disclaimers in my source?
First of all: choose a license for your software. The website http://choosealicense.com can help you in doing that.
Usually a license requires to add a text header to your source code files. This is just a fragment of text which shows the terms of the license right within the source code.
Also, a license.txt file is often required in which the full license has to be pasted. Anyway choosealicense.com clearly explains what to do.
Notice that some licenses (e.g. the GPL) need that a list of changes is added to your source code. This list has to be mantained through the entire life of your software distribution and updated when you provide new releases.
When you are ready with your package use a website like GitHub to distribute it as a source code.
Do not include binaries. Just add the source code and a README file in which you explain how to compile them.

Using software in a GPL linux distribution [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I am looking at different types of linux to run a small web server on, however I have a question as I am a bit confused about how the GPL works. If I have PHP scripts that I created myself, etc...running on the linux server, do those automatically become part of the GPL, or are those still mine to do with as I please? How about if I need to make a copy of the system, as is, by making a disk image, to install it on another computer of mine? Does that mean that all my work would become part of the GPL?
First of all it is very likely that your Linux system will run Apache, which is not licensed under terms of GPL, but Apache license. Apache itself does not run PHP scripts. In fact lots of functionality is provided by third-party modules and this applies to PHP too, which is handled by mod_php. Those modules are allowed to be distributed under their own licenses. And PHP utilizes this being distributed under terms of PHP license. PHP license is not permissive (or not copyleft), which means that you may distribute your scripts under any license you wish, with very little restrictions like including in your product a statement:
This product includes PHP software, freely available from <http://www.php.net/software/>
So basically no, your software will not become a part of GPL in any way.

Distribution of commercial front-end for LGPL-licensed console application [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
There's a LGPL-licensed console application. I want to create a commercial GUI front-end for it and distribute it bundled with this console app. Does LGPL license allow that?
Note that I am not using a LGPL-licensed library, I am using a stand-alone application.
I tried reading the license itself, but it is still unclear to me.
Note that I am not using a LGPL-licensed library, I am using a stand-alone application.
The first L in LGPL stands for Lesser not Library. So it does not play much of a role whether it is a library or a stand-alone application.
LGPL is with weaker copyleft. That means, if you re-distribute that LGPL'ed software in object code (binary) you need to offer the source for it (for that version you distribute).
However it is lesser, meaning that you do not need to put your code under LGPL as well. Take care that your users should be able to tell both applications apart (and replace the one or other part easily).
However if you write GUI frontend, I think this is a pretty standard case, you will create a command-line and then execute the LGPL'ed binary.
Take care that this is from a developers perspective, not from a lawyer. A lawyer would require to see your current application and then could tell you in more detail the whats and whereabouts for your very concrete case.
It's also practical you get in contact with the author of the LGPL'ed software, they might be interested to know which supporting tools exist. As they have choosen the LGPL it's likely they do not expect your software to be under LGPL as well. So if you get in touch with the original authors you can also clarify your issue, albeit I don't think there is one technically.

Is it possible to use CKEditor in commercial web site? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I plan to use CKEditor in commercial site. I've read http://ckeditor.com/license but I didn't understand how it is possible to have pricing for commercial use while they offer LGPL(which is good choice for commercial use)
Imagine you want to compile the javascript code of CkEditor into a binary application. Just assume this is possible. Then you would not ship the source code of the library any longer.
If you now even make modifications to the source code to distribute within the binary, you do not satisfy the LGPL as it requires that you provide the source for the library along with your binary. Same for the MPL on the file level.
If you don't want to distribute (your changes in) the source-code form of the library, you then can get a commercial license by the project (you buyout the license).
Next to such specific cases I can imagine that some folks just would like to have a commercial license as form of a backup if their legal department is too much puzzled. If the license is relatively cheap, they can opt for it and continue with their own work w/o being further interrupted. Business, you need to keep it running.
But regarding the LGPL, as long as you offer source (incl. the changes you probably make) of the library, you're fine to use it with non-free programs. So this does not mean that your website must be LGPL it's just using a LGPL'ed library.
You can use it for your commercial website. However, if you build a product and want to include (distribute) CKEditor with it then you might need a commercial license.
The condition whether you need the license is based on your product's license. If your product is closed sourced then including an open source product with it without sharing the source code is illegal. So, this commercial/closed distribution license fills the gap. You pay for it and you can distribute your product with the CKEditor closed sourced. Additionally you may do any closed source modifications to CKEditor.
TL;DR: if you want to modify and distribute it with a commercial license then you need to pay, otherwise you are free to use to for free!

Using LGPL library in a commercial Java application [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I have a commercial Java application which I will be distributing.
I want to use an LGPL'd java library.
I wont be modifying the library.
Does the LGPL license of that library have any impact on my application's license?
Yes, it does to a certain degree. You are e.g required to allow people to upgrade the LGPL'd library without your help. I suggest reading through the whole license yourself, as you're legally obligated to adhere to it's clauses. Know what you oblige yourself to, don't just take other people's words for it :)
As far as I understand the LGPL, no, you can distribute it however you like. You will only be linking to the library, not creating a derivative work, and the LGPL doesn't restrict linking.
There is no impact on your application. LGPL license allows inclusion in commercial application as long as the terms of the license are fulfilled (LGPL license text in the distribution, indication of the use of the library, etc).
My guess is that as long as your linking is dynamic (i.e. dynamic loading of the .dll/.so/.a/.class/whatever file at runtime), you're OK. If you statically compile your code to include the library, you're at risk of violating the license, depending on how your code is structured.
If it's Java, however, you can not link statically - it's an impossibility of the platform.

Resources