📘
Engineering Communications Program Team Projects
Open Source Guide
Open Source Guide
  • Welcome
  • Creators
    • Reasons to create
    • Create a repository
      • Set up documentation
        • README
        • CONTRIBUTING
        • License
    • Name your project
    • Build a community
      • Communication Mediums
        • Mass Notifications
        • Formal Exchanges
        • Real-Time Messaging
      • Code of Conduct
    • Additional Resources
  • Contributors
    • Reasons to contribute
    • Find a project
      • GitHub Trending
    • Ways to contribute
    • Choose an issue
    • Read supporting documentation
    • Git Workflow
      • Fork a project
      • Create a branch
      • Add a commit
      • Submit a pull request
      • Review code
Powered by GitBook
On this page
  1. Creators
  2. Create a repository
  3. Set up documentation

License

Protecting yourself legally

PreviousCONTRIBUTINGNextName your project

Last updated 3 years ago

The license is the last of the three main documentation files. An open source license complies with open source standards and ensures that your project can be replicated, used, and contributed to by others. In the event of legal issues, a license protects you. A license is essential for an open source project to truly be open source.

If you’re not a lawyer that’s alright because luckily there are a lot of licenses that are available for you to use for free. The MIT license is the most common for open source projects but there are plenty of others such as the Apache License 2.0 or the Common Development and Distribution License. All of these licenses serve the same purpose but you're free to check the differences on your own. Below is an external resource that covers many of the common open source licenses.

Licenses & Standards | Open Source Initiative
Example of the MIT License of GitHub
Logo