Greetings, Thanks Trev for some great insights.
The main purpose for ZLIB is to make JALLIB attractive to end-users. My first encounter was when working on some JAL libraries years ago, and Wouter spoke up and pointed out that unless the license was clearly spelled out, he would not be able to make use of the library. After some debate, we settled on ZLIB. Personally MIT or new BSD would have been fine with me also. Saying it another way, the main purpose for the ZLIB is so that end- users, and possibly their employers, will be willing to consider JALLIB as a valid solution, with a clearly stated and widely understood license. Now then for fellow JALLIB developers, I think that what we've been doing up till now has been working fine -- generally we discuss changes and don't go against the author's wishes without permission. Personally I welcome improvements and bug fixes, whether I am aware of them or not. But if you want to re-factor, then it seems appropriate to at least try to get the author's buy-in. In a rare case that we cannot reach compromise (never happened so far as I know), then a derivative work could be done, but with a different file name. Let me be clear -- I am not advocating that we make any major changes to the way things are being done here at JALLIB, but only that we realize that the author of a work retains some rights to his works that are published in JALLIB. William -- You received this message because you are subscribed to the Google Groups "jallib" 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/jallib?hl=en.
