派生Apache License v2开源项目和版权声明 [英] Forking an Apache License v2 open source project and copyright notices

问题描述

我打算分叉一个开源项目，该项目已获得Apache License v2的许可.现有的大多数资源的标题中都有版权声明，版权bla bla，Inc..

I'm planning to fork an open-source project which is licensed under Apache License v2. Most of the existing sources have a copyright notice in the heade, Copyright bla bla, Inc.

如果我在分叉中更改了某些来源(即使只是少量更改)，那么版权会如何处理?它会成为版权bla bla，Inc和Thomas"这样的联合版权声明吗?

If I change some these sources in my fork (even if only marginally), what happens to the copyright? Will it become a joined copyright notice like "Copyright bla bla, Inc and Thomas"?

推荐答案

免责声明:我不是律师，而只是软件开发人员.这只是我个人的看法，在每种具体情况下，如果您需要法律帮助，则必须代表您与法律团队联系.

Disclaimer: I'm not a lawyer, just a software developer. This is just my own opinion, in each concrete case if you need legal help you must talk to a legal team on your behalf.

如果我在分叉中更改了某些来源(即使只是很小的改动)，版权会发生什么?

If I change some these sources in my fork (even if only marginally), what happens to the copyright?

保留其代码的版权.如果删除代码，则不再有版权.如果您修改了代码，就像您已经假设的那样，这些代码行具有版权，而新代码行具有版权.

The copyright remains for it's code. If you remove the code, there is no copyright any longer. If you modify the code, it's like you already assume, there is copyright for those lines of code, and copyright for the new lines of code.

它将成为像版权bla bla，Inc和Thomas"这样的联合版权声明吗?

Will it become a joined copyright notice like "Copyright bla bla, Inc and Thomas"?

如果每个文件都有通知:如果您不更改文件，请按原样保留它，包括版权标头.

If there is a notice per file: If you don't change the file, keep it as-is including the copyright header.

如果您对文件进行更改，通常会将新版权放在文件顶部，然后可以看到这是基于先前的代码，然后是原始车牌.大多数许可证都要求您不要更改原始的版权/许可证通知，这一点很重要，否则您通常会失去使用该软件的权利(例如，分叉它).

If you make changes to the file, normally the new copyright is put on top of the file, then making it visible that this is based on the previous code and then the original license plate follows. Most licenses require that you do not change the original copyright/license notice, this is important otherwise you normally loose the rights to make use of the software (e.g. fork it).

重要的是清楚地知道哪个代码属于哪个版权，因此您也要自己记录下来.使用上述方法，您可以知道已修改了哪些文件(以及哪些文件保持未修改).

The important part is that it's clear which code falls under which copyright, so you have it documented on your own as well. With the method described, you know which files you have modified (and which files remain unmodified).

使用版本控制软件，以便您可以进行任何更改.

Use version control software so you can follow any changes.

即使GPL不适用于您的分叉，一篇不错的文章是:维护GPL许可项目中的许可许可文件:开发人员指南.

A good article, even if GPL does not apply for your fork, is: Maintaining Permissive-Licensed Files in a GPL-Licensed Project: Guidelines for Developers.

这篇关于派生Apache License v2开源项目和版权声明的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！