We’re rewarding the question askers & reputations are being recalculated! Read more.
Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
Status closed:yes
Types is:question
Exclude -[tag]
For more details on advanced search visit our help page
Results tagged with Search options answers only user 2021

Questions about the GNU General Public License

Yes: "However, some licenses had requirements that weren't really restrictive, because they were so easy to comply with. For example, some licenses say that they don't give you permission to use cert …
answered Dec 5 '12 by Martin Beckett
public domain even though your release is GPL. Then people have the option of building on your GPL'ed code or returning to the original …
answered Mar 19 '13 by Martin Beckett
People develop plugin scripts that have to invoke library functionality from the Joomla core in order to function. This surely means that the plugin has to be GPL. Not necessarily, it … or do with it whatever they like (provided it falls under GPL terms). If the code falls under the GPL, either because they chose to make it so - or because it was deemed to be a derived work …
answered Jul 26 '11 by Martin Beckett
If you created a derived work of a lib you received under the GPL then your lib is GPL. If you paid them for a commercial license then the derived work is under whatever the terms are for that license …
answered Jan 22 '12 by Martin Beckett
You can certainly keep ownership of the logo and name yourself while releasing the code under the GPL. This is essentially what the Firefox/Mozzila logo licence did. Truecrypt also have a similar … requirement, you can alter the code but not call the modified version Truecrypt. However since you have released the code under the GPL there is nothing to stop the users simply rebuilding their code under a new name and logo. …
answered Jul 2 '12 by Martin Beckett
No - the GPL license controls how the code is to be distributed, it isn't an intrinisic property of the code. Code doesn't become GPL - it is distributed under the GPL If you aren't distributing the earlier versions of the code then the license has nothing to do with it. …
answered Oct 2 '12 by Martin Beckett
If your code uses someone else's GPL (ie not LGPL) code then you have (probably) created a derived work. The only license you have to distribute the other person's GPLed work is GPL. You cannot take … their work and give it away as CC - it's not yours! edit: If you merely wish to release you own code on it's own (eg as source) then even if that requires your users to get the GPL lib to use it …
answered Aug 1 '12 by Martin Beckett
If you link to a GPL lib then you have created a derived work and your code must be GPL - this is different to LGPL code which specifically allows dynamic linking of differently licensed code. The …
answered Jul 30 '12 by Martin Beckett
approval of the "wxWidgets Licence" which will be identical apart from the name. The wxWindows Licence is essentially the L-GPL (Library General Public Licence), with an exception stating that …
answered Aug 22 '11 by Martin Beckett
actually having any major effect is small. Secondly GPL limits how you can distribute a derived work. Unless your testing framework requires some changes to my main codebase (in which case it's a …
answered Aug 15 '12 by Martin Beckett
No a piece of work created by a GPL piece of software is not generally a derived work. There are exeptions, where for example, the GPL app is a code generator which produces source code containing … significant bits of the original app. But producing an image, or any other piece of creative work with a GPL tool is not itself GPL. …
answered Apr 5 '15 by Martin Beckett
Did you write the code? Then the GPL is working for you - you don't need to do anything to bide by it, the people you distribute the code to are bound by it. Remember the GPL doesn't apply to you … for your own code - you are still free to do anything else you want with it. You can even sell it alongside the GPL version. If you used other GPL code in your app then you just abide by the same …
answered Nov 3 '12 by Martin Beckett
"This original wordpress theme has the GPLv2 licence in it's root directory, so I assume that the entire theme is GPL code" Not necessarily, the GPLed code should say so in each source file …
answered Aug 2 '12 by Martin Beckett
Yes - the GPL says nothing about "selling" software, it talks about distributing. If you distribute GPL software you have to abide by the licence. The GPL3 uses a slightly different phrase "convey" - to clear up some different meanings of "distribute" in different jurisidictions …
answered Sep 26 '12 by Martin Beckett
If your code is a derived work of the GPL code it must be released. If your code incorporates the GPL code, modified or not, it is (almost certainly) a derived work. The question is a little different if the database wrapper is an LGPL library. …
answered May 3 '16 by Martin Beckett

15 30 50 per page