15

Say I'm writing a small GPLv3 licensed Python script that I want to release publicly. It would use a few MIT licensed libraries and maybe also some chunks of code from some MIT licensed projects.

As per the MIT license conditions I would have to include the MIT license text in my project. So how would that be done properly? And how about other licenses that require the license text to be included?

Sorry if this has already been answered a million times. I'm relatively new to this stuff and I find the licenses really hard to understand despite my attempts. I tried to also use some other open source projects as examples, but most of them don't seem to include the license texts anywhere but the readme files at least seem to state which libraries they use.

you are viewing a single comment's thread
view the rest of the comments
[-] frongt@lemmy.zip 10 points 1 day ago

There's no formal system. If you put the lib in its own dir, just keep its license intact. If you have to put it alongside your own stuff, you can create a LICENSE-libname.txt file, or have one long LICENSE.txt file with your license at the top, then include each library name and its license, or whatever makes sense in your project that will satisfy the license requirements.

[-] bluewhale_@lemmy.ml 1 points 1 day ago

Right, I guess the licenses don't typically give exact instructions on where to put it etc and the requirements can be met in multiple ways. I guess I'm just too stuck trying to understand what's the typical way people do these things in their projects. :'D

this post was submitted on 05 Jul 2026
15 points (94.1% liked)

Open Source

47735 readers
43 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 6 years ago
MODERATORS