选择开源托管服务/许可证
我正在与另外三名学生组成的小组开始一个游戏设计项目。我们想使用一些开源托管服务来进行版本控制、维基百科等。我已经研究过类似的线程（https://stackoverflow.com/questions/10490/best-open-source-project-hosting-site，https://stackoverflow.com/questions/29736/what-open-source-hosting-service-should-i-use ，http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities），但我仍然不确定这最适合我们的情况。这些线程似乎更关注大规模、长期的开源项目，而我的团队规模较小，合作时间相对较短。
以下是我的限制：
- 4-5 人组成的小组
- 每人每周花 10 个小时以上的时间在这个项目上，直到 2010 年 5 月
- 语言/框架：C# XNA
- IDE：Visual Studio 2008
- 项目将不超过 100 mb
功能会很好拥有：
- Wiki
- 里程碑跟踪
- 问题/错误跟踪
- 代码审查
- 文档托管（如游戏手册、设计规范等）
我认为 CodePlex 会很好，因为它支持 Visual Studio。我过去在一个小型项目中使用过 CodePlex，并获得了积极的体验。然而，Assembla 有一个很好的 UI，它的时间跟踪功能/将票证链接到 SVN 提交似乎真的很有帮助。 （时间跟踪特别吸引我，因为如果某些小组成员偷懒，它可能会在这里显示出来。）
Google 代码在上述主题中受到了许多人的赞扬，我小组中的每个人都有一个谷歌帐户。
另外，我不确定我们应该为我们的项目选择哪个许可证。
I am starting a game design project with a group of three other students. We would like to use some open source hosting service for version control, a wiki, etc. I have looked at threads like these (https://stackoverflow.com/questions/10490/best-open-source-project-hosting-site, https://stackoverflow.com/questions/29736/what-open-source-hosting-service-should-i-use, http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities) but am still not sure which is best for our situation. Those threads seem to focus more on large scale, long term open source projects, whereas my group will be small and working together for a relatively short time.
Here are my constraints:
- group of 4-5 people
- 10+ hours per week per person spent working on this project until May 2010
- Language/framework: C# XNA
- IDE: Visual Studio 2008
- project will be no bigger than 100 mb
Features that would be nice to have:
- Wiki
- Milestone tracking
- Issue/bug tracking
- Code reviews
- Document hosting (like the game manual, design spec, etc)
I'm thinking CodePlex would be nice because of its support for Visual Studio. I've had a positive experience with CodePlex in the past for a tiny project. However, Assembla has a nice UI, and its time tracking feature/linking tickets to SVN commits seems like it could be really helpful. (The time tracking in particular appeals to me, because if certain group members are slacking it could show through here.)
Google Code has been praised by many in the aforementioned threads, and everyone in my group has a Google account.
Also, I'm not sure which license we should pick for our project.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Codeplex 上已经托管了许多 XNA 相关项目。 Codeplex 的一大优点是您可以从大量源代码控制客户端中进行选择。它支持TFS客户端、SVN和mercurial。所以从灵活性的角度来看，这非常非常简单。
从许可证的角度来看......好吧，您并没有真正提供有关您的目标的足够信息。您是否想要像 GPL 这样的许可证，以确保您的代码不能在闭源项目 dodwnstream 中使用？你真的不在乎谁做什么吗？
就我个人而言，对于我在 codeplex 上托管的开源项目，我更喜欢 mozilla 公共许可证。它基本上表示代码是原样的，你可以用它做任何你想做的事情，打开或关闭。
Codeplex already has lots of XNA related projects being hosted on it. One of the great things about codeplex is that you can choose from a large number of source control clients. It supports the TFS client, SVN, and mercurial. So from a flexibility perspective, it's very very simple.
From a license perspective ... well, you didn't really give enough information about what your goals are. Do you want a license like GPL, which ensures that your code can't be used in a closed source project dodwnstream? Do you not really care who does what?
Personally, for the open source projects I've hosted on codeplex, I prefer the mozilla public license. It basically says the code is as is, and you can do whatever you want with it, open or closed.
我认为这与文档/组/等的轻松使用相结合。对于您不一定想要公共和组集成的事情，所有这些都具有整个团队很可能已经习惯使用的界面，这使得它成为一个合乎逻辑的选择，除非您认为其他服务可以更好地实现某些功能。在这里不必唱出谷歌的正常天堂——这似乎是一个非常务实、无大惊小怪的解决方案。
I think this coupled with easy usage of Docs/Groups/etc. and what not for things you dont nesscearily want public as well as group integration, all with interfaces that the entire team is most likely already used to working with, makes it a logical choice unless there are some features better fulfilled by another service in your opinion. In not nessecarily singing the normal paraises of google here - it just seems like a very pragmatic no fuss solution.