Add information on compliance requirements

[andrewhavens]

Hello! Thank you for making this website. It is such a great resource! The only thing that I feel is missing is some information on the compliance requirements. It is really, really difficult to find information on what is required of you when using or modifying a particular open source project. For example, what is required of you if you choose to use some code from a project which uses GPLv2? I recently learned that you MUST offer to mail a physical CD of the source code to anyone who requests it. It is only in GPLv3 that you can offer the source code over the internet. I also wonder about what the compliance requirements are of more permissive licenses like MIT. Is it enough to include a copy of the license in the source code, or do you need to mention somewhere publicly that you are using these projects in order to give public attribution? It would be really helpful to know this information for each of the different licenses that are available.

[mlinksva]

How to comply isn't the primary topic of this project but it is relevant when choosing a license. There's a new compliance guide out that might have the kind of information you're looking for (but in general, read the pertinent licenses and talk to your lawyer 😬) -- see https://www.finos.org/blog/announcing-the-open-source-license-compliance-handbook and https://github.com/finos-osr/OSLC-handbook -- I've suggested they make entries web linkable which would enable us to consider linking to them from here.