Skip to main content
Selecting an open source license is a pivotal step when launching a community-driven software project. It not only determines how others can use, modify, or distribute your code but also defines your project’s governance model. With your idea validated and infrastructure ready, this guide will help you navigate the two main license categories and publish your project with confidence.
The image shows four icons of documents with checkmarks, accompanied by the text "Let's Choose a License."
To streamline your decision:
  • Identify your goals: community contributions, commercial adoption, or strict sharing.
  • Compare license obligations: attribution, copyleft reciprocity, patent grants.
  • Align with your project’s mission and long-term vision.
Always review the full legal text of any license and consider consulting a legal professional for complex projects.

​
License Categories

License TypeKey FeatureCommon Examples
CopyleftDerivatives must carry the same licenseGPL, AGPL, LGPL
PermissiveMinimal restrictions; requires attributionMIT, Apache 2.0, BSD-3-Clause

​
Copyleft Licenses

Copyleft licenses ensure that every modification or fork remains free and open by requiring derivative works to inherit the same terms as the original. This model fosters a collaborative ecosystem where improvements stay within the community.
The image shows a diagram with the label "COPY LEFT" and icons representing a document with a checkmark and a hexagon with a keyhole.
Key considerations:
  • Enforces reciprocity for downstream users
  • Protects community contributions from being closed-source
  • May deter commercial adopters who need proprietary integration

​
Permissive Licenses

Permissive licenses offer maximum flexibility by allowing your code to be used in both open source and proprietary projects. The only typical requirement is to retain the original copyright notice and license text.
The image is a diagram with two sections, highlighting "Permissive" licenses with minimal restrictions.
Why choose permissive?
  • Broad commercial adoption
  • Fewer barriers for contributors
  • Ideal for libraries or tools aiming for wide integration

​
Publishing Your Project

Once you’ve chosen a license, make it official:
  1. Add a LICENSE file at your repository root.
  2. Reference the license in your README.md.
  3. Tag your initial release to mark your project’s version history.
The image features a network diagram with interconnected nodes and icons for GitHub and GitLab, suggesting a focus on version control or software development.
Popular hosting platforms:
  • GitHub – the largest development community
  • GitLab – built-in CI/CD pipelines and self-hosting options
Mismatched license files or missing attributions can lead to legal complications. Double-check that your repository includes the correct LICENSE and copyright notices.

Watch Video