问题描述
我一直在关注有关许可证的火焰战争。
参与这个行业的人有很多动机，所以
对许可证的分歧反映这些议程。
我没有议程，至少现在没有。我打算写一些
几个程序。
这些将是我需要的固件测试工具。它们将是b / b
相对简单的东西，比如用于分析数据的工具，以便于查看，通过串口发送命令/宏，
等类似的事情存在，但他们不做我需要的一切。这些
对我来说也是一个很好的学习机会，因为我仍然对Python很不稳定。
如何我决定许可证吗？是否有任何网站总结
的利弊？我想我不太关心其他人如何使用它。这些东西不够全面，或者没有足够的吸引力，有人会在他们身上涂上一层新的油漆
并尝试出售它们。我想我不在乎是否有人把它们变成了更大的东西。如果有人要为他们添加功能，
那么获得代码并将衍生作品保持为开放
来源会很好，但我不认为对我来说很重要。如果
有人可以增加价值并找到一种赚钱的方式，我就不会因为我太不高兴了。
我将在我自己的时间内完成大部分编码，因为我需要
才能在我更换雇主时随身携带这些工具。
但是，我确信在使用这些工具的过程中，我需要花时间调试或调整它们。
。我不希望我的
当前雇主以任何方式对我的代码提出任何索赔。通常，如果您在公司时间编程，那就会使您的工作成为为雇佣而工作。
我不会像这样污染我的代码。这是否意味着GPL在这种情况下是最强的防御？
我愿意接受有关考虑哪些许可证的建议。但是，
请尽量将对话与决策过程保持一致，或者
听起来最好是为此目的。让我们保持更广泛的问题
哪个许可证将导致西方文明的垮台
另一个问题。
Ron Britton
（下一行的乱码真的是我的电子邮件地址。）
nk67v8o02
at
sneakemail.com
I''ve been watching the flame war about licenses with some interest.
There are many motivations for those who participate in this sector, so
disagreements over licenses reflect those agendas.
I don''t have an agenda, at least not right now. I do plan on writing a
few programs.
These will be tools I need for firmware testing. They will be
relatively simple things like tools for breaking down data by its
structure for easy viewing, sending commands/macros over serial ports,
etc. Similar things exist, but they don''t do everything I need. These
will also be excellent learning opportunities for me, since I''m still
pretty shaky on Python.
How do I decide on a license? Are there any web sites that summarize
the pros and cons? I guess I don''t care too much about how other
people use it. These things won''t be comprehensive enough or have
broad enough appeal that somebody will slap a new coat of paint on them
and try to sell them. I guess I don''t care if somebody incorporates
them into something bigger. If somebody were to add features to them,
it would be nice to get the code and keep the derivative work as open
source, but I don''t think that matters all that much to me. If
somebody can add value and find a way of making money at it, I don''t
think I''d be too upset.
I will be doing the bulk of the coding on my own time, because I need
to be able to take these tools with me when I change employers.
However, I''m sure that in the course of using these tools, I will need
to spend time on the job debugging or tweaking them. I do not want my
current employer to have any claim on my code in any way. Usually if
you program on company time, that makes what you do a "work for hire".
I can''t contaminate my code like that. Does that mean the GPL is the
strongest defense in this situation?
I''m open to suggestions as to which licenses to consider. However,
please try to keep the conversation to the decision process or what
sounds like it is best for this purpose. Let''s keep the broader issue
of which license will bring about the fall of Western Civilization on
the other thread.
Ron Britton
(The gibberish on the next line really is my email address.)
nk67v8o02
at
sneakemail.com
推荐答案
IANAL，但我不相信GPL在这种情况下有所帮助。它在重新分配代码时放置了
的条件;它并没有强迫你
重新分配修改后的代码。您的雇主可以拒绝让您
随身携带代码，因为他们拥有部分版权。他们
以后因为GPL而无法卖掉，但这不是你的
问题。
我倾向于让客户同意来自外部的b
的代码可以根据它所带来的任何许可证退回。那个
让我们清楚地知道结果会回到社区，
这意味着你可以得到它们。
如果您处理此问题，最符合您的
描述的许可证是类似BSD的许可证，已被称为
copycenter许可证。他们对
的进一步使用没有任何限制。
< mike
-
Mike Meyer< mw*@mired.org>
独立的WWW / Perforce / FreeBSD / Unix顾问，电子邮件以获取更多信息。
IANAL, but I don''t believe the GPL helps in this situation. It places
conditions on redistributing the code; it doesn''t force you to
redistribute modifieed code. Your employers could refuse to let you
take the code with you because they own partial copyright on it. They
couldn''t sell it later because of the GPL on it, but that''s not your
issue here.
I tend to try to get clients to agree that code that comes in from
outside can go back out under whatever license it came in on. That
makes it clear up front that the results go back to the community,
which means you can get at them.
If you deal with this issue, the license that best meets your
description are the BSD-like license, which have been called
"copycenter" licenses. They place no restrictions whatsoever on the
the further use.
<mike
--
Mike Meyer <mw*@mired.org>http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
完全没有。你在雇主的时间写的代码可能是
属于雇主（你需要阅读你的合同和
相关的州法律或谈话在您所在地区的合格律师处获取完整的
详情）。仅仅因为你将代码添加到GPLed项目中并不是
意味着添加的代码将在GPL下发布。如果你的b
雇主有兴趣让你在离开他们之后不再使用它们，他们就根本不会发布代码。他们不会使用您的GPL代码将其变成专有项目，但是他们可以阻止您随身携带添加的代码。
/>
此外，如果与您的工作有很大关系，雇主可能仍然拥有您自己编写的软件的版权（因为它
似乎确实如此）。同样，你必须阅读你的合同和
相关的州法律，或者可以与律师联系以了解情况。我不是这样的律师，当然，这些都不是法律建议。
也就是说，假设您可以在一个开源的
许可证，鉴于你没有议程，BSD许可似乎是适当的b $ b。您可能还想阅读此许可证摘要：
这是草稿，但它包含有用的信息。另外，拉里罗森的书
-
Robert Kern
在地狱的地方，草地长得很高
梦想的坟墓是否能够死亡。
- - Richard Harter
Not at all. The code that you write on your employer''s time probably
belongs to the employer (you''ll need to read your contract and the
relevant state law or talk to a competent lawyer in your area for full
details). Just because you added that code to a GPLed project doesn''t
mean that the added code would be released under the GPL. If your
employer had an interest in keeping you from using it after you left
them, they simply wouldn''t release the code at all. They wouldn''t be
able to turn it into a proprietary project using your GPLed code, but
they could prevent you from taking the added code with you.
Also, the employer may still own the copyright on software that you
write on your own time if it substantially relates to your job (as it
seems it does). Again, you will have to read your contract and the
relevant state law or possibly talk to a lawyer to find out. I am not
such a lawyer, and, of course, none of this is legal advice.
That said, assuming that you can release the code under an open source
license and given your lack of an agenda, the BSD license seems
appropriate. You may also want to read this Licensing HOWTO:
http://www.catb.org/~esr/faqs/Licensing-HOWTO.html
It''s a draft, but it contains useful information. Also, Larry Rosen''s
book _Open Source Licensing_ is quite helpful (and free!).
http://rosenlaw.com/oslbook.htm
--
Robert Kern
ro*********@gmail.com
"In the fields of hell where the grass grows high
Are the graves of dreams allowed to die."
-- Richard Harter
如果他们拥有代码的权利，他们可以根据GPL或者他们选择的任何许可证出售它。此外，如果您使用GPL，您的雇主
将能够像其他任何人一样出售它。
-
Bj ?? rn Lindstr ?? m< bk ** @ stp.lingfil.uu.se>
计算语言学学生，瑞典乌普萨拉大学
If they have the rights to the code, they can sell it, under the GPL or
any license of their choosing. In addition, if you GPL it, your employer
will be able to sell it, just like anyone else.
--
Bj??rn Lindstr??m <bk**@stp.lingfil.uu.se>
Student of computational linguistics, Uppsala University, Sweden
这篇关于我应该使用哪种许可证？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！