![]() A work that constitutes a Collective Work will not be considered a Derivative Work (as defined below) for the purposes of this License. Means a work, such as a periodical issue, anthology or encyclopedia, in which the Work in its entirety in unmodified form, along with a number of other contributions, constituting separate and independent works in themselves, are assembled into a collective whole. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.īY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE CREATIVE COMMONS PROVIDES THIS INFORMATION ONĪN "AS-IS" BASIS. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE ANĪTTORNEY-CLIENT RELATIONSHIP. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional.CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. GitHub displays license information to help users get information about open source licenses and the projects that use them. The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. For more information on adding a license to a repository, see " Adding a license to a repository." Disclaimer You can manually add a license using the browser. The license picker is only available when you create a new project on GitHub. Applying a license to a repository with an existing license To have your license detected, simplify your LICENSE file and note the complexity somewhere else, such as your repository's README file. If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. ![]() If your repository is using a license that isn't listed on the Choose a License website, you can request including the license. Licensee also provides the Licenses API and gives us insight into how repositories on GitHub are licensed. The open source Ruby gem Licensee compares the repository's LICENSE file to a short list of known licenses. For more information, see " Searching for repositories." Detecting a license For example, when you use the query license:gpl, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. When you search by a family license, your results will include all licenses in that family. University of Illinois/NCSA Open Source License ![]() LicenseĬreative Commons Attribution ShareAlike 4.0ĭo What The F*ck You Want To Public License You can filter repositories based on their license or license family using the license qualifier and the exact license keyword. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license."Īs a best practice, we encourage you to include the license file with your project. Some projects include information about their license in their README. ![]() Most people place their license text in a file named LICENSE.txt (or LICENSE.md or LICENSE.rst) in the root of the repository here's an example from Hubot. For more information, see " Setting repository visibility." Determining the location of your license When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. Note: If you publish your source code in a public repository on GitHub, according to the Terms of Service, other users of have the right to view and fork your repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |