需要在源头中对经过大量修改的OSS代码(BSD,Apache等)的归属/版权提出建议 [英] Need advice on attribution/copyright of heavily modified OSS code (BSD, Apache, etc) in source headers

查看:77
本文介绍了需要在源头中对经过大量修改的OSS代码(BSD,Apache等)的归属/版权提出建议的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个关于使用许可许可(BSD,Apache,MIT等)源的问题,原始源代码和借用代码之间的界限可能会非常模糊.

I've got a question about use of permissive-licensed (BSD, Apache, MIT, etc) source where the line may be heavily blurred between original code and borrowed code.

我们很高兴根据许可证的要求公开原始来源的版权.

We are more than happy to disclose a copyrights for original source as required by the licenses.

我想知道的具体情况是如何正确更新已修改文件中的源头.

The specific case I'm wondering about is how to correctly update source headers in files I've modified.

假设您有其他项目要使用的资源.它包含一个类似于以下内容的标题.

Assume you have some source from another project you'd like to make use of. It contains a header like the following.

/*
 * Copyright (C) 2006, 2007 John Doe.
 * Copyright (C) 2008, 2009 Project comitters.
 * All rights reserved.
 *
 * The software in this package is published under the terms of the BSD
 * style license a copy of which has been included with this distribution in
 * the LICENSE.txt file.
 * 
 * Created on 07. March 2004 by John Doe
 */

对于一个简单的错误修复程序,我将做一些小的更改,将其发送给上游,并希望该修复程序得到合并.完成后,我将删除补丁版本,然后返回主线.

For a trivial bug fix, I would just make my small change, send it upstream and hope the fix gets incorporated. When it does, I would drop my patched version and go back to mainline.

有时我想将源用作跳出点.随着时间的流逝,它得到了改造,并进行了重新设计和改进.它可能类似于原始代码,但到那时肯定是我们自己的工作.

Some times I want to use the source as a jumping off point. It gets transformed over time and reworked and improved. It may resemble the original code but it certainly would be our own work by that point.

那可以用我自己的标头替换吗?我是否应该写类似基于John Doe的原始XYZ"的内容?

Is it ok then to replace that header with my own? Should I just write something like "Based on original XYZ by John Doe"?

推荐答案

BSD系列许可证明确禁止您修改或删除其标头.

The BSD family of licenses expressly forbid you from modifying or removing their headers.

我想我应该对此做更深入的研究.

I suppose I should go more into depth on this.

从本质上讲,您使用他们的代码作为自己的基础.由于这种影响,您仍然受原始许可证的约束,因此必须保留原始归属.

Essentially, you used their code as a basis for your own. Due to that influence, you are still bound by the original license, and thus have to keep the original attribution intact.

这篇关于需要在源头中对经过大量修改的OSS代码(BSD,Apache等)的归属/版权提出建议的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆