My Look up app for OS X certainly isn't ready for public consumption.
Part of that is getting the right license information and stuff
bundled with the program.
If I understand correctly, GPL allows me to do what I want with the
client I'm writing - I can Copyright it to myself, keep my
At 03:17 PM 4/1/2002 -0700, Nathan wrote:
...
If I understand correctly, GPL allows me to do what I want with the client
I'm writing - I can Copyright it to myself, keep my source to myself, and
even commercialize it. But if I modify the API, I need to submit those
changes back. Or am I
My Look up app for OS X certainly isn't ready for public consumption.
Part of that is getting the right license information and stuff
bundled with the program.
If I understand correctly, GPL allows me to do what I want with the
client I'm writing - I can Copyright it to myself, keep my
Ahh... okay. I was thinking of LGPL (Lesser GPL), which from looking
at the Sword license page, it clearly is not. So basically I have to
GPL my client if I use the Sword API. I don't really have a problem
with releasing my source code, I just need to get the right license
information with
Okay... but my client itself doesn't have to be GPLed? I have to make
the source available under one of the compatible licenses.
And I don't need to write GPL all over my software, right? If the
source is available under GPL, do the binaries have to state that?
Just curious about this stuff.
