Comply with Component Licenses
In Components, you reviewed the licenses of all project components to ensure the license you select isn’t in conflict. Now it’s time to comply with the licenses of those same components.
The most common responsibility required by FOSS licenses is attribution. You learned a bit about this already in Give Attribution, which also contains a couple of examples of attribution listings. Each license will tell you what sort of information you need to provide with the attribution, but usually it’s the name and copyright/license statement of each component.
Most often, software projects collect and publish these attributions in a file in the repository on their forge. This file can go by several names, but Apache ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access