I have very good experience with Google Code. It is fast, has no technical issues and the online interface is very clean and easy to use (unlike SourceForge).
I recommend either GPL or AGPL license.
AGPL is Affero GPL. It is pretty much the same as GPL, except anyone who publicly uses modified version has to provide its source code. For example if some company made extensive modifications to the code only for its own website/project, it would not be forced to release the changed source code if you used only GPL. But under AGPL, the company would have to release code even though it didn't distribute the application, but used it on its own server only - contributing to the public code base. This could deter some potential users from corporate sector though, so you have to weigh its advantages and disadvantages!
EDIT 2: Reacting on comment by David Dorward on the question.
There are two possible reasons why you would want to choose open license.
1) Political. You want to go open, because open is the morally right way to go. You should choose AGPL or even MIT License.
2) Practical. You want attention and people using your project. Open source projects gather attention much more easily that similar closed source (or even commercial) projects. If your project is looking promising, you may get people who will actively contribute into code base - for free. Also, distributing free PHP closed source application is somewhat complicated (though not entirely impossible). GPL is the way to go.
MIT licensing means the developers can take your code and do pretty much what they want with it, with no obligations to give credit to you for the code they reuse. So you may want a stricter license than that. GNU GPL usually works well.
As for the hosting platform, I would recommend GitHub. From what I've seen, it has the biggest potential to get developers to contribute, thanks to its simple tools for forking a project and submitting changes back to the source.
发布评论
评论（2）
我对 Google 代码有非常好的经验。它速度快，没有技术问题，并且在线界面非常干净且易于使用（与 SourceForge 不同）。
我推荐 GPL 或 AGPL 许可证。
AGPL 是 Affero GPL。它与 GPL 几乎相同，只是任何公开使用修改版本的人都必须提供其源代码。例如，如果某个公司仅针对自己的网站/项目对代码进行了大量修改，那么如果您仅使用 GPL，则不会被迫发布更改后的源代码。但在 AGPL 下，即使该公司没有分发该应用程序，但仅在自己的服务器上使用它，也必须发布代码 - 为公共代码库做出贡献。但这可能会阻止一些企业部门的潜在用户，因此您必须权衡其优点和缺点！
编辑：仅供参考，有使用 AGPL 的项目列表： http://en.wikipedia.org/wiki /List_of_AGPL_web_applications
编辑2：对 David Dorward 对这个问题的评论做出反应。
您想要选择开放许可证有两个可能的原因。
1) 政治。你想要开放，因为开放是道德上正确的道路。您应该选择 AGPL 甚至 MIT 许可证。
2）实用。您需要关注和人们使用您的项目。开源项目比类似的闭源（甚至商业）项目更容易吸引注意力。如果您的项目看起来很有前途，您可能会免费获得积极为代码库做出贡献的人员。此外，分发免费的 PHP 闭源应用程序有些复杂（尽管并非完全不可能）。 GPL 是一条出路。
编辑3：我推荐这本免费书：生产开源软件
I have very good experience with Google Code. It is fast, has no technical issues and the online interface is very clean and easy to use (unlike SourceForge).
I recommend either GPL or AGPL license.
AGPL is Affero GPL. It is pretty much the same as GPL, except anyone who publicly uses modified version has to provide its source code. For example if some company made extensive modifications to the code only for its own website/project, it would not be forced to release the changed source code if you used only GPL. But under AGPL, the company would have to release code even though it didn't distribute the application, but used it on its own server only - contributing to the public code base. This could deter some potential users from corporate sector though, so you have to weigh its advantages and disadvantages!
EDIT: Just for inspiration, there is list of projects using AGPL: http://en.wikipedia.org/wiki/List_of_AGPL_web_applications
EDIT 2: Reacting on comment by David Dorward on the question.
There are two possible reasons why you would want to choose open license.
1) Political. You want to go open, because open is the morally right way to go. You should choose AGPL or even MIT License.
2) Practical. You want attention and people using your project. Open source projects gather attention much more easily that similar closed source (or even commercial) projects. If your project is looking promising, you may get people who will actively contribute into code base - for free. Also, distributing free PHP closed source application is somewhat complicated (though not entirely impossible). GPL is the way to go.
EDIT 3: I recommend this free book: Producing Open Source Software
麻省理工学院的许可意味着开发人员可以使用您的代码并用它做几乎他们想做的事情，而没有义务为他们重用的代码归功于您。因此，您可能需要比这更严格的许可证。 GNU GPL 通常运行良好。
至于托管平台，我推荐GitHub。据我所知，它具有让开发人员做出贡献的最大潜力，这要归功于它用于分叉项目并将更改提交回源的简单工具。
MIT licensing means the developers can take your code and do pretty much what they want with it, with no obligations to give credit to you for the code they reuse. So you may want a stricter license than that. GNU GPL usually works well.
As for the hosting platform, I would recommend GitHub. From what I've seen, it has the biggest potential to get developers to contribute, thanks to its simple tools for forking a project and submitting changes back to the source.