<story><title>Choosing an OSS license</title><url>http://choosealicense.com/</url></story><parent_chain></parent_chain><comment><author>pbiggar</author><text>Really, this should just be a big sign saying &amp;quot;use the MIT license&amp;quot;.&lt;p&gt;This is a site for beginners to OSS licensing. If this is your first time, just choose the MIT. If it&amp;#x27;s not the first time, you get to worry about whether you want to restrict reuse with the GPL, whether you prefer the BSD (2-clause or 3?), whether you agree with Stallman&amp;#x27;s philosophy enough to put up with the downsides of imposing GPL on your users, whether patents affect you, whether you need copyright assignment, whether to set up an entity to own your code, and all sort of other license bullshit.&lt;p&gt;First timers should use MIT, every time.</text></comment>
<story><title>Choosing an OSS license</title><url>http://choosealicense.com/</url></story><parent_chain></parent_chain><comment><author>narcissus</author><text>At some point in the distant past, there used to be a site that had a huge matrix of licenses, that allowed you to look across one axis for one license, down the other axis for a different license and then basically read the consequences of combining code with those two licenses.&lt;p&gt;I liked that site and for the life of me cannot find it again. Things like &amp;quot;can I copy Apache licensed code into this LGPL code&amp;quot; were answered really simply, even when the answer included comments around making changes available, impact on copyright notices etc.&lt;p&gt;Does anyone know of anything similar these days? Don&amp;#x27;t get me wrong, the site linked here is great, but for me, at least, the fuzziness is in the legalities of combining code...</text></comment>