[incubator-echarts] 06/07: fix: add some hints for copyright.

[su...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sushuang pushed a commit to branch release
in repository https://gitbox.apache.org/repos/asf/incubator-echarts.git

commit 927c3e9be52c9d44b2b44d96186ced717e5e844f
Author: sushuang <su...@gmail.com>
AuthorDate: Sun Sep 8 02:30:37 2019 +0800

    fix: add some hints for copyright.
---
 .github/CONTRIBUTING.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 6e8ca44..20b8a6c 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -82,3 +82,30 @@ Then, open the test cases under `~/workspace/echarts/test` in Web browser. You c
 Fork ECharts project into your own project. Checkout a branch from master branch named `fix-xxxx`, where xxxx is the issue id related. If there's no related issue, you need to create one in most cases to describe what's wrong or what new feature is required.
 
 If you are a committer of apache/incubator-echarts project, which means you have the write access to the project, you still need to push to a new branch (by `git push origin HEAD:refs/heads/fix-xxxx`) and use pull request to push your code. You cannot push code directly to `master` branch, otherwise it will be rejected by GitHub.
+
+
+## Some hints about using code from other authors
+
++ About using some algorithms/formulas or inspired by other's work:
+    + We can be inspired from other people’s work. There is no problem with copying ideas and no problems associated with that so long as the code is entirely yours and you aren’t violating the license of the inspirational work. You can just follow "normal" source code rules.
+    + But when you copy the code, even parts of files, it must remain under the copyright of the original authors.
+    + What's the right thing to do for the public good here? I'll go with:
+        + Be transparent when implementing an existing idea/algorithm.
+        + Reference where that idea/algorithm came from.
+        + Use standard language when doing so (we need to define standard language).
+            + "inspired by", "learned from" and "references to" are vague concepts in copyright.
+        + If any copyrightable expression is copied from the existing idea/algorithm, compare its licensing to our licensing policies and include licensing accordingly.
+    + Check the original discussion about it in: https://lists.apache.org/list.html?legal-discuss@apache.org:lte=36M:echarts
++ About adding the license/header of 3rd-party work:
+    + https://www.apache.org/legal/src-headers.html#3party
++ Licenses that are compatible with the Apache license:
+    + BSD and MIT are compatibal with the Apache license but CC_BY_SA is not (https://apache.org/legal/resolved.html#cc-sa).
++ Stack overflow:
+    + before intending to copy code from Stack overlow, we must check:
+    + https://apache.org/legal/resolved.html#stackoverflow
+    + https://issues.apache.org/jira/browse/LEGAL-471
++ Wikipedia:
+    + Wikipedia is licensed CC 4.0 BY_SA and is compatible with the Apache license. So we should not copy code from Wikipedia.
++ Working in progress disclaimer:
+    + In some cases we might use the work in progress disclaimer and document the issues in that until they are fixed.
+    + https://incubator.apache.org/policy/incubation.html#disclaimers


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org