haiku/License.md

The vast majority of code in this repository was written by the Haiku Project,
and is licensed under the MIT license, which appears below. There are some
notable exceptions to this, such as the GNU C library (which is under the GPL)
as well as many other files in this repository which are under other licenses.
Every piece of source code should have its license specified at the top, but
there is also a (probably) comprehensive set of known licenses in the
`data/system/data/licenses` directory.


The MIT License
-----------------------------------------------------------

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
LICENSE: Rename to License.md, and remove all licenses but the MIT. This file was introduced with the rationale that bots attempt to scrape GitHub repositories for license data. GitHub now has an API for this, and since all its sniffer rules fail because this file is not identical to any known license, it just marks it "Other" and includes the full text anyway. Since this is the case, nobody else wants to look at all the licenses in a single monolithic file, so we just put the explanatory message and a reference to the directory containing all the licenses at the top of the file, and include only the MIT license. Also, GitHub renders Markdown nicer than it does plain text, so use that (which matches what we already do for READMEs.) 2016-07-29 23:28:38 +02:00			`The vast majority of code in this repository was written by the Haiku Project,`
			`and is licensed under the MIT license, which appears below. There are some`
			`notable exceptions to this, such as the GNU C library (which is under the GPL)`
			`as well as many other files in this repository which are under other licenses.`
			`Every piece of source code should have its license specified at the top, but`
			`there is also a (probably) comprehensive set of known licenses in the`
			`data/system/data/licenses` directory.


			`The MIT License`
			`-----------------------------------------------------------`

			`Copyright (c) <year> <copyright holders>`

			`Permission is hereby granted, free of charge, to any person obtaining a copy`
			`of this software and associated documentation files (the "Software"), to deal`
			`in the Software without restriction, including without limitation the rights`
			`to use, copy, modify, merge, publish, distribute, sublicense, and/or sell`
			`copies of the Software, and to permit persons to whom the Software is`
			`furnished to do so, subject to the following conditions:`

			`The above copyright notice and this permission notice shall be included in`
			`all copies or substantial portions of the Software.`

			`THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR`
			`IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,`
			`FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE`
			`AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER`
			`LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,`
			`OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN`
			`THE SOFTWARE.`