对于短期项目来说，最好的协作工具是什么？
我，我们，发现自己与一些外部实体进行了短期合作（具体定义：但可以是 1 周、1 个月、1 年）。我称其为实体，因为它可以是一个人，也可以是一个大型的多元化公司。
问题是，到目前为止，所有通信都是为客户端完成的，这也意味着大量的工作。如果我们能提供一个协作工具：SVN、TortoiseSVN 或其他工具，那就更容易了。
该解决方案应该独立于操作系统，并且是一个可行的可交付成果。 我个人有点坚持使用某些 SVN 工具，但我可能需要 一些严重的个性化。
那么问题来了：您使用什么作为协作工具？哪一个最好（如果有的话）？ 假设异构环境。
I, we, find ourselves collaborating for a short time (to be defined: but it can be 1 week, 1 month, 1 year) with some external entities. I call it entities because it can be a single person but also a huge multi-multi company.
The problem is that all the communications have been, so far, always done for the client side, which also meant a lot of work. It would be easier if we can present a collaboration tool: SVN, TortoiseSVN, or something else.
The solution should be OS independent, and a working deliverable.
I personally kinda stick to some SVN tool, but I might need
some heavy personalization.
So the question: What do you use as a collaboration tool? Which one is the best (if any)?
Assuming an heterogeneous environment.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我将根据使用 Mercurial 支持之前的海报（但请记住 - 从我的观点来看，自己的 Subversion /over Apache/ 更易于管理）...
但必须提及 - 完全意义上的协作不仅仅是代码（因此 - SCM选择），更多的是 - 沟通、协调行动（“纯编码”之外）：如果你的任务是“事情必须完成”，仅 *VCS 是不够的。
PS - 对于我的随时项目，我更喜欢使用 Assembla，新的存储库现有空间或带有项目所需工具集的全新空间
I'll support previous posters in light of using Mercurial (but remember - own Subversion /over Apache/ is more manageable, from my POV)...
but have to mention - collaboration in full sense is not only code (thus - SCM of choice), it's more - communications, coordinated actions (outside the "pure coding"): if you mission is "Things must be done", just *VCS is insufficiently.
PS - for my any-time projects I prefer to use Assembla, new repo in existing space or totally new space with needed-for-project toolset
我假设“协作”工具指的是源代码管理/修订控制，因为您以 SVN 为例。
看来 CVS 和 SVN 等集中式版本控制系统的日子已经屈指可数了，而且运行它们的开销对于小团体或短期项目来说似乎尤其不合理。
就个人和职业而言，我已成功迁移到 Mercurial。它是用 Python 编写的（因此是跨平台的），并且具有比 Git，它的主要“竞争对手”。
如果您想模仿 CVS 和 SVN 的工作方式，那么设置一台服务器作为“权威”存储库是相当容易的。您还可以以完全分布式的方式工作，在客户端之间推送变更集。
要尝试一下，请在您的平台上安装并尝试：
这应该会让您了解工作流程以及您对它的喜欢程度。 Internet 上有大量教程可帮助您继续在实际项目中使用。
I assume by "collaboration" tool you mean source code management/revision control, since you are bringing up SVN as an example.
It would appear that the days of centralized revision control systems such as CVS and SVN are numbered, and the overhead of running them seems especially unjustified for a small group or short term project.
Personally and professionally I have migrated with great success to Mercurial. It's written in Python (and thus cross-platform) and has a user experience that is much superior (IMHO) to Git, its chief "competitor."
It's fairly easy to setup one server to act as an "authoritative" repository if you would like to mimic how CVS and SVN work. You can also work in a completely distributed manner, with changesets pushed between clients.
To give it a try, install on your platform and try:
That should give you an idea of the workflow and how much you like it. Tutorials abound on the Internet to help you move on with use in an actual project.
任何版本控制系统都会为您提供“协作工具”。这就是版本控制系统的主要作用：为开发人员提供一种结构化的协作方式。
我自己更喜欢 Mercurial，因为它轻量、快速且分布式。所有平台都有（图形）客户端：TortoiseHg（Windows、Linux、Mac）、MacHg 和 SourceTree （苹果）。
Any version control system will provide you with a "collaboration tool". That is the main role of a version control system: to provide a structured way for developers to work together.
I prefer Mercurial myself since it's light-weight, fast, and distributed. There are (graphical) clients for all platforms: TortoiseHg (Windows, Linux, Mac), MacHg and SourceTree (Mac).