News for hackers. Stuff that matters.
Re:Building an Open Source Service by nickpsecurity on Wednesday October 26, 2016 @10:06PM (#12802403)
What do you think about using a license that forces freeing any changes to what you shared but doesn't affect anything linking to it dynamically or statically? As in:

http://zeromq.org/area:licensing

Additionally, patent license provisions for using the shared code seem almost mandatory given the patent trolling we're seeing of both suppliers and users of whatever they manage to get through a patent clerk. All the FOSS licenses should try to include some protection there against beneficiaries suing derivatives.

Re:Building an Open Source Service by zeeg on Thursday October 27, 2016 @01:30AM (#12803118)
Definitely not a license expert here. Lots of legal folk I trust would stand by "Apache and only Apache" for releasing FOSS, and I think one of the core reasons is patent protection. We may re-license Sentry at some point to Apache just because its a more understood model and as a growing business that may one day be important. It's also nice that it provides good out of the box tools that are widely supported (e.g. the CLA).
Re:Building an Open Source Service by nickpsecurity on Thursday October 27, 2016 @10:11AM (#12805225)
You should definitely check out MPL too. I was told it's like LGPL for static linking. As in, commercial integrators can use it without releasing their source. Only have to release improvements to sentry itself in that model.