Your project if it contains someone else's open source code, where should the licence file be placed

The following is the contents of the licence file

Copyright (c), Alan Szlosekpermission is hereby granted, free of charge, to all person obtaining a copyof this Softwar E and associated documentation files (the "Software"), to dealin the software without restriction, including without limit ation the Rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to PE  RMIT persons to whom the software isfurnished to does so, subject to the following conditions:the above copyright notice and This permission notice shall being included inall copies or substantial portions of the Software.the software is provided "A S is ', without WARRANTY of any KIND, EXPRESS orimplied, including and not LIMITED to the warranties of Merchantability,fit NESS for A particular PURPOSE and noninfringement.  In NO EVENT shall theauthors or COPYRIGHT holders is liable for any CLAIM, damages OR otherliability, WHETHER in an ACTION of contract, TORT or OTHERWISE, arising from,out of or in CONNECTION with the software or theUse OR other dealings inthe software. 

Where can I put the licence file?

Reply content:

The following is the contents of the licence file

Copyright (c), Alan Szlosekpermission is hereby granted, free of charge, to all person obtaining a copyof this Softwar E and associated documentation files (the "Software"), to dealin the software without restriction, including without limit ation the Rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to PE  RMIT persons to whom the software isfurnished to does so, subject to the following conditions:the above copyright notice and This permission notice shall being included inall copies or substantial portions of the Software.the software is provided "A S is ', without WARRANTY of any KIND, EXPRESS orimplied, including and not LIMITED to the warranties of Merchantability,fit NESS for A particular PURPOSE and noninfringement.  In NO EVENT shall theauthors or COPYRIGHT holders is liable for any CLAIM, damages OR otherliability, WHETHER in an ACTION of contract, TORT or OTHERWISE, arising from,out of or in CONNECTION with the software or theUse OR other dealings inthe software. 

Where can I put the licence file?

Thank you for inviting me.
I think it is possible for you to put it this way.

The above @joyqi answer is that you write your own software, to open source, the copyright notice should be put in place, it should be noted that the file name is not necessarily license.txt, there is also called copying (MySQL is such), Copyright, copyleft, License (no suffix), open source protocol name (XAMPP is Gpl.txt), and even useful HTML and PDF.

If you refer to a third party's open source software, the copyright file can be placed like this:

1. Retain the third-party software's own directory structure, in its root directory generally have a copyright notice file
2. Place its copyright note in your software root directory, such as Vemplator_license.txt
3. If you refer to a particular number of third-party software, you can also set up a folder in your software root directory, specifically for the various open source software you refer to the copyright files.

There are no hard rules for the location of open source licenses, but for many years the open source community has formed some of its own conventions.

Place the LICENCE.TXT file in the source code root directory

You go to see all the open source code, the license file will be placed in this place, and all the users who want to find this file, the first reaction is to go here to find this file. And the file name is usually a LICENCE.TXT single file named.

Declaring an open source license in a code file comment

This is also a good habit, when we look at foreign code, their head will generally have a large section of the copyright statement, sometimes its length even more than the code itself, which is often the people's ridicule. In fact, this is necessary, especially if your code includes multiple styles of open source licenses, so you can assign the appropriate copyright permissions to different modules. such as the general PHP code beginning

 
                                          
                                    
As long as it is possible to distribute the copyright, such as you put in the third-party library of the respective directory, no problem.
                                        
                                    
I suggest that you refer to the YII framework practice, which has a directory where the copyright notice is placed.
Https://github.com/yiisoft/yii/tree/m ...
