README and documentationThis is probably a stupid question, but I couldn’t find a reasonable answer anywhere so I thought I’d just ask anyway.
I’m working on a library of my own, and I wish to include IGListKit as a dependency within it. I will not be storing IGListKit within my library’s repository, and only linking to it as a dependency using the official Carthage and CocoaPods methods to do so.
So two questions about this:
Again, I realise these are stupid questions, and I think I can guess the answers to both, but ones that I thought I’d get clarified regardless.
Thanks
Hey @HarshilShah ! 😄
Not a stupid question at all. Software licensing is hard. In general, the BSD license is an extremely permissive license. (It's basically the MIT license, except it requires attribution and prevents endorsements.) Caveat — I am not a lawyer. 😉
Despite some legal jargon, the 3 conditions are pretty straight-forward:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
Do I need to include IGListKit's copyright notice within the library and/or any attached example projects?
Yes (although this is rarely, if ever, enforced — generally speaking.)
Does using IGListKit mean I have to use the same license or anything like that?
No. You're free to apply any license, or use this for closed-source project.
I'd recommend using the MIT license for your library (assuming it will be open-source). This is probably the most common because it is the most permissive license.
Thanks for the help @jessesquires! Definitely going ahead with MIT for my library.
Most helpful comment
Hey @HarshilShah ! 😄
Not a stupid question at all. Software licensing is hard. In general, the BSD license is an extremely permissive license. (It's basically the MIT license, except it requires attribution and prevents endorsements.) Caveat — I am not a lawyer. 😉
Despite some legal jargon, the 3 conditions are pretty straight-forward:
Yes (although this is rarely, if ever, enforced — generally speaking.)
No. You're free to apply any license, or use this for closed-source project.
I'd recommend using the MIT license for your library (assuming it will be open-source). This is probably the most common because it is the most permissive license.