15
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jul 2026
15 points (94.1% liked)
Open Source
47722 readers
55 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
Normally you would have in each file a license header and depending on which license the file ia it would have a different header if the licenses are mixed.
Often we don't copy the library source code into the same git repo but use some package manager which installs them for the user.
In that case if the whole git repo is the same license then often we just have a LICENSE file in the root which ia mentioned in the readme.
Back in the day we made https://github.com/Pelagicore/OpenSourceTemplates
It has links to SPDX descriptions ect which are best practices in this regard.
Thanks! So if I simply use pip to get some libraries for my project, do I need to include the licenses (e.g. MIT) somewhere in my source code?
How about if I statically link them by building a executable that contains everything in a single file, so the user doesn't have to install Python and all the libraries separately?