- Embed this table into your Open Source Compliance Page
- Make this Open Source Compliance Page accessible by the footer of your pages
But what is actually the challenge?
As site owners, we have two options to deal with this challenge: Either we subsequently (and (semi) manually) heal the packages we implicitly have taken over by using WordPress and bootScore. Or we use them as we’ve got them. It’s clear: Healing would imply that we redo that job whenever we update WordPress or bootScore. So, we tend to go the other way — if there nevertheless was an option, not to violate the idea and the requirements of free software licenses.
The solution is this:
If we apply this process to our 3rd. party JS libraries, we have a strong argument for our position in case of a legal dispute — I’ve never heard of one — and we’re in good company: Even the FSF is proposing to do so.7 And the FSF really doesn’t have a reputation for taking license compliance lightly.
- cf. MIT License [↩]
- pars pro toto cf. GPL‑2.0. Additionally, the (A)GPL requires that each code that uses the (A)GPL-licensed library, etc. is also licensed under the (A)GPL (copyleft effect). But that’s not the point in this context. [↩]