Hi Istvan, Thank you for clearing the confusion! I've replaced the BSD with the GPL license in the Python Ensembl API package. I also made related changes in the README and setup.py before submitting the final tarball to Google this morning.
One thing I am still not clear about is how to apply the GPL license to my program. So far, I simply copied the GNU GNERAL PUBLIC LICENSE (Version 2, June 1991) verbatim and put it at the top-level of my package. Do I need to write to the Free Software Foundation at Boston to require a copy of the GNU General Public License? I guess it is not necessary. Since my code includes Pygr components which are GPL-d, it will automatically inherit the GPL nature. Is that right? thanks, Jenny On Mon, Sep 8, 2008 at 5:33 AM, Istvan Albert <[EMAIL PROTECTED]>wrote: > > > > On Sep 7, 12:46 am, "Jenny Qing Qian" <[EMAIL PROTECTED]> wrote: > > > It's time to release my code and submit it to Google. I don't know which > > license should I choose. > > Hi Jenny, > > I believe that you have one choice only. Since your code includes code > that was GPL-d, it may not be released with any other license than > GPL. Not even a "free"-er license. That is the main ideology behind > GPL. > > best, > > Istvan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
