[02] The copyright agreement that programmers must know

A while ago, there was a lot of discussion about copyright issues on Zhihu. For example,  who is the "Zhihu God" on Sina Weibo? Alleged infringement? , and recently Himalayan FM has also caused many columns to be taken off the shelf and postponed due to the copyright issue of background music. As a magician who likes to share, I have also encountered some copyright-related issues. I just took this opportunity to share with everyone Open Source License and Creative Commons License.


open source protocol

I believe that many small partners follow the principle of not repeating the creation of wheels (lazy) by default when developing. As long as you have an idea, you can immediately search on GitHub to see if someone has done it. If it has been done, naturally You're welcome, just take it over and modify it and you can use it.pick up(LOL). However, you may not have noticed that there are some traps (constraints) in many open source codes, which are open source protocols. Let's take a look at open source protocols.

Why add an open source license?

The first is the protection of authors to prevent knowledge achievements from being maliciously used.

  • The open source agreement generally contains a disclaimer (the author of the code is prohibited from bearing the risks and consequences of using the code). For example, if you open source a code to crack a smart lock, if someone uses this to steal and cause losses to others, you do not need to bear the responsibility. responsible.

The second is the protection of the user, which is convenient for the user.

  • Users can see at a glance which operations they are allowed to perform and which operations are not allowed.
  • By default, the code without the agreement is reserved by the author (the laws of different countries may be slightly different), which is like a time bomb. If you use this code without agreement in the project, the original author As long as you can prove that you used his code without permission, you can sue you.
How to choose the right open source protocol?

Since there are many types of open source protocols, it is difficult for ordinary people to understand the difference between them. Even common protocols do not fully know the content of the protocol. So how to quickly choose a protocol that suits you? If you are a person who is afraid of trouble, the following suggestions may be helpful to you.

Quick selection protocol

At present, the MIT protocol is the most used, and the Apache License 2.0 protocol is commonly used by me (GcsSloop)   , because it can help me know which open source projects use my content, and what modifications have been made, which will help me improve myself. project.

The reason why this protocol is adopted instead of  GNU GPLv3  is because  GNU GPLv3  users must open source according to the same protocol, and the  Apache License 2.0  is relatively loose, you can use it privately or closed source, but if the open source project uses At the time, you only need to place the copyright notice and the modification notice.

The three protocols described above are the most commonly used ones. If you want to choose more open source protocols, you can go to  Choose an open source software protocol to  view. This website was created by GitHub. I did some minor translation work.  an open source license  If you feel that some of my translations are inaccurate, you can go to  ChooseLicense.github.io  to give me suggestions. It would be better if you submit a Pull Request directly.

Note: No matter what protocol you use, once you publish your content on some platform, you accept the platform's agreement by default. This is especially important to note. For example, on GitHub, others are allowed to view and fork your open source project by default. .


Creative Commons

Creative Commons is also a type of copyright agreement, which is often used in data, multimedia, websites, articles and other content, and is a barrier for authors to protect their rights and interests.

There are many versions of Creative Commons (also known as CC), but it should be noted that Creative Commons does not apply to open source software.

注意:虽然你可以采用知识共享协议来保护你的内容,但是一旦你在某些平台上发布你的内容,你就默认接受了该平台的协议,这一点尤其需要注意。

下面我们来看两个例子,仅看知识产权部分的:

百度的知识产权声明:

知乎的知识产权声明:

对比一下,你在百度上发表的任何东西,不论是百度知道,百度文库或者是贴吧,百度自动拥有版权,可以随意使用这些内容,而在知乎上的回答,文章等则是作者拥有版权,知乎拥有使用权,当然了,前提是你为原创作者。

你可以到 creativecommons.org 为自己选择一个合适的知识共享协议。

我的文章、原创图片等其他非代码内容一般会采用 知识共享 署名-非商业性使用-禁止演绎 4.0 国际 许可协议。你在我的 AndroidNote 和我的 个人网站 底部均可以看到声明。

这在知识共享协议里面算是比较严苛的一个协议了,它允许所有人在非商业用途下免费转载我的文章,但必须:

  • 保持原文,不作修改。
  • 明确署名,即至少注明 作者:GcsSloop 字样以及文章的原始链接,且不得使用 rel="nofollow" 标记。
  • 商业用途可以联系本人,需要征得本人同意。

下面解释一下我为什么要采用这一个协议:

禁止商用

这个毋庸置疑,为了保证自身的利益,写一篇文章需要经过选材,制作图片,书写,排版,排查错误等诸多步骤,其中每一步都凝聚了作者大量的心血,如果被别人一声不吭拿去为自己赚钱了,作者岂不是要哭晕在厕所。

保持原文

之前又一个文章中因为一个公式问题引起了一些混乱,那篇文章中本身公式是正确的,可能是因为书写方式问题,导致一些小伙伴错认为是有误的,而且有小伙伴在fork我的仓库后修改了文章中的公式,之后有小伙伴讨论这个公式的问题,因为担心小伙伴看到的是错误版本,在这个问题上浪费了很多时间。所以我的文章转载均要求保持原文,如果你觉得我的文章中有错误的地方,可以到评论区或者其他地方告诉我。

明确署名

保持署名和原始链接可以保证其他人能找到原文的作者,如果文章出现了问题,能够反馈给原作者,以保证文章内容正确,不误导以后阅读的人。


关于参考链接

我们人类之所以发展这么快,是因为有前人的努力,我们都是站在巨人肩膀上的人,书写文章也不例外,有很多需要借鉴他人的地方,如果借鉴了他人的想法或者成果,建议在文末加上参考链接。除了能够帮助读者更好理解知识的来源外,也可以顺便给这些人带来一些名气。


我书写参考链接的规则一般是这样的,我借鉴了他人的想法,成果,或者一部分成果,我都会在文末添加上文章地址。


有时候有小伙伴会反馈说,我的文章和我参考链接里面的文章有些地方存在冲突,这是因为我并没有把原文中这一部分作为参考。如果一些文章的理论本身就是错误的,但思路是正确的,或者部分内容是正确的,我使用了这些内容,同样会将其加入我的参考链接中。


关于抄袭和洗文(洗稿)

抄袭(英语:plagiarism),亦称作剽窃,根据教育部国语辞典定义[1],为抄录他人作品以为己作。对于原著未经或基本未经修改的抄录,这是一种侵犯著作权的行为。(引用自维基百科)

抄袭属于一种比较低级的方式,更高级一点的一般称为洗文或者洗稿,常见洗稿有以下的方式:

第一种是打乱排版排版,然后用近似的语句来表达原文的内容。

第二种是按照原作者类似的风格来书写一件类似的事情,对其中对内容稍作修改。

The third type is mainly for articles that are not allowed to be reprinted, first plagiarize them to a certain forum or an unknown website, and then reprint it and mark it as a certain forum (website), and easily erase the original author information.

This kind of manuscript washing article is a headache for the original author. Some new drivers are not skilled, and they can tell it is manuscript washing at a glance, while for some old drivers, the washed articles are difficult to identify and it is difficult to protect their rights. But if you have the time to confront the plagiarist, there is still a good chance of getting justice. After all, the eyes of the masses are sharp, but what does this mean to you? Waste of time and nothing in return.



It is precisely because the cost of plagiarism is low and the cost of rights protection is high that there is a large amount of plagiarized content. Baidu search results are especially obvious. Many top-ranking technical articles are not the original text of the author, but have been reprinted (plagiarized) by some big platforms. . In contrast, Google is much better, and the processing speed of reporting plagiarism is also very fast.

Take for example an article I posted earlier:

 


The first item in the Google search results is my original address, and the first item in the Baidu search results is the reprinted (plagiarized) article. I have never contributed this article on this platform. Although this reprinted (plagiarized) article is The original address is given at the end of the article, but it is not in the form of a hyperlink, without the author's signature, and the website also has advertisements, because the advertising revenue generated by this article will not give the author a penny, which has actually seriously violated my Creative Commons protocol.


You ask why I didn't report it?

The main reason is that this reprint is quite conscientious, at least the typesetting is not messy, and it can help some beginners. If you want to tamper with the original link, the typesetting is messy, and a large number of advertisements are inserted, which seriously affects the viewing effect, I must see one report one.


Epilogue

Choose a suitable open source agreement or Creative Commons agreement for yourself. Although it is not useful most of the time, it can at least protect your rights to a certain extent.

Finally, I recommend using Google more and staying away from Baidu.


Related Websites

Choose an Open Source Software License

Choose a Creative Commons Agreement





**

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324730675&siteId=291194637