This question is underspecified. Many packages exist for each category that you list, all designed to support collaboration across people distributed globally over different time zones.
So I can make a recommendation, based on open-source tools that have worked for me in the past. You may have specific needs that require more specific solutions, but you didn't mention them. Also, for productivity, it is useful if people can continue to use tools they are familiar with, and you didn't explain what tools your people already know.
In any case, here is my recommendation:
use Subversion for source control
use Roundup as the bug tracker
use make for the build management, use Buildbot for automated, distributed builds
Bug tracker: BugTracker.NET (open-source). But if you can, i would recommend Trac.
I am very satisfied with Assembla - they host SVN server and Trac for your projects for very reasonable prices (or for free if the oproject is public).
As source control: why not a distributed system, like git (if you are not using Windows), Mercurial or Bazaar? For bug tracking, I would go on Trac - it has also an integrated Wiki, that is always useful for project documentation. As for build management, you could go on cruise control, or ant - I am not really expert on this side.
However, there is something you should really take into consideration: the main issue for distributed teams is not the toolset, is communication. This is even more important in an "agile" setup, as suggested by your tag.
The best mitigation I have ever seen for this issue is videoconferencing. It is very effective for enhancing communication bandwidth in distributed teams, and with GTalk and Skype is now really inexpensive.
When you say "open source" do you just mean free software, or do you mean "I need/prefer to be able to see the source"?
Note that your decision will be influenced by the nature of your project. There are many free development/project hosting sites that require that your project must be an open source project and free/open to the public.
The other answers given to your question are solid, here is what I currently use or have used in the past:
A great continuous build tool JetBrains TeamCity. (http://www.jetbrains.com/teamcity/) The tool has out of the box support for many build tools as well as for building Visual Studio solutions out of the box. It is free for teams of 20 or less developers. It also has loads of functionality out of the box, and can be up and running for you in minutes - a remarkably low learning curve without cutting back on features.
A useful SVN repository which is free for two developers, and will save you the time of setting up and administering your own SVN repository is Unfuddle. (http://www.unfuddle.com) Unfuddle also has extra paid-for features and basic task tracking.
Another paid source repository is ProjectLocker (http://www.projectlocker.com) which has low priced SVN repositories and Trac integration for task management.
A useful task tracking tool is Remember The Milk (http://www.rememberthemilk.com) - it does not work on "tickets" like Trac, it is not only for tracking projects, but it does allow you to email each other tasks, and to have shared task lists. I also point them out because the product itself is developed by a distributed development team and you might want to try mail them for advice. :-)
It helps as an asynchronous communication media between ans inside the teams. People can share their tips (eg how do I compile this, how to activate traces ... ). It can be used to gather design decisions or changes... People can ask questions to the whole team without clobbering other mailboxes. It can also be used to grow the documentation.
There is a gazillion of wiki's, pick one depending on what you plan to do with it.
I think you'll need a few more things to help out with this project than what you've asked.
First, I'll give my recommendations for your list:
Source control: git or svn, if yu use either of these, you'll need a way to let your developers know who checked in what and when, Trac is good for this for svn
Bug tracking: Trac (not Bugzilla), Mantis, FogBuz
Build Management: CruiseControl is great for continuous integration; if you need build scripts try Ant or Maven
Other things you will probably need:
Collaboration tool: Trac has a wiki or pick a wiki of your choice
Chat tools: Even though they are across timezones, instant communication will be needed. IRC, Jabber, Skype, which is great for video or audio calls over the internet.
Project management: you'll need a way to setup your releases (sprints if using Scrum) and your backlog. My favorite tool for this is Acunote: (http://www.acunote.com). There are some other out there but they are more expensive and you get all of the features that you probable don't need.
是的，我坚信在分布式团队中工具很重要。 如果你们不在本地一起工作，沟通就已经很困难了。 诸如 Agilo for Scrum 等基于 trac 为您提供维基、规划板（在线白板），并以这种方式支持您改善与同事的沟通。
Yes I strongly believe that in distributed teams a tool is important. Communication is hard enough if you are not working locally together. A tool like e.g Agilo for Scrum that is based on trac offers you with a wiki, a planning board (online whiteboard) and supports you in this way to improve the communication with your colleagues.
发布评论
评论（9）
对于前两个：
For the first two:
这个问题没有具体说明。 您列出的每个类别都存在许多软件包，所有这些软件包都旨在支持分布在全球不同时区的人们之间的协作。
因此，我可以根据过去对我有用的开源工具提出建议。 您可能有需要更具体解决方案的特定需求，但您没有提及。 此外，对于生产力而言，如果人们可以继续使用他们熟悉的工具，并且您没有解释您的人员已经知道哪些工具，这将很有用。
无论如何，我的建议是：
This question is underspecified. Many packages exist for each category that you list, all designed to support collaboration across people distributed globally over different time zones.
So I can make a recommendation, based on open-source tools that have worked for me in the past. You may have specific needs that require more specific solutions, but you didn't mention them. Also, for productivity, it is useful if people can continue to use tools they are familiar with, and you didn't explain what tools your people already know.
In any case, here is my recommendation:
对于 .NET 环境：
我对 Assembla 非常满意 - 他们托管 SVN 服务器和 Trac 您的项目，价格非常合理（如果项目是公开的，则免费）。
For .NET environment:
I am very satisfied with Assembla - they host SVN server and Trac for your projects for very reasonable prices (or for free if the oproject is public).
考虑使用 Fogbugz 进行错误跟踪。 这很有帮助。
Consider Fogbugz for bug tracking. It's helpful.
作为源代码控制：为什么不采用分布式系统，例如 git（如果您不使用 Windows）、Mercurial 或 Bazaar？
对于错误跟踪，我会继续使用 Trac - 它还有一个集成的 Wiki，对于项目文档始终很有用。
至于构建管理，你可以继续巡航控制，或者蚂蚁 - 我在这方面并不是真正的专家。
然而，有一些事情你应该真正考虑到：分布式团队的主要问题不是工具集，而是沟通。
正如您的标签所建议的，这在“敏捷”设置中更为重要。
我见过的解决此问题的最佳方法是视频会议。 它对于增强分布式团队中的通信带宽非常有效，并且 GTalk 和 Skype 现在非常便宜。
As source control: why not a distributed system, like git (if you are not using Windows), Mercurial or Bazaar?
For bug tracking, I would go on Trac - it has also an integrated Wiki, that is always useful for project documentation.
As for build management, you could go on cruise control, or ant - I am not really expert on this side.
However, there is something you should really take into consideration: the main issue for distributed teams is not the toolset, is communication.
This is even more important in an "agile" setup, as suggested by your tag.
The best mitigation I have ever seen for this issue is videoconferencing. It is very effective for enhancing communication bandwidth in distributed teams, and with GTalk and Skype is now really inexpensive.
当您说“开源”时，您只是指免费软件，还是指“我需要/更喜欢能够看到源代码”？
请注意，您的决定将受到项目性质的影响。 有许多免费的开发/项目托管网站要求您的项目必须是开源项目并且免费/向公众开放。
您还可以根据您用于开发项目的语言选择特定的托管平台。 例如，CodePlex (http://www.codeplex.com/) 是一个托管开源的网站基于 .Net 的项目，以及 Java.Net (http://community.java.net/projects/) 托管 Java 项目。
对您的问题给出的其他答案是可靠的，这是我当前使用或过去使用过的：
一个很棒的连续构建工具JetBrains TeamCity。 (http://www.jetbrains.com/teamcity/) 该工具对许多构建工具以及构建 Visual Studio 解决方案提供开箱即用的支持。 对于 20 名或更少开发人员的团队来说，它是免费的。 它还具有大量开箱即用的功能，并且可以在几分钟内为您启动并运行 - 学习曲线非常低，而无需削减功能。
Unfuddle 是一个有用的 SVN 存储库，它对两名开发人员免费，可以节省您设置和管理自己的 SVN 存储库的时间。 (http://www.unfuddle.com) Unfuddle 还具有额外的付费功能和基本任务跟踪。
另一个付费源存储库是 ProjectLocker (http://www.projectlocker.com)，它具有低价的 SVN 存储库和用于任务管理的 Trac 集成。
一个有用的任务跟踪工具是 Remember The Milk (http://www.rememberthemilk.com) - 它不像 Trac 这样的“票据”工作，它不仅用于跟踪项目，而且允许您通过电子邮件互相发送任务，并共享任务列表。 我还指出了它们，因为产品本身是由分布式开发团队开发的，您可能想尝试向他们发送邮件以寻求建议。 :-)
祝您的团队一切顺利！
When you say "open source" do you just mean free software, or do you mean "I need/prefer to be able to see the source"?
Note that your decision will be influenced by the nature of your project. There are many free development/project hosting sites that require that your project must be an open source project and free/open to the public.
You may also choose to go with a particular hosting platform based on the language you are using to develop the project. For example, CodePlex (http://www.codeplex.com/) is a site that hosts open source .Net based projects, and Java.Net (http://community.java.net/projects/) hosts Java projects.
The other answers given to your question are solid, here is what I currently use or have used in the past:
A great continuous build tool JetBrains TeamCity. (http://www.jetbrains.com/teamcity/) The tool has out of the box support for many build tools as well as for building Visual Studio solutions out of the box. It is free for teams of 20 or less developers. It also has loads of functionality out of the box, and can be up and running for you in minutes - a remarkably low learning curve without cutting back on features.
A useful SVN repository which is free for two developers, and will save you the time of setting up and administering your own SVN repository is Unfuddle. (http://www.unfuddle.com) Unfuddle also has extra paid-for features and basic task tracking.
Another paid source repository is ProjectLocker (http://www.projectlocker.com) which has low priced SVN repositories and Trac integration for task management.
A useful task tracking tool is Remember The Milk (http://www.rememberthemilk.com) - it does not work on "tickets" like Trac, it is not only for tracking projects, but it does allow you to email each other tasks, and to have shared task lists. I also point them out because the product itself is developed by a distributed development team and you might want to try mail them for advice. :-)
All the best to your team!
wiki 是必须的。
它有助于作为团队内部人员之间的异步通信媒体。 人们可以分享他们的技巧（例如，我如何编译它，如何激活跟踪......）。 它可用于收集设计决策或更改......
人们可以向整个团队提问，而无需破坏其他邮箱。
它还可以用于扩展文档。
有无数的 wiki，根据您打算用它做什么来选择一个。
A wiki is a must.
It helps as an asynchronous communication media between ans inside the teams. People can share their tips (eg how do I compile this, how to activate traces ... ). It can be used to gather design decisions or changes...
People can ask questions to the whole team without clobbering other mailboxes.
It can also be used to grow the documentation.
There is a gazillion of wiki's, pick one depending on what you plan to do with it.
我认为您需要比您所要求的更多的东西来帮助完成这个项目。
首先，我将为您的列表提供我的建议：
您可能需要的其他东西：
我希望这有帮助。
I think you'll need a few more things to help out with this project than what you've asked.
First, I'll give my recommendations for your list:
Other things you will probably need:
I hope this helps.
是的，我坚信在分布式团队中工具很重要。 如果你们不在本地一起工作，沟通就已经很困难了。 诸如 Agilo for Scrum 等基于 trac 为您提供维基、规划板（在线白板），并以这种方式支持您改善与同事的沟通。
Yes I strongly believe that in distributed teams a tool is important. Communication is hard enough if you are not working locally together. A tool like e.g Agilo for Scrum that is based on trac offers you with a wiki, a planning board (online whiteboard) and supports you in this way to improve the communication with your colleagues.