Perhaps you intend your tools as purely academic exercise or for use only in altogether open source projects.
I find the proliferation of GPLv3 code as something tragic, because I can only use these things as toys and not for work. For instance, for this reason I am unable to use the excellent GSL code in any of my work. My favorite license style is Berkeley (e.g. PostgreSQL, ACE), followed by LGPL. I have donated work on many GPL projects, but they have to be strictly hobby projects for me. There is some chance I might use the LGPL subset, but those sort of things always seem half-hearted and I may need the functionality in the other parts and so I guess that I will stick with projects with a license style that is more useful for me. Of course, there is room for any sort of license and I have worked on Public Domain, Berkeley, LGPL, GPL, closed source commercial and other sorts of projects and see value in all of them. I just wanted you to think about the impact for people who would like to use your tools in a commercial environment. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
