Merge pull request #116 from coding-for-reproducible-research/add-license-content

Add content on licenses to Software Development Best Practices course

Author: liamjberrisford

individual_modules/software_development_best_practices/reproducibility.ipynb

@@ -44,6 +44,39 @@
     "    - Implement testing and continuous integration.\n",
     "- **Documentation and Access**: Make code and data available on sharing platforms with comprehensive documentation.\n",
     "\n",
+    "## Choosing and Including a License\n",
+    "\n",
+    "When it comes to reproducible research, including a license with your code is crucial. A license ensures that others can reuse, modify, and build upon your work legally. Without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. [GitHub License Documentation](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)\n",
+    "\n",
+    "### Why Licensing is Essential\n",
+    "\n",
+    "- **Legal Clarity:** A license provides clear terms under which your code can be used, modified, and shared.\n",
+    "- **Encourages Collaboration:** It allows other researchers to confidently build upon your work.\n",
+    "- **Promotes Reproducibility:** Licensing your code ensures that others can replicate your results, learn from your methodologies, and advance the research.\n",
+    "\n",
+    "### How to Choose a License\n",
+    "\n",
+    "Selecting the right license can be daunting, but here are some resources to help you:\n",
+    "- **[Choose a License](https://choosealicense.com/):** A great website to guide you through the process of selecting a license that fits your needs.\n",
+    "\n",
+    "### Adding a LICENSE File\n",
+    "\n",
+    "To include a license in your repository:\n",
+    "1. **Choose a License:** Use resources like [Choose a License](https://choosealicense.com/) to select the appropriate license.\n",
+    "2. **Add a LICENSE File:** Create a file named `LICENSE` in the root of your repository and include the text of the license you chose.\n",
+    "3. **Reference the License in Your Documentation:** Make sure to mention the license in your README file and other relevant documentation.\n",
+    "\n",
+    "### Common Licenses\n",
+    "\n",
+    "Here are some commonly used licenses in the open-source community:\n",
+    "- **MIT License:** A permissive license that is short and to the point. It lets people do almost anything with your project, like making and distributing closed-source versions.\n",
+    "- **GPL License:** A copyleft license that requires anyone who distributes your code or a derivative work to make the source available under the same terms.\n",
+    "- **Apache License:** A permissive license that also provides an express grant of patent rights from contributors to users.\n",
+    "\n",
+    "Including a license is a simple step that significantly enhances the impact and reach of your research by ensuring that it can be freely and legally reused. Make sure to include a LICENSE file in your repository to support open science and reproducible research.\n",
+    "\n",
+    "For more detailed guidance, visit our the [University of Exeter Copyright and Licences page](https://www.exeter.ac.uk/research/openresearch/oa/copyright/)\n",
+    "\n",
     "## Summary Quiz"
    ]
   },