As copyright holder you can license your stuff however you want and give yourself whatever permissions you want.
But if you want it to be useful to others, you have to make sure that they receive everything that they need to take the GPLed project and run with it. So, for instance, if you've just cut and pasted code here and there, they don't need to know where it came from. But if you include some other library of yours unchanged, that library should be distributable by them under the GPL. On Tue, Oct 9, 2012 at 10:40 AM, Ryan <[email protected]> wrote: > Hello All, > > I have a question I'm unable to confirm the answer to and was hoping someone > on this list could kindly lend me their expertise in answering it. I'm a > freeware software coder and publish simple tools for anyone to download. > Recently I've been working on a larger project and because of its size I > would like to license it under the GPL for others to freely build upon it as > they see fit. From what I understand of the GPL if you use GPL code in a > separate project that separate project must be licensed under GPL too. Now > what I've done is sort of the opposite and borrowed code from freeware tools > I've written not licensed under GPL and want to use the borrowed code in a > GPL project. My question is as the copyright holder of the code do I have > to release all my other projects for which I borrowed/reused code from under > the GPL? > > Thanks, > Ryan > > _______________________________________________ > License-discuss mailing list > [email protected] > http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss > _______________________________________________ License-discuss mailing list [email protected] http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss
