Software licences MIT, GPL and proprietary: where commercial projects run into trouble
The article argues that software licences are not just paperwork but real constraints on a product, affecting whether it can be sold, kept closed source, and what must be published. It compares MIT, BSD, Apache 2.0, LGPL, GPL, AGPL, proprietary and CC BY-NC terms, noting which permit commercial use and which require source disclosure. It highlights common pitfalls, such as statically linking GPL code into a shipped mobile app or using AGPL software as a networked service. The same caution applies to AI model weights and datasets, where non-commercial licences like NLLB's CC BY-NC 4.0 can rule out commercial use. The author recommends checking licences during architecture design and maintaining a third-party notices file, while stressing the article is not legal advice.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in