In terms of technology, I would definitely go for a wiki (and Twiki is certainly not a bad choice). If it's installed on your company's intranet then there is no issue in terms of security.
One thing to keep in mind about a wiki is that it requires some work to keep it maintained; it's easy (and sometimes tempting) for everyone in the team to constantly just add pages without taking any linking of pages or structure into account. The moral here: a wiki is a very helpful tool for helping in communication, but it doesn't come for free.
However, depending on the kinds of communication/discussion that you're talking about: definitely watch out that online communication isn't replacing face-to-face communication. Depending on the interpersonal skills of the members of the team, it can some times be too easy for some people to shift to e-mail/wiki/forum use instead of verbal communication. Even having daily stand-up meetings (a la SCRUM) can be very useful in ensuring that everyone knows what is going on in the team instead of relying on electronic communication.
It has a forum and wiki per project, as you seem to need, and a lot more features very usefull when dealing with a project that requires several members to participate. And its opensource!
The only "issue" is that it was written using Ruby on Rails.
I would say Twiki, its an open source enterprise wiki.
Needs sometime to get used to it, but once you are, you will find opening new pages and topics very easy and quick. One of the advantages IMO is its hosted on your own server
我们还使用维基来获取更永久的内容。有时，在聊天中开始的材料会迁移到 wiki。结构化 wiki 的优点在于，它可以更轻松地加入新的团队成员并维护团队规范等特定内容（如 Subversion 的 HACKING 文档）。
这样做的好处是，我们可以针对短暂的问题等进行快速、轻量级的聊天，但我们仍然可以通过 wiki 来保存重要的内容。
My own distributed team has experienced a similar problem, and we've solved it in the following way.
Day-to-day we run a continuous group chat (Campfire is an option). Announcements, questions, and answers can happen in chat, and it's recorded. You can search past transcripts as needed. This is simple and lightweight.
We also use a wiki for more permanent content. Sometimes material that starts in chat migrates to the wiki. The advantage of a structured wiki is that it makes it easier to onboard new team members and maintain specific content like team norms (like Subversion's HACKING doc).
The benefit is that we keep fast and lightweight chat for transient questions and so on, but we still have the wiki to hold content once it's deemed important.
发布评论
评论（4）
就技术而言，我肯定会选择 wiki（Twiki 当然不是一个糟糕的选择）。如果它安装在您公司的内联网上，那么在安全方面就不存在问题。
关于 wiki 需要记住的一件事是它需要一些工作来维护它；对于团队中的每个人来说，不断添加页面而不考虑任何页面链接或结构是很容易的（有时很诱人）。这里的寓意是：维基是一个非常有用的工具，有助于沟通，但它不是免费的。
但是，根据您所讨论的沟通/讨论类型：一定要注意在线沟通不会取代面对面的沟通。根据团队成员的人际交往能力，有时对于某些人来说，转向使用电子邮件/维基/论坛而不是口头交流可能太容易了。即使每天举行站立会议（la SCRUM）也非常有用，可以确保每个人都知道团队中正在发生的事情，而不是依赖电子通信。
In terms of technology, I would definitely go for a wiki (and Twiki is certainly not a bad choice). If it's installed on your company's intranet then there is no issue in terms of security.
One thing to keep in mind about a wiki is that it requires some work to keep it maintained; it's easy (and sometimes tempting) for everyone in the team to constantly just add pages without taking any linking of pages or structure into account. The moral here: a wiki is a very helpful tool for helping in communication, but it doesn't come for free.
However, depending on the kinds of communication/discussion that you're talking about: definitely watch out that online communication isn't replacing face-to-face communication. Depending on the interpersonal skills of the members of the team, it can some times be too easy for some people to shift to e-mail/wiki/forum use instead of verbal communication. Even having daily stand-up meetings (a la SCRUM) can be very useful in ensuring that everyone knows what is going on in the team instead of relying on electronic communication.
我建议 redmine
它每个项目都有一个论坛和维基，正如你似乎需要的那样，还有很多在处理需要多个成员参与的项目时，更多功能非常有用。而且它是开源的！
唯一的“问题”是它是使用 Ruby on Rails 编写的。
I'd suggest redmine
It has a forum and wiki per project, as you seem to need, and a lot more features very usefull when dealing with a project that requires several members to participate. And its opensource!
The only "issue" is that it was written using Ruby on Rails.
我想说的是 Twiki，它是一个开源企业 wiki。
需要一些时间来适应它，但一旦习惯了，您会发现打开新页面和主题非常容易和快速。
IMO 的优势之一是它托管在您自己的服务器上
TWiki® - 开源企业 Wiki 和 Web 2.0 应用程序平台
I would say Twiki, its an open source enterprise wiki.
Needs sometime to get used to it, but once you are, you will find opening new pages and topics very easy and quick.
One of the advantages IMO is its hosted on your own server
TWiki® - the Open Source Enterprise Wiki and Web 2.0 Application Platform
我自己的分布式团队也遇到了类似的问题，我们通过以下方式解决了它。
我们每天都会进行连续的群聊（Campfire 是一个选项）。公告、问题和答案可以在聊天中进行，并且会被记录下来。您可以根据需要搜索过去的成绩单。这是简单且轻量级的。
我们还使用维基来获取更永久的内容。有时，在聊天中开始的材料会迁移到 wiki。结构化 wiki 的优点在于，它可以更轻松地加入新的团队成员并维护团队规范等特定内容（如 Subversion 的 HACKING 文档）。
这样做的好处是，我们可以针对短暂的问题等进行快速、轻量级的聊天，但我们仍然可以通过 wiki 来保存重要的内容。
My own distributed team has experienced a similar problem, and we've solved it in the following way.
Day-to-day we run a continuous group chat (Campfire is an option). Announcements, questions, and answers can happen in chat, and it's recorded. You can search past transcripts as needed. This is simple and lightweight.
We also use a wiki for more permanent content. Sometimes material that starts in chat migrates to the wiki. The advantage of a structured wiki is that it makes it easier to onboard new team members and maintain specific content like team norms (like Subversion's HACKING doc).
The benefit is that we keep fast and lightweight chat for transient questions and so on, but we still have the wiki to hold content once it's deemed important.