自己的项目如果包含别人的开源代码，licence文件应放在哪里

以下是licence文件内容

Copyright (c) 2008 Alan Szlosek

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.

licence文件放在如图所示的地方可以吗？

回复内容：

以下是licence文件内容

Copyright (c) 2008 Alan Szlosek

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.

licence文件放在如图所示的地方可以吗？

感谢邀请。
我认为你这样放是可以的。

上面@joyqi的回答，是说你自己写的软件，要开源的话，版权声明应该放在什么地方，需要指出的是，文件名不一定是license.txt，也有叫copying（mysql是这样的）、copyright、copyleft、license（无后缀）、开源协议名（xampp就是gpl.txt），甚至还有用html和pdf的。

如果你引用第三方的开源软件，版权文件可以这样放：

1. 保留第三方软件自己的目录结构，在其根目录下一般就有版权声明文件
2. 在你的软件根目录放置它的版权说明，如vemplator_license.txt
3. 如果你引用的第三方软件特别多，你也可以在你的软件根目录建一个文件夹，专门放你引用的各个开源软件的版权文件。

对开源许可证的位置倒没有什么硬性的规定，不过这么多年以来开源社区已经形成了一些自身的约定

在源代码根目录放置LICENCE.TXT文件

你去看所有的开源代码，许可证文件都会放到这个地方，而所有想找这个文件的用户，第一反应也是去这里找这个文件。而且文件名一般都是一个名为LICENCE.TXT的单一文件。

在代码文件注释中声明开源许可

这也是一个好习惯，我们在看国外的代码时，它们的头部一般会有一大段的版权声明，有的时候其长度甚至超过了代码本身，这经常遭到国人的调侃。其实这样做是非常必要的，特别是如果你的代码包括多种风格的开源许可证，那么这样可以为不同的模块分配相应的版权许可。比如一般php代码开头

<?php /**
 * Zend Framework (http://framework.zend.com/)
 *
 * @link      http://github.com/zendframework/zf2 for the canonical source repository
 * @copyright Copyright (c) 2005-2012 Zend Technologies USA Inc. (http://www.zend.com)
 * @license   http://framework.zend.com/license/new-bsd New BSD License
 * @package   Zend_Mvc
 */

只要是可以进行分发的版权，像你这样放在第三方库的各自目录下，没问题。

我建议你可以参考一下yii框架的做法，专门有一个目录放置版权声明。
https://github.com/yiisoft/yii/tree/m...