When we create open source software, we share it with others so they can use, learn from, or improve it. But many of us forget one very important step: choosing the correct license. Without a proper license, people may not know if they can use our code legally. Worse, it might lead to legal problems or reduce the chances of our project being adopted or supported by others.
This talk is for all those who write code but may not know how licensing works. We will start with the basics of open source licenses—what they mean, why they matter, and how they affect our project in real life.
We will learn about:
i) Permissive licenses like MIT and Apache 2.0 (which allow others to do almost anything with our code)
ii) Copyleft licenses like GPL (which require others to share improvements)
iii) Compatibility Licenses, determines how code with different licenses can be distributed together.
iv) Special cases like MongoDB's license or the React license change
Using real examples from famous projects like React, MongoDB, and Linux, we will see how license choices changed the path of those projects.
We will learn a simple method to choose the right license for our own project, based on:
Our project's goals (personal, academic, startup, etc.)\
Who will use our code
Whether we want to allow commercial use
Whether we care if others open-source improvements
This talk will also show:
Tools that help check license compatibility and avoid problems
Common mistakes made by developers
What businesses or startups expect from open source licenses.
How to apply a license to our project the right way (with examples)
At the end of this session, we’ll get a ready-to-use checklist to help you choose and add the correct license to our project. This session is perfect for college students, individual developers, contributors, or anyone who wants to grow in open source safely and legally.
Key Takeaways
Easy License Selection Method
Learn a step-by-step method to select the right license based on our project goals.
Understand the difference between open sharing (MIT) and required sharing (GPL).
How Licenses Work Together
Know how our project's license must match or work with the licenses of any code you include from outside (dependencies).
Avoid legal conflicts between different types of licenses.
Tools That Save Time
Use tools like FOSSA, WhiteSource Bolt, and license scanners to quickly find out what licenses are in our codebase.
Avoid Common Mistakes
Many projects don’t put any license or choose the wrong one. Learn what mistakes to avoid and how to fix them.
Licensing and Business
Know how our license choice can affect business usage, startup adoption, or enterprise-level contribution.
Checklist & Resources
Get a practical checklist and useful links to apply licensing to our own projects right after the session.
This is a quintessential item for a FOSS project. However, this has been discussed many times over.