Figure out what you want people to be able to do with it. Do you want people to be able to use it for anything, including commercial stuff, or do you want it to be locked down as open source crazy GNU stuff? This list should be a good start. http://www.opensource.org/licenses/category
Next, pick a place to host the project. Google Code is a great one and I believe they require your project is a certain license. So that makes your decision for you.
Another thing you might want to consider is source control. If you like SVN, Git, or something else that can matter. GitHub is a good place for git projects and almost all of your hosts will have svn support.
正如 Jonathan 所说，请检查 OSI 以获取有关可能许可证的信息。从那里选择一个。与您可能编写的许可证不同，它们或多或少都会起作用（除非您知道自己在做什么）。有些站点（例如 Sourceforge）不允许使用未经过 OSI 批准的许可证的项目，因此您将通过 OSI 许可证获得更多选项。此外，很多人已经熟悉标准许可证，您无需向他们解释您的许可证。
There are numerous Open Source licenses, but the ones I'd recommend are either BSD-style or the GPL. You'll have to decide which you like. Should people be able to take what you've done and wrap them into proprietary software and sell it, without necessarily giving back their changes? Up to you. A BSD-type license might get you more users, and a GPL-type license might get you more development help.
If you're thinking of dual-licensing, with an open source and a commercial license, you almost certainly want to go GPL for the open source license, since BSD-style doesn't leave you with enough extra rights to sell.
You keep the copyright on everything you do that's not for hire, unless you explicitly give it away. If you start getting help from other people, you need to decide what to do. You can ask for the copyright to be transferred to you, which will keep your complete copyright control at the expense of discouraging outside developers. You can trademark your software, to keep the branding, and this is independent of who owns what copyright. I'd advise talking to a lawyer about that, as trademark law isn't as clean as copyright law, and can vary from state to state. If you live in the US, you can probably get a lawyer referral from your local bar association, and it shouldn't cost much for an initial consultation.
As Jonathan said, check the OSI for information on possible licenses. Pick one from there. They'll all work, more or less, unlike a license you might write up (unless you know what you're doing). Some sites, like Sourceforge, don't allow projects that are not under an OSI-approved license, so you'll get more options with an OSI license. Moreover, lots of people are already familiar with the standard licenses, and you won't have to explain your license to them.
如果你想设置你的项目，那么只需看看 GNU Hello，我认为是一个很好的模板，可以开始设置开源项目并重新分级许可证，这取决于您想要从项目中获得什么，正如其他人已经解释的那样。
If you want to setup your project then just have a look at GNU Hello, which I think is a good template to start setting up an open source project and regrading license it depends what you want from projects as explained by others already.
TL;DR Legal allows you to look up open source software licenses and get a summary, in plain English, of what you Can, Can't and Must do with the software. It also allows you to see the affects of combining two licenses, although that option is misleadingly called "Compare Licenses."
发布评论
评论（6）
弄清楚你希望人们能够用它做什么。
你是否希望人们能够将它用于任何用途，包括商业用途，还是希望它被锁定为开源疯狂的 GNU 东西？
这份清单应该是一个好的开始。
http://www.opensource.org/licenses/category
接下来，选择托管位置该项目。 Google Code 是一个很棒的代码，我相信他们要求您的项目具有一定的许可证。所以这会为你做出决定。
您可能需要考虑的另一件事是源代码控制。如果您喜欢 SVN、Git 或其他可能很重要的东西。 GitHub 是 git 项目的好地方，几乎所有主机都会有 svn 支持。
Figure out what you want people to be able to do with it.
Do you want people to be able to use it for anything, including commercial stuff, or do you want it to be locked down as open source crazy GNU stuff?
This list should be a good start.
http://www.opensource.org/licenses/category
Next, pick a place to host the project. Google Code is a great one and I believe they require your project is a certain license. So that makes your decision for you.
Another thing you might want to consider is source control. If you like SVN, Git, or something else that can matter. GitHub is a good place for git projects and almost all of your hosts will have svn support.
有许多开源许可证，但我推荐的是 BSD 风格或 GPL。你必须决定你喜欢哪一个。人们是否应该能够将您所做的事情包装成专有软件并出售，而不必归还他们的更改？由你决定。 BSD 类型许可证可能会为您带来更多用户，而 GPL 类型许可证可能会为您带来更多开发帮助。
如果您正在考虑双重许可，即具有开源和商业许可证，那么您几乎肯定会希望采用 GPL 来获得开源许可证，因为 BSD 风格不会给您留下足够的额外权利来出售。
您保留所有非雇佣行为的版权，除非您明确放弃。如果您开始从其他人那里获得帮助，您需要决定该怎么做。您可以要求将版权转让给您，这将保持您对版权的完全控制，但代价是阻止外部开发人员。您可以为您的软件注册商标，以保留品牌，这与谁拥有什么版权无关。我建议与律师讨论此事，因为商标法不像版权法那么明确，而且每个州的情况都有所不同。如果您居住在美国，您可能可以从当地律师协会获得律师推荐，并且初次咨询的费用不会很高。
正如 Jonathan 所说，请检查 OSI 以获取有关可能许可证的信息。从那里选择一个。与您可能编写的许可证不同，它们或多或少都会起作用（除非您知道自己在做什么）。有些站点（例如 Sourceforge）不允许使用未经过 OSI 批准的许可证的项目，因此您将通过 OSI 许可证获得更多选项。此外，很多人已经熟悉标准许可证，您无需向他们解释您的许可证。
There are numerous Open Source licenses, but the ones I'd recommend are either BSD-style or the GPL. You'll have to decide which you like. Should people be able to take what you've done and wrap them into proprietary software and sell it, without necessarily giving back their changes? Up to you. A BSD-type license might get you more users, and a GPL-type license might get you more development help.
If you're thinking of dual-licensing, with an open source and a commercial license, you almost certainly want to go GPL for the open source license, since BSD-style doesn't leave you with enough extra rights to sell.
You keep the copyright on everything you do that's not for hire, unless you explicitly give it away. If you start getting help from other people, you need to decide what to do. You can ask for the copyright to be transferred to you, which will keep your complete copyright control at the expense of discouraging outside developers. You can trademark your software, to keep the branding, and this is independent of who owns what copyright. I'd advise talking to a lawyer about that, as trademark law isn't as clean as copyright law, and can vary from state to state. If you live in the US, you can probably get a lawyer referral from your local bar association, and it shouldn't cost much for an initial consultation.
As Jonathan said, check the OSI for information on possible licenses. Pick one from there. They'll all work, more or less, unlike a license you might write up (unless you know what you're doing). Some sites, like Sourceforge, don't allow projects that are not under an OSI-approved license, so you'll get more options with an OSI license. Moreover, lots of people are already familiar with the standard licenses, and you won't have to explain your license to them.
您可以使用任何主要的开源许可证 - 这将取决于您想要从项目中获得什么。
您可能不会使用 LGPL，除非您正在编写的是一个库。
因此，开源计划提供有关可能的开源许可证的信息。不要尝试发明自己的。
You could use any of the main Open Source licences - it is going to depend on what you want from the project.
You probably wouldn't use the LGPL unless what you're writing is a library.
So the Open Source Initiative for information abuot possible open source licences. Do not try to invent your own.
如果您想保护软件，您可以使用
之一，但在许多情况下，更宽松的许可证会吸引更多用户。
是相当宽容的。
如果您想进行双重许可，请考虑使用 GPL 和商业许可。
在选择许可证之前，您必须回答自己：
从这里选择一个已经建立的许可证：http://www.opensource.org/licenses/category
If you want be protective about the software you could for example one of
But in many cases a more permissive license attracts more users.
are quite permissive.
If you want to do dual licensing then consider using GPL and a commercial license.
Before you pick a license and you have to answer yourself :
Pick an already established license from here : http://www.opensource.org/licenses/category
如果你想设置你的项目，那么只需看看 GNU Hello，我认为是一个很好的模板，可以开始设置开源项目并重新分级许可证，这取决于您想要从项目中获得什么，正如其他人已经解释的那样。
If you want to setup your project then just have a look at GNU Hello, which I think is a good template to start setting up an open source project and regrading license it depends what you want from projects as explained by others already.
TL;DR Legal 允许您查找开源软件许可证并获取摘要，用简单的英语说明您可以、不能和必须使用该软件做什么。它还允许您查看组合两个许可证的影响，尽管该选项被误导性地称为“比较许可证”。
TL;DR Legal allows you to look up open source software licenses and get a summary, in plain English, of what you Can, Can't and Must do with the software. It also allows you to see the affects of combining two licenses, although that option is misleadingly called "Compare Licenses."