3 ms·

Using MIT licensed icons in a website

2 points by hdkl 4y ago

Hi, I want to use SVG icons (heroicons) licensed under MIT in a website The license states - "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.". Where do I need to put a copy of MIT license text? Do I put it as a comment in the SVG code of the icon? or make a separate "/license" page and say "Icons provided by heroicons licensed under MIT, license notice below - and then paste the MIT license text" is that fine?

Cockbrand 4y ago
A similar question has been submitted as an issue in the project's GitHub repo [1]. I'm as much a lawyer as any random person on the street, but I'd go with the separate "/license" page. Or you could submit your question as a GitHub issue yourself in order to be sure. [1] https://github.com/tailwindlabs/heroicons/issues/172 https://github.com/tailwindlabs/heroicons/issues/172
- hdkl 4y ago
  "A similar question has been submitted as an issue in the project's GitHub repo" - I've read that issue already, it doesn't answer where should I include the license text that I asked in this question. "but I'd go with the separate "/license" page." - Thank you for your answer :) "Or you could submit your question as a GitHub issue yourself" - I will create an GitHub issue for confirmation. Thanks :)
  - Cockbrand 4y ago
    I didn't want this to come across as a snarky comment, sorry if it did! And it's true that that's not a definite answer, but it made me imply that the "license" page is the way to go.
    - hdkl 4y ago
      I get it and it's not a snarky comment. I appreciate your answer, I opened a GitHub issue just to confirm :)
afiori 4y ago
The solution I would propose is to include a link to the licence inside the SVG, either as a comment or as some non visible element. Or otherwise to include such a link in the html. Overall I see more people/projects going for a separate license page where you list all the relevant notices/licenses; going with the group sound like a good idea in this case.
- hdkl 4y ago
  Got it, thanks for the input!

2 points by hdkl 4y ago

Cockbrand 4y ago

A similar question has been submitted as an issue in the project's GitHub repo [1]. I'm as much a lawyer as any random person on the street, but I'd go with the separate "/license" page. Or you could submit your question as a GitHub issue yourself in order to be sure. [1] https://github.com/tailwindlabs/heroicons/issues/172 https://github.com/tailwindlabs/heroicons/issues/172

hdkl 4y ago
"A similar question has been submitted as an issue in the project's GitHub repo" - I've read that issue already, it doesn't answer where should I include the license text that I asked in this question. "but I'd go with the separate "/license" page." - Thank you for your answer :) "Or you could submit your question as a GitHub issue yourself" - I will create an GitHub issue for confirmation. Thanks :)
- Cockbrand 4y ago
  I didn't want this to come across as a snarky comment, sorry if it did! And it's true that that's not a definite answer, but it made me imply that the "license" page is the way to go.
  - hdkl 4y ago
    I get it and it's not a snarky comment. I appreciate your answer, I opened a GitHub issue just to confirm :)

afiori 4y ago

The solution I would propose is to include a link to the licence inside the SVG, either as a comment or as some non visible element. Or otherwise to include such a link in the html. Overall I see more people/projects going for a separate license page where you list all the relevant notices/licenses; going with the group sound like a good idea in this case.

hdkl 4y ago
Got it, thanks for the input!