Hacker News new | past | comments | ask | show | jobs | submit login

For content, rather than code, I generally prefer to use one of the creative commons licenses.

https://creativecommons.org/share-your-work/




I 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...) might make more sense.


How would you differentiate content from code when the thing in question is as meta as SVG?


If the line is really that grey, dual license MIT/CC0?


I am following what a few books like 'Think Python' do, content is CC and code is MIT (or GPL, etc).




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: