www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/philosophy po/assigning-copyright.translist...


From: GNUN
Subject: www/philosophy po/assigning-copyright.translist...
Date: Sat, 27 Jun 2020 22:58:40 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     20/06/27 22:58:40

Modified files:
        philosophy/po  : assigning-copyright.translist 
                         assigning-copyright.zh-cn.po 
Added files:
        philosophy     : assigning-copyright.zh-cn.html 
        philosophy/po  : assigning-copyright.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/assigning-copyright.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/assigning-copyright.translist?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/assigning-copyright.zh-cn.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/assigning-copyright.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/assigning-copyright.translist
===================================================================
RCS file: /web/www/www/philosophy/po/assigning-copyright.translist,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- po/assigning-copyright.translist    15 Mar 2020 18:34:45 -0000      1.13
+++ po/assigning-copyright.translist    28 Jun 2020 02:58:40 -0000      1.14
@@ -7,6 +7,7 @@
 <span dir="ltr">[es]&nbsp;<a lang="es" hreflang="es" 
href="/philosophy/assigning-copyright.es.html">español</a> &nbsp;</span>
 <span dir="ltr">[fr]&nbsp;<a lang="fr" hreflang="fr" 
href="/philosophy/assigning-copyright.fr.html">français</a> &nbsp;</span>
 <span dir="ltr">[ru]&nbsp;<a lang="ru" hreflang="ru" 
href="/philosophy/assigning-copyright.ru.html">русский</a> &nbsp;</span>
+<span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/assigning-copyright.zh-cn.html">简体中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/philosophy/assigning-copyright.html" hreflang="x-default" />
@@ -15,4 +16,5 @@
 <link rel="alternate" type="text/html" lang="es" hreflang="es" 
href="/philosophy/assigning-copyright.es.html" title="español" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/philosophy/assigning-copyright.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/philosophy/assigning-copyright.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/assigning-copyright.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/assigning-copyright.zh-cn.po
===================================================================
RCS file: /web/www/www/philosophy/po/assigning-copyright.zh-cn.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- po/assigning-copyright.zh-cn.po     28 Jun 2020 02:33:35 -0000      1.3
+++ po/assigning-copyright.zh-cn.po     28 Jun 2020 02:58:40 -0000      1.4
@@ -13,7 +13,7 @@
 "Language: zh_CN\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit"
+"Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
 msgid ""

Index: assigning-copyright.zh-cn.html
===================================================================
RCS file: assigning-copyright.zh-cn.html
diff -N assigning-copyright.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ assigning-copyright.zh-cn.html      28 Jun 2020 02:58:39 -0000      1.1
@@ -0,0 +1,133 @@
+<!--#set var="ENGLISH_PAGE" value="/philosophy/assigning-copyright.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>当有个企业想要你的版权时 - GNU 工程 - 
自由软件基金会</title>
+<link rel="canonical"
+      href="http://www.fsf.org/blogs/rms/assigning-copyright"; />
+
+<!--#include virtual="/philosophy/po/assigning-copyright.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>当有个企业想要你的版权时</h2>
+
+<p>开发自由软件的企业会按照 GNU GPL
+发布软件,有时也会把某些代码按照å…
¶ä»–方式发布。如果他们把同样的代码按ç…
§ä¸åŒçš„许可证发布给某些付费用户(通常是允许专有软件包
含这些代码),那么我们称之为
+&ldquo;销售例外&rdquo;。如果他们把某些代码版本只按ç…
§ä¸“有形式发布,那么我们称之为发布该程序的一个纯专有版本。</p>
+
+<p><a
+href="/philosophy/selling-exceptions.html">http://www.gnu.org/philosophy/selling-exceptions.html</a>
+解释了为什么销售例外是可以的,尽管是最低限度的可以。反之,发布纯专有版本则完å
…¨é”™è¯¯ï¼Œå°±åƒå…¶ä»–专有软件一样。</p>
+
+<p>企业一般对自己开发的代码才会这样做。因
为他们对这些代ç 
æ‹¥æœ‰ç‰ˆæƒï¼Œæ‰€ä»¥ä»–们可以按任何合法的方式发布这些代ç 
ï¼Œç”šè‡³å¯ä»¥å¹¶è¡Œä½¿ç”¨å¤šç§æ–¹å¼ã€‚当你
要发布这个程序的自由版本的修改版,而该企业想要在å…
¶ç‰ˆæœ¬é‡ŒåŒ…含你的修改时,会发生什么呢?</p>
+
+<p>由于你获得的程序是 GPL,所以当你发布修改版时你必
须使用 GPL。如果原企业获得一份拷贝,那么它也可以按照 GPL
+来使用你的修改;但是它不能在其版本中加入你
的修改并按照销售例外来销售。它也不能发布包含你
的修改代码的纯专有版本。如果你希望如此,那么默认情
况就是这æ 
·ã€‚不过,如果该企业想要销售例外,那么它可能就不会包
含你的修改。</p>
+
+<p>然而,让我们假设,你
并不反对销售例外,也愿意让该企业在销售例外时包含你
的修改。你可以同意此事,但是签字时要看清楚,否则你
会追悔莫及。</p>
+
+<p>该企业可能会让你把版权转让或者
许可给它,这可以通过签署版权转让合同或贡献者
许可证协议达成。这件事本身并不是坏事;例如,许多 GNU
+软件开发者把版权转让给 FSF。不过,FSF
+从不做销售例外,而且签署的转让合同中包
含一个发布承诺:只按照包含源代码的形式发布,只按照å…
è®¸å†å‘布的形式发布。</p>
+
+<p>而企业提供的合同中可能不包含这æ 
·çš„承诺。反之,它可能会允许企业按照其意愿处理你的代ç 
ã€‚如果你签了字,那么企业就可以对你的代ç 
é‡‡å–各种处理。它可能会继续销售包含你的代ç 
çš„销售例外。它也可能会发布包含你代ç 
çš„纯专有版本的修改版或扩展版。它甚至可以
+<em>只在</em> 纯专有版本中包含你的代码。这样,你
贡献的代码实际上就是对专有软件的捐赠。</p>
+
+<p>这些事情的决定权在你,但这里 FSF
+给出一些建议。如果你
计划为此项目做主要的贡献,那么请在贡献者
协议中坚持要求包含你的贡献的软件发布版按ç…
§è‡ªç”±è½¯ä»¶è®¸å¯è¯è®©å…¬ä¼—可得。这也å…
è®¸ä¼ä¸šè¿›è¡Œé”€å”®ä¾‹å¤–,但是禁止其只在专有许可证下使用你
的贡献。</p>
+
+<p>如果你
的贡献不大,那么较弱的条件也可以接受,该企业可以把你
的贡献放在自由软件及非自由软件中。这意味着å…
è®¸è¯¥ä¼ä¸šæŠŠä½ è´¡çŒ®çš„修改仅按ç…
§ä¸“有许可证发布。发布专有软件不是好事,但是如果你
的改动较小,那么改进软件的自由版本比对抗å…
¶éžè‡ªç”±ç‰ˆæœ¬æ›´é‡è¦ã€‚</p>
+
+<p>ä½ 
可以通过在合同中坚持相应的条款来控制以上结果。如果你å…
è®¸å¸¦æœ‰ä½ ä»£ç çš„销售例外,但是不允许企业发布含有你
的贡献的专有版本,那么你可以坚持以下条款:<sup><a
+href="#TransNote1">1</a></sup></p>
+
+<blockquote>
+  <p>FOO 发布的任何带有 Hacker 代码的程序(按照 GNU 通用公å…
±æŽ§åˆ¶ç‰ˆæœ¬ 3 的定义)应该按照 a) &ldquo;GNU
+通用公共许可证(GPL),版本 2 或以后版本可得&rdquo;,或者
 b) 按照以上 (a) 的许可证可得,但是用 &ldquo;2&rdquo;
+已有更高版本号的 GPL 版本。如果 FOO
+按照这样的方式把程序以源代码形式免费发布给å…
¬ä¼—,那么它也可以把同æ 
·çš„程序连接非自由软件并将合并后的二进制程序按ç…
§è‡ªé€‰è®¸å¯è¯å‘布。</p>
+</blockquote>
+
+<p>或者,如果你反对 <em>你的代码</em> 可能会被仅按ç…
§ä¸“有许可证发布,那么你可以坚持以下条款:<sup><a
+href="#TransNote1">1</a></sup></p>
+
+<blockquote>
+  <p>FOO 发布的任何带有 Hacker 代码的程序(按照 GNU 通用公å…
±æŽ§åˆ¶ç‰ˆæœ¬ 3 的定义)应该按照 a) &ldquo;GNU
+通用公共许可证(GPL),版本 2 或以后版本可得&rdquo;,或者
 b) 按照以上 (a) 的许可证可得,但是用 &ldquo;2&rdquo;
+已有更高版本号的 GPL 版本。如果 FOO 按照这æ 
·çš„方式把程序以源代码形式免费发布给å…
¬ä¼—,那么它也可以在其他程序中把同样的 Hacker
+代码按照自选许可证发布。</p>
+</blockquote>
+
+<p>如果程序是按照 GNU Affero GPL 发布的,那么请在 
&ldquo;General&rdquo; 之前添加
+&ldquo;Affero&rdquo;,就是把 &ldquo;GPL&rdquo; 改成 
&ldquo;AGPL&rdquo;,并把 &ldquo;2
+或者&rdquo; 改成 &ldquo;3 或者&rdquo;,把 &ldquo;FOO 发布的&rdquo; 
改成 &ldquo;FOO 发布的,或者
+FOO 在用户可访问的其他服务器上部署的&rdquo; 也可以。</p>
+
+<p>FSF 已经让律师看过这些文字,不过在使用之前,你
还是应该再咨询一下律师。</p>
+
+<p>当企业告诉你它会接受哪些条款时,它就是在向你
展示它的计划究竟和自由软件的理念差别多大。然后你
就可以做出决定来保证你
的贡献是给自由软件社区的,而不是给专有软件的。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<h3>译注</h3>
+<ol>
+<li id="TransNote1">以下部分原文是律师审阅过的,翻译仅
供参考。</li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有关自由软件基金会(FSF) &amp; 
GNU的一般性问题发送到<a
+href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>。也可以通过<a
+href="/contact/">其他联系方法</a>联系自由软件基金会(FSF)。有å…
³å¤±æ•ˆé“¾æŽ¥æˆ–其他错误和建议,请发送邮件到<a
+href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:web-translators@gnu.org";>
+
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方面有评论或一般性的建议,请发送至
 <a
+href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a>。</p><p>å
…³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信息参见
+<a href="/server/standards/README.translators.html">《译者
指南》</a>。</p>
+</div>
+
+<p>Copyright &copy; 2014 Free Software Foundation, Inc.</p>
+
+<p>本页面使用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States License</a> 授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译团队</b>:<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2020。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新:
+
+$Date: 2020/06/28 02:58:39 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/assigning-copyright.zh-cn-en.html
===================================================================
RCS file: po/assigning-copyright.zh-cn-en.html
diff -N po/assigning-copyright.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/assigning-copyright.zh-cn-en.html        28 Jun 2020 02:58:40 -0000      
1.1
@@ -0,0 +1,175 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>When a Company Asks For Your Copyright
+- GNU Project - Free Software Foundation</title>
+<link rel="canonical"
+      href="http://www.fsf.org/blogs/rms/assigning-copyright"; />
+<!--#include virtual="/philosophy/po/assigning-copyright.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>When a Company Asks For Your Copyright</h2>
+
+<p>Companies that develop free software and release it under the GNU GPL
+sometimes distribute some copies of the code in other ways.  If they
+distribute the exact same code under a different license to certain
+users that pay for this, typically permitting including the code in
+proprietary programs, we call it &ldquo;selling exceptions&rdquo;.  If they
+distribute some version of the code solely in a proprietary manner, we
+call that releasing a purely proprietary version of the program.</p>
+
+<p><a 
href="/philosophy/selling-exceptions.html">http://www.gnu.org/philosophy/selling-exceptions.html</a>
 explains why
+selling exceptions is acceptable, though only barely.  By contrast,
+releasing a purely proprietary version is outright wrong, like
+any other proprietary software.</p>
+
+<p>Companies normally do these things using code they
+developed.  Since they hold the copyright on that code, they can
+legally distribute it in any manner, even in multiple manners in
+parallel.  But what happens when you publish a modified version of
+that free program, and the company wants to include your changes in
+its version?</p>
+
+<p>Since you got the program under the GPL, when you distribute a
+modified version you have to license it under the GPL.  If the company
+receives a copy, it will be able to use those changes under the GPL;
+it won't be allowed to include your changes in that program and sell
+exceptions for it.  It also won't be able to release purely
+proprietary versions containing your code.  If this is the outcome you
+want, you get it by default.  However, if the company intends to sell
+exceptions, it will probably decide not to use your changes.</p>
+
+<p>Suppose, though, that you're not opposed to selling exceptions and
+you're willing to let the company do so while including your changes
+in the program.  You can agree to this, but you need to be careful
+about what you sign, or you may be surprised by the results.</p>
+
+<p>The company will probably invite you to assign or license your
+copyright to the company, by signing a copyright assignment contract
+or a contributor license agreement.  That in itself is not inherently bad; for
+instance, many GNU software developers have assigned copyrights
+to the FSF.  However, the FSF never sells exceptions, and its
+assignment contracts include a commitment to distribute the
+contributor's code only with source and only permitting
+redistribution.</p>
+
+<p>The company's proposed contract may not include such a commitment.  It
+might instead let the company use your changes any way it likes.  If
+you sign that, the company could do various things with your code.  It
+could keep selling exceptions for a program including your code.  It
+could release purely proprietary modified or extended versions
+including your code.  It could even include your code <em>only</em> in
+proprietary versions.  Your contribution of code could turn out to be,
+in effect, a donation to proprietary software.</p>
+
+<p>It is up to you which of these activities to permit, but here are the
+FSF's recommendations.  If you plan to make major contributions to the
+project, insist that the contribution agreement require that software
+versions including your contributions be available to the public under
+a free software license.  This will allow the developer to sell
+exceptions, but prevent it from using your contributions in software
+that is only available under a proprietary license.</p>
+
+<p>If your contributions are smaller, you could accept a weaker
+condition, that the company make your contributions available in a
+free software release as well as possibly in nonfree programs.
+This would allow the company to use your contributions in
+modified software that's only available under a proprietary license.
+Releasing proprietary software is never a good thing, but if your
+changes are smaller, it might be more important to improve the free
+version than resist the nonfree versions.</p>
+
+<p>You can control these outcomes by insisting on the proper conditions
+in the contract.  To allow selling exceptions for the program that
+contains your code, but refuse to let the company release purely
+proprietary versions containing your code, you can insist on a
+condition more or less like this:</p>
+
+<blockquote>
+  <p>Any program based on (as defined in GNU General Public License
+  version 3) Hacker's code that FOO distributes shall be made
+  available by FOO under a) the &ldquo;GNU General Public License (GPL),
+  version 2 or later&rdquo;, or b) the licensing in (a), above, but with 
&ldquo;2&rdquo;
+  replaced by any higher existing GPL version number.  Provided FOO
+  makes the program available as source code gratis to the public in
+  this way, it may also distribute the identical program to some of
+  its users under terms permitting them to link the program's code
+  with nonfree code and release the combination in binary form under a
+  license of their own choosing.</p>
+</blockquote>
+
+<p>Or, if what you object to is that some variant <em>of your code</em>
+might be released solely in a proprietary version, you can insist on a
+condition more or less like this:</p>
+
+<blockquote>
+  <p>Any program based on (as defined in GNU General Public License
+  version 3) Hacker's code that FOO distributes shall be made
+  available by FOO under a) the &ldquo;GNU General Public License (GPL),
+  version 2 or later&rdquo;, or b) the licensing in (a), above, but with 
&ldquo;2&rdquo;
+  replaced by any higher existing GPL version number.  Provided FOO
+  makes the program available as source code gratis to the public in
+  this way, it may also distribute the same version of Hacker's code
+  in other programs released under other licenses of its own choosing.</p>
+</blockquote>
+
+<p>If the program is released under the GNU Affero GPL, then add 
&ldquo;Affero&rdquo;
+before &ldquo;General&rdquo;, change &ldquo;GPL&rdquo; to &ldquo;AGPL&rdquo;, 
change &ldquo;2 or&rdquo; to &ldquo;3 or&rdquo;, and
+it could make sense to replace &ldquo;that FOO distributes&rdquo; with 
&ldquo;that FOO
+distributes, or deploys on a server accessible to users other than
+FOO&rdquo;.</p>
+
+<p>The FSF has had these texts reviewed by a lawyer, but you should get
+your own legal advice before using them.</p>
+
+<p>When a company says which of these conditions it will accept, that
+will show you how far it plans to depart from the principles of free
+software.  Then you can respond to ensure your work will contribute to
+the free software community and not be diverted into proprietary
+software.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:web-translators@gnu.org";>
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<p>Copyright &copy; 2014 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2020/06/28 02:58:40 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]