4 ms·
For content, rather than code, I generally prefer to use one of the creative commons licenses. https://creativecommons.org/share-your-work/ https://creativecom
by hardmaru 7y ago
For content, rather than code, I generally prefer to use one of the creative commons licenses.
https://creativecommons.org/share-your-work/ https://creativecommons.org/share-your-work/
- metaphor 7y agoHow would you differentiate content from code when the thing in question is as meta as SVG?
- tingletech 7y agoIf the line is really that grey, dual license MIT/CC0?
- asicsp 7y agoI am following what a few books like 'Think Python' do, content is CC and code is MIT (or GPL, etc).
- tribby 7y agoI agree with the spirit of your comment (CC makes sense for SVGs), but I also don't think it's quite as simple as content vs. code. there are many icon sets that are distributed as font binaries, for example, which are software; in which case the OFL (SIL open font license -- https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=OFL_web https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id...) might make more sense.