Skip to content

Instantly share code, notes, and snippets.

@Shrestha7
Last active June 5, 2024 11:27
Show Gist options
  • Save Shrestha7/4ef7f78c1a8ff61a39bd68c52058a7a6 to your computer and use it in GitHub Desktop.
Save Shrestha7/4ef7f78c1a8ff61a39bd68c52058a7a6 to your computer and use it in GitHub Desktop.
github license guide

How to choose a license for your GitHub repository

“Explain me like I’m 5!” Imagine you made a cool toy, and you want to share it with your friends. But you also want to set some rules for how they can play with it. These rules are like licenses for open source projects. Here are some popular ones:

  • public domain: This is like saying, "Play with my toy however you like! You can even say it's your own."

  • mit license: You say, "You can play with my toy and even change it, but you have to say I made the first version."

  • gnu general public license (gpl): This one's like, "You can play and change my toy, but if you share your changed toy, you must use the same rules I did."

  • apache license: It's like the MIT license, but you also say, "If you make a new version of my toy, tell everyone what you changed."

  • bsd license: You say, "Play with my toy and change it if you want. Just remember to say I made the first one. And don't use my name to say your toy is the best."

  • mozilla public license (mpl): It's like saying, "You can play and change my toy, but if you make a new part, you need to share that new part with the same rules."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment