IANAL so none of this addresses legal requirements. The individual license will determine this and you should seek professional advice. My answer speaks only to the ethics of using open source software.
The main principle is that if you use an open source project you should credit that project in a way that could be seen but isn't invasive to your website or app. A "Powered by Python" logo on every Webpage is invasive. A paragraph with a link to the project URL on a help page is quite acceptable (imho).
Desktop applications: on the Help menu put an "About" link that describes the technologies used and gives appropriate credits. IMHO noone reads README files.
Web Sites: if they have a menu, you can do the same thing. Alternatively you can put it as a question in your FAQ. If there's no menu (or possibly in addition to that), you can put a link to that information in the footer (which is small and non-invasive). Eitehr as a separate link or on another relevant link.
Any of the credits should include a link to the project or company homepage.
FYI Some open source project are licensed under a "copyleft" license, which means that any derivative work must also be open source.
You should be careful with that, especially for GPL codes, if they does not explicitly state that you can use the lesser-GPL license and you accidently modified the GPL-ed code (fix a bug, some minor enhancements etc.) you might be up for trouble.
The best thing you can do is fully read the license that the library is released under and interpret what the requirements are from that. There's just no substitute. From there you can look at other projects that use the same libraries (check out sourceforge.net, where you can also filter projects by license) and see what they do.
发布评论
评论（4）
IANAL 因此这些都没有解决法律要求。 个人许可证将决定这一点，您应该寻求专业建议。 我的回答仅涉及使用开源软件的道德规范。
主要原则是，如果您使用开源项目，您应该以一种可以看到但不会侵入您的网站或应用程序的方式来认可该项目。 每个网页上的“Powered by Python”徽标都是侵入性的。 帮助页面上包含项目 URL 链接的段落是完全可以接受的（恕我直言）。
桌面应用程序：在“帮助”菜单上放置一个“关于”链接，描述所使用的技术并给出适当的说明。 恕我直言，没有人读自述文件。
网站：如果它们有菜单，您也可以执行相同的操作。 或者，您可以将其作为常见问题解答中的问题。 如果没有菜单（或者可能除此之外），您可以在页脚中放置指向该信息的链接（该链接很小且非侵入性）。 作为单独的链接或另一个相关链接。
任何学分都应包含指向项目或公司主页的链接。
IANAL so none of this addresses legal requirements. The individual license will determine this and you should seek professional advice. My answer speaks only to the ethics of using open source software.
The main principle is that if you use an open source project you should credit that project in a way that could be seen but isn't invasive to your website or app. A "Powered by Python" logo on every Webpage is invasive. A paragraph with a link to the project URL on a help page is quite acceptable (imho).
Desktop applications: on the Help menu put an "About" link that describes the technologies used and gives appropriate credits. IMHO noone reads README files.
Web Sites: if they have a menu, you can do the same thing. Alternatively you can put it as a question in your FAQ. If there's no menu (or possibly in addition to that), you can put a link to that information in the footer (which is small and non-invasive). Eitehr as a separate link or on another relevant link.
Any of the credits should include a link to the project or company homepage.
仅供参考 某些开源项目是根据“copyleft”许可证获得许可的，这意味着任何衍生作品也必须是开源的。
您应该小心这一点，特别是对于 GPL 代码，如果它们没有明确声明您可以使用较小的 GPL 许可证，并且您不小心修改了 GPL 代码（修复错误、一些小的增强功能等），您可能会准备好惹麻烦了。
读物： http://www.gnu.org/copyleft/
这里有一篇关于 Copyleft 的好 抛开担忧不谈，就像 @cletus 一样：将适当的积分放在适当的位置是一个好主意。
FYI Some open source project are licensed under a "copyleft" license, which means that any derivative work must also be open source.
You should be careful with that, especially for GPL codes, if they does not explicitly state that you can use the lesser-GPL license and you accidently modified the GPL-ed code (fix a bug, some minor enhancements etc.) you might be up for trouble.
Here is a good read on copyleft: http://www.gnu.org/copyleft/
Legal concerns aside, as with @cletus: putting proper credits in proper places is a good idea.
您能做的最好的事情就是充分阅读该库发布所依据的许可证，并解释其中的要求。 没有替代品。 从那里您可以查看使用相同库的其他项目（查看 sourceforge.net，您还可以在其中按许可证过滤项目）并查看它们的功能。
The best thing you can do is fully read the license that the library is released under and interpret what the requirements are from that. There's just no substitute. From there you can look at other projects that use the same libraries (check out sourceforge.net, where you can also filter projects by license) and see what they do.
这就是我们在我们正在开发的网站上所做的：
http://www.cartell.ie/about-us/open-source-学分/
This is what we did on a site we were working on:
http://www.cartell.ie/about-us/open-source-credits/