3 ms·
I prefer zlib license[1] just because of that. I'm fine with other people using my code. But keep my name clean. It also also haves quite simple and easy to und
by zokier 17y ago
I prefer zlib license[1] just because of that. I'm fine with other people using my code. But keep my name clean. It also also haves quite simple and easy to understand language and no extraneous capitals.
[1] http://www.opensource.org/licenses/zlib-license.html http://www.opensource.org/licenses/zlib-license.html
- KirinDave 17y agoI don't mean to be contentious, but it doesn't seem to include the clause the BSD license includes. From the BSD license: “Neither the name of the <ORGANIZATION> nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.” I don't think the zlib license has an equivalent restriction? I don't see anything that protects the author or the organization funding the author from misrepresentation. To give a clear example of what this clause presents, I have a friend who wrote a open-sourced library that a company used a few years ago. The founder of that company ran around using his name “Lots of people are excited about our product! We've got a lot of software engineers doing pro-bono work for it, such as <FRIENDNAME>.” Obviously, this is disingenuous and potentially damaging to someone's representation, but it's not strictly forbidden by most licenses. What's nice about having your license explicitly forbid this practice is that if the user does this, they void the license and it is relatively easy to get them to stop using your library and really firmly disassociate yourself with the organization, should you choose to.