Closed idokleinman closed 8 years ago
Comment by idokleinman Monday Jan 12, 2015 at 03:06 GMT
Will do thanks for the input, wasn't sure about this one
Comment by zsup Monday Jan 12, 2015 at 05:01 GMT
sure thing. although actually now that I think about it, maybe we want this to be LGPL? @towynlin, what do you think?
Typically our approach is LGPL licenses to libraries and Apache for any example application code. LGPL ensures that users contribute improvements back to us. I think we could go either way here; on one hand it's a library so that would suggest LGPL, but on the other hand I would be comfortable allowing people to use this for non-Spark purposes (the set-up process stuff may be useful). Would love input from others
Comment by towynlin Monday Jan 12, 2015 at 07:19 GMT
I don't have a strong opinion here. Either Apache or LGPL would be fine. The biggest difference I think is that LGPL would require a developer using the SDK to share the source code of any changes they make to the SDK (not of the app in which they use it). Apache would let them change the SDK behavior without sharing the source of those changes.
I'd lean slightly toward LGPL as a sense of assurance of high quality of Spark-powered apps as well as community spirit.
Comment by idokleinman Tuesday Jan 13, 2015 at 02:27 GMT
LGPL 2.1 or 3.0? http://choosealicense.com/licenses/lgpl-2.1/ vs http://choosealicense.com/licenses/lgpl-3.0/
The problem with LGPL is that the license is incompatible with apps distributed through the App Store.
All files/SDKs are now Apache 2.0 license
Issue by idokleinman Saturday Jan 10, 2015 at 01:26 GMT Originally opened as https://github.com/spark/mobile-sdk-ios/issues/26