blocks|key|416186|text|Subversion+(SVN)对您来说是一个很好的选择。它是免费的，通过TortoiseSVN很好地集成到Windows中，并且被用户很好地接受。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|416187|我们将其用于源代码和文档管理。|416188|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Subversion (SVN) is an excellent option for you. It's free, integrates nicely into Windows with TortoiseSVN, and is well-tolerated by users.

We are using it for source code, as well as for document management.

blocks|key|416125|text|http://trac.edgewall.org/+-可能有点难安装，但如果与svn存储库结合使用，则非常好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|416126|entityMap|0|LINK|mutability|MUTABLE|url|http://trac.edgewall.org/^0|0|P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://trac.edgewall.org/" rel="nofollow noreferrer">http://trac.edgewall.org/</a> - might be a bit hard to install but otherwise is very good if coupled with svn repository

blocks|key|416044|text|Mantis是很好的问题跟踪工具。用于源代码控制的Subversion。两者都是免费的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|416045|至于文件，我不知道。听起来你使用网络共享会做得很好。|416046|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Mantis is good for issue tracking. Subversion for source control. Both are free.

For documents, I do not know. Sounds like you would do fine with a network share.

blocks|key|2731382|text|你可能想看看Trac。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2731383|entityMap|0|LINK|mutability|MUTABLE|url|http://trac.edgewall.org/^0|6|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You may want to look at <a href="http://trac.edgewall.org/" rel="nofollow noreferrer" title="Trac">Trac</a>.

blocks|key|2731490|text|我在一家类似规模的公司工作，当我来到这里的时候，我和你在同一个地方。我很容易就实现了SVN/Subversion+http://subversion.tigris.org/。如果您使用svn协议并使用svnserve+(可以设置为在您的服务器上自动启动的windows服务)，根据您想要阅读http://svnbook.red-bean.com/的多少，应该需要1.5-3个小时来设置，请参阅collabnet+http://www.collab.net/downloads/subversion/以获取Windows包下载|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2731491|使用Windows，您可以使用集成到windows+shell中的Tortoise+SVN。还有集成到Visual+Studio中的Ankh+SVN+(2.0)+http://ankhsvn.open.collab.net/的新版本。Ankh非常好(有挂起的更改窗口，有点类似于Subclipse的功能)，但它是一个新版本，并且有一些but+(我们经历了一些内存问题和缓慢)。我们目前使用Tortoise进行初始结帐或导入，使用Ankh处理其他所有事情，并且非常满意。|2731492|如果你有Mac用户，有很多选择。我们这里有一位mac用户，他使用的是http://www.versionsapp.com/版本，尽管听起来他们一旦退出测试版就会收费。|2731493|我会推荐SVN，因为它在那里得到了广泛的应用，而且我觉得这对于您将每天用于生产目的的开源项目很重要。简单地说，这里提到的所有东西(版本除外)都是免费的。|2731494|entityMap|0|LINK|mutability|MUTABLE|url|http://subversion.tigris.org/|1|http://svnbook.red-bean.com/|2|http://www.collab.net/downloads/subversion/|3|http://ankhsvn.open.collab.net/|4|http://www.versionsapp.com/^0|1L|T|0|41|S|1|5Q|17|2|0|29|V|3|0|Y|R|4|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]|$A|13|B|14|1|15]|$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]]|C|$]]|$1|F|3|G|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|H|3|I|5|6|7|1H|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]|V|$5|M|N|O|C|$P|W]]|X|$5|M|N|O|C|$P|Y]]]]

I work for a similar sized company, and when I got here I was in the same place as you. I implemented SVN/Subversion <a href="http://subversion.tigris.org/" rel="nofollow noreferrer">http://subversion.tigris.org/</a> quite easily. If you use the svn protocol and use svnserve (can be setup as a windows service that auto starts on your server) it should take you 1.5-3 hours to setup depending on how much you want to read <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">http://svnbook.red-bean.com/</a>, see collabnet <a href="http://www.collab.net/downloads/subversion/" rel="nofollow noreferrer">http://www.collab.net/downloads/subversion/</a> for the Windows package download

Using Windows, you can use Tortoise SVN which integrates into the windows shell. There is also a new release of Ankh SVN (2.0) <a href="http://ankhsvn.open.collab.net/" rel="nofollow noreferrer">http://ankhsvn.open.collab.net/</a> that integrates into Visual Studio. Ankh is very nice (has pending changes window, kind of similar to Subclipse like functionality) but it is a new release and is somewhat buggy (we have experienced some memory probs and slowness). We currently use both Tortoise for initial checkouts or imports and Ankh for everything else and are pretty happy.

If you have any Mac users, there are a lot of options out there. We have a mac user here who uses Versions <a href="http://www.versionsapp.com/" rel="nofollow noreferrer">http://www.versionsapp.com/</a>, though it sounds like they will charge for it once they get out of beta.

I would recommend SVN because it is widely used out there and I feel that is important with open source projects you are going to use daily for production purposes. Just to spell it out, everything (other than Versions) mentioned is free.

blocks|key|4197223|text|当然！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4197224|与大多数其他源代码控制系统相比，它的速度非常快。它可以远程工作。(在我的例子中，SSH隧道)|4197225|VS插件相当不错...我还没有试过那么多Eclipse版本。|4197226|如果您可以使用两个用户，每个用户有5个工作区，那么您可以免费使用它。(目前，我有)|4197227|如果那行不通，那就得花点钱...我想大概是800美元/用户。明年的某个时候我可能会付这笔钱。(当您在具有虚拟机的多台计算机上工作时，5个工作区是困难的)|4197228|尽管如此，我听说一个客户正在使用的比冰川更慢的ClearCase/ClearQuest系统大约是每个开发人员10K美元，所以对于源代码控制来说，昂贵是一个相对的概念。|4197229|不要在源码控制上省钱，伙计！在a$$中，缓慢的源代码控制是一个非常痛苦的问题。|4197230|避免使用类似SourceSafe的系统，这些系统只对文件进行版本控制...使用跟踪任务或变更集的系统。将所有内容作为一项任务放在一起是非常有用的。标签不是可接受的替代品。|4197231|此外，Perforce的日志特性使备份和恢复变得容易得多。|4197232|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

Perforce!

It's extremely fast compared to most other source control systems. It works great remotely. (SSH tunnels, in my case)

The VS plugins are quite decent... I haven't tried the Eclipse one that much yet.

If you can get by with two users with 5 workspaces each, then you can use it for free. (I do, currently)

If that won't work, then it does cost a bit... something like $800/user I believe. Sometime next year I'm probably paying that. (5 workspaces is tough when you work on several machines with VMs)

Still, I heard the slower-than-glacial ClearCase/ClearQuest system one client one mine is using was something like $10k per developer, so expensive where source control is concerned is a relative concept.

Don't skimp on the source control, man! Slow source control is a serious pain in the a$$.

Avoid SourceSafe-like systems that only version files... use systems that track tasks or change sets. It's very useful to see what all belongs together as a task. Tags are not an acceptable substitute.

Also, the journalling nature of Perforce makes backups and recovery a lot easier.

blocks|key|808707|text|使用Git进行源代码控制，使用Basecamp/Pivotal+Tracker/Unfuddled进行工作流程编码，使用Sharepoint/Google+Docs进行文档管理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|808708|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Use Git for source control, Basecamp/Pivotal Tracker/Unfuddled for coding workflow, and Sharepoint/Google Docs for document management.

blocks|key|4196987|text|如果您获得了MSDN开发人员许可证，则可以运行TFS工作组版。这使得源代码控制和文档管理都集中在一个包中，非常容易使用和管理。除了内部维基之外，这也是我的公司所做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4196988|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you get a MSDN developer license, you can run TFS workgroup edition. That has source control and document management rolled all up in one package that's pretty easy to use and manage. That, in addition to an internal wiki, is what my company does.

blocks|key|801887|text|使用Subversion。它是免费的，是绝大多数开源项目首选的源代码控制系统。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|801888|SVN使用浅层复制，因此当您在存储库中有大文件并进行分支时，无法完成完整文件复制……只是指向原件的指针。对于文本文件(代码)，只存储差异。|801889|使用TortoiseSVN进行windows资源管理器集成。|801890|TFS是一头猪，您需要打开visual+studio才能与源代码资源管理器交互。CAD工程师必须获得TFS的许可证才能做到这一点，这太愚蠢了。|801891|对于文档管理，只需使用Windows+Server+2003+(或2008)附带的Windows+Sharepoint+Services即可。|801892|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Use Subversion. It's free and is the preferred source control system for the vast majority of open source projects.

SVN uses shallow copies, so when you have large files in a repository and you branch, a full file copy isn't done... just a pointer to the original. As for text files (code) only diffs are stored.

Use TortoiseSVN for windows explorer integration.

TFS is a pig, and you'd need to open visual studio to interact with source explorer. Stupid for a CAD engineer to have to need a license to TFS for that.

For document management, just use Windows Sharepoint Services that comes with Windows Server 2003 (or 2008).

blocks|key|416223|text|我也在一家小公司工作，我们主要使用.NET语言进行开发。我们决定使用Visual+SourceSafe进行源代码控制，尽管它的名声有问题，因为它与Visual+Studio很好地集成在一起。VSS对我们来说工作得很好，我们没有遇到任何严重的问题。此外，我们还托管了一个SharePoint服务器，用于存储文档，如编码标准、故事板，甚至我们的SCRUM日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|416224|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also work for a small company and we mainly develop in .NET languages. We have decided to use Visual SourceSafe for source control, despite its questionable reputation, since it integrates nicely with Visual Studio. VSS works very well for us, and we have not experienced any serious problems with it. Also, we host a SharePoint server, which we use to store documents like coding standards, storyboards, and even our SCRUM log.

blocks|key|416241|text|我们使用HostingPlayground。每月6美元，我们可以获得多个Subversion存储库和一个Trac实例。没人能比得上。由于这是一项服务，因此可以立即使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|416242|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We use HostingPlayground. For $6 per month we get multiple Subversion repositories and an instance of Trac. Can't beat it. And since its a service its available immediately.

blocks|key|802059|text|似乎你的“管理”需求的解决方案至少需要以下类别的一个或一组工具：(很抱歉链接，没有足够的声誉在回复中放入合适的链接)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|802060|802061|源代码管理|unordered-list-item|802062|802063|一定要看看stackoverflow.com/questions/15024/tools-to-help-a-small-shop-score-higher-on-the-joel-test工具，它可以帮助小商店在stackoverflow.com/questions/84303/code-document-management-for-a-very-small-company/84363#84363+Kristopher提到的乔尔测试中获得更高的分数|802064|每一个都有各种免费/开源的解决方案，同样也有商业解决方案。|802065|源代码管理(SCM)|802066|一个重要的趋势(？)源代码管理正在从集中式的代码管理演变为分散式的“分布式”源代码管理，比如使用TFS(?)、cvs或git-scm.com.+code+/mercurial/wiki/或subversion.tigris.org+-scm.com/等工具。有些工具要么集成到continutation中|802067|上面提到的源代码管理工具都有很好的ms+windows集成工具，有些甚至有更紧密的Visual+Studio集成(例如Mario提到的TFS，ankhsvn.open.collab.net/+ANKH+svn+)。|802068|当您的编码涉及到与集中式源代码存储库断开连接的大部分时间时(例如，当您的存储库无法通过Internet访问时，在家中进行大量编码)，一个简单的概括将推荐git/mercurial。|802069|Wikipedia有一个en.wikipedia.org/wiki/+source+_+code+_+management，它很好地概述了与源代码管理相关的各种问题，以及各种选项的好处。|802070|如果您以前没有使用过scm，只需选择一两个适合您团队需求的工具并对其进行测试即可。当然，如果你知道你身边的人有特定的scm解决方案的经验，那么分享经验可能会有助于团队的学习曲线。|802071|我为您的场景选择:使用ankhsvn.open.collab.net和SVN进行Visual+Studio集成的Subversion。|802072|故障/错误票证|802073|没有一种可用的工具可以解决所有人的所有问题，每种工具都有自己的优点，而且大多数工具都需要开发团队在现有的操作方式上做出一些妥协。再说一次，维基百科是你的朋友，它提供了en.wikipedia.org/wiki/Bug_tracker综合摘要和主要工具的en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems比较。|802074|安装|802075|根据我的经验，基于php的工具是最容易安装和运行的，而perl工具涉及的更多(？)当然也有python+one，它很容易安装，但需要比我更好的头脑来配置。|802076|我为您的场景选择:+trac.edgewall.org/+Trac|802077|802078|跟踪是一个增强的维基和软件开发项目的问题跟踪系统。Trac使用最简单的方法来进行基于web的软件项目管理。我们的任务是帮助开发人员写出优秀的软件，同时保持中立。Trac应该尽可能少地强加在团队已建立的开发过程和策略上。|blockquote|802079|802080|它提供了一个到Subversion+(或其他版本控制系统)的接口，一个集成的Wiki和方便的报告工具。|802081|Trac允许在问题描述和提交消息中使用wiki标记，在bug、任务、变更集、文件和wiki页面之间创建链接和无缝引用。时间线按顺序显示所有当前和过去的项目事件，使得获取项目概述和跟踪进度变得非常容易。路线图显示了未来的道路，列出了即将到来的里程碑。|802082|802083|图形/文档管理|802084|如果您在Trac中使用Subversion，那么您的大部分文档管理都可以使用这些工具来解决。另外，另一个stackoverflow讨论主题:+Windows文档、sharepoint文档管理与screwturn+wiki，适用于以stackoverflow.com/questions/587481/developer-documentation-sharepoint-document-management-vs-screwturn-wiki为中心的环境，是一个很好的读物。|802085|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1Q|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1V|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1X|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|20|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|21|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|22|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|23|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|24|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|25|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|19|3|1A|5|1B|7|27|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|28|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|29|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|2A|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2C|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2D|8|@]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]]|1N|$]]

It seems the solution for your 'management' requirements will require at least a tool or set of tools in the following categories: (sorry about the links, not enough reputation to put proper ones in the reply)

<ul>
<li>Source Code Management</li>
<li>Trouble/Bug Ticketing</li>
<li>Document Management</li>
</ul>

Definitely take a look at stackoverflow.com/questions/15024/tools-to-help-a-small-shop-score-higher-on-the-joel-test Tools to help a small shop score higher on the joel test referenced by stackoverflow.com/questions/84303/code-document-management-for-a-very-small-company/84363#84363 Kristopher

Each have various free/open source solutions, and likewise there are commercial solutions.

<h2>Source Code Management (SCM)</h2>

A significant trend(?) of source code management is evolving from centralised code management with something like TFS(?), cvs or subversion.tigris.org svn), to decentralised 'distributed' source code management with tools such as www.selenic.com/mercurial/wiki/ or git-scm.com/. Some of the tools either integrate into continutation 

The above mentioned source code management tools all have nice ms windows integration tools, and some even have closer Visual Studio integration (e.g. TFS, ankhsvn.open.collab.net/ ANKH svn mentioned by Mario).

A simplistic generalistion would recommend git/mercurial when your coding involves a good portion of time away/off disconnected from your centralised source code repository (such as doing a lot of coding from home when your repository is not accessible through the Internet.)

Wikipedia has a en.wikipedia.org/wiki/Source_code_management nice overview of the various issues related to source code management, and the benefits of various options. 

If you haven't used scm before, just pick one or two of the tools that fits your groups requirements and test it. Of course, if you know someone near who has experience with a particular scm solution it may help with the team's learning curve to have that shared experience around.

My pick for your scenario: Subversion with ankhsvn.open.collab.net Ankh SVN for Visual Studio integration.

<h2>Trouble/Bug Ticketing</h2>

None of the tools available solve everything for everybody, each have their advantages and most require some compromise from a development teams existing modus operandi. Again, wikipedia is your friend with a en.wikipedia.org/wiki/Bug_tracker general summary and en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems comparison of major tools.

<h3>Installation</h3>

The php based tools are the easiest (in my experience) to get up and running, and the perl tools more involved(?) Of course there's python one that's real easy to install, but then requires a better mind than mine to configure.

My pick for your scenario: trac.edgewall.org/ Trac

<blockquote>
 Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.
 
 It provides an interface to Subversion (or other version control systems), an integrated Wiki and convenient reporting facilities.
 
 Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all current and past project events in order, making the acquisition of an overview of the project and tracking progress very easy. The roadmap shows the road ahead, listing the upcoming milestones.
</blockquote>

<h2>Drawings/Document Management</h2>

If you use Subversion with Trac then much of your document management may be solved with these tools. Otherwise another stackoverflow discussion topic: stackoverflow.com/questions/587481/developer-documentation-sharepoint-document-management-vs-screwturn-wiki Developer documentation sharepoint document management vs. screwturn wiki, for Windows centric environment, is a good read.

I work for a very small company (~5 employees, 2.5 coders). We have gotten away with no code or document management for several years, but it's starting to catch up with us as we grow a bit.

Any suggestions for a management system. Free is better, but cheap is acceptable. We just don't want to spend more time on installation/configuration than it is going to save us.

We use mostly VC++ 6, but we're branching into VC# 2008. Also, we need to keep track of mechanical drawings and circuit diagrams for several pieces of hardware, as well as user manuals for both hardware and software (but I don't really expect to find one tool that will do all of this, just hoping).

Code/Document Management for a very small company

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在一家非常小的公司工作(大约5名员工，2.5名程序员)。我们已经有几年没有代码或文档管理了，但随着我们的成长，它开始跟上我们的脚步。对管理系统的任何建议。免费更好，但便宜也是可以接受的。我们只是不想花更多的时间在安装/配置上，而不是花在节省我们的时间上。我们主要使用VC++ 6，但我们也在使用VC# 2008。此外，我们需要跟踪几个硬件的机械图纸和电路图，以及硬件和软件的用户手册(但我真的不希望

问面向超小型公司的代码/文档管理
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问面向超小型公司的代码/文档管理EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问面向超小型公司的代码/文档管理
EN