Apache Subversion vs. Microsoft SharePoint

Subversion solves our software versioning problem by providing tools for conflict resolution when doing collaborative work on the same files and projects. We use it with TortoiseSVN and it works great for some of our projects with smaller teams. However, we have a need to make code reviews more and it is a little more difficult to do that in SVN, compared to Bitbucket and Git.

Incentivized

SharePoint Document Management excels as a central repository for storing, organising, and retrieving documents. It supports version control, metadata tagging, secure access, and integration with tools like Power Automate. At our organisation, it's used for managing contracts, policies, and supplier documents. SharePoint Workflow Automation integrates with Power Automate to streamline approvals, gather feedback, and automate recurring tasks. This reduces reliance on email chains and manual trackers.

Incentivized

• Track and control concurrent versions of the same files.
• Has good support from many different software, including visualization, DevOps toolchain.
• Well documented and understood by developers as it has been around for a long time.

Incentivized

• We track employees' performance sheets, which are accessible to the employee, his manager, and HR, and this helps with transparency.
• We maintain technical process documents and SOPs, which help us quickly provide relevant documents during audits.
• We maintain incident documents change request forms in SharePoint, which helps us in tracking the changes.

Incentivized

• Refactoring the layout of a respoitory--or a part of a repository--can be a bit painful, especially for users with workspaces associated with the affected part of the repository. Not sure what could be done to make that better, but it would be nice if something was possible.
• Folks coming from Git can have problems using Subversion. Again, not sure anything can (or should) be done to address that, but it is occasionally an issue.

Incentivized

• It still needs to jam some services together like Planner and lists so that teams can interact from a single place[.]
• Sites need to be more intuitive and rather building from scratch should come up with some suggestion[.]
• The tool tips for new users are not adequate[.]

Incentivized

While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.

We have too much invested at this point to do anything different and there are too many reasons as a company our size to keep it. We are heavily licensed out for Microsoft and have 12 years of SharePoint development baked into who we are. Extracting that as a tool at this point would be dumb and devastating. There are no like-kind competitors to it at an enterprise level that scale and integrate as well.

Incentivized

No usability issues reported. Individual teams also have allocated areas which replace legacy shared drives on local LANs. Access to Sharepoint resources is fully integrated with corporate Active Directory with additional two-factor authentication required for administrative users. Users have access to Microsoft Services Hub which allows you to create, manage, and track support requests while staying current on Microsoft technologies with access to select self-paced learning paths

Incentivized

Support for SharePoint is quite good. Microsoft provides good support. Microsoft offers

• Quick turnaround time for issues
• A range of support services
• Access to a network of resources
• Escalation of issues
• Ongoing development and commitment to produce enhancement

The majority of support is required for initial installation. Once complete and the system is operating we have had very few support issues.

Incentivized

The face to face training I received was on SharePoint Administration. It was rushed as there was a lot of information to cover and the application of the labs weren't that great either. I like to be able to relate what I am learning to what I am currently doing.

I like to learn at my own pace and online training allows for that. Additionally, you can skip through pieces of content that you already know or are already comfortable with. Microsoft actually offers great videos on their website for basic fundamental SharePoint Training. I have used these training videos in some of my own training sessions with end users.

Planning to the last detail would be advised. SharePoint is a very large application that takes a lot of finesse to get operational

After Microsoft Visual SourceSafe was discontinued, we chose Subversion and it was a great choice. We were able to migrate to Apache Subversion very quickly and easily and benefited immediately from its non-locking workflow (SourceSafe required users to "lock" the file when editing to prevent editing conflicts from other users, whereas Subversion allows multiple users to edit the same file simultaneously and then merge conflicts later.)

While we still use Apache Subversion for our legacy projects, we've migrated to Git and GitHub for our new projects as that is the new "cool kid" and it provides some benefits such as distributed and offline development. But Git is more complex than Apache Subversion and not as easy to learn.

Incentivized

The reasons for selecting MS SharePoint are: SharePoint provides ease of use and web design assistance and support SharePoint helps you schedule your content for publishing. enables users to share documents with external parties and offers a better internal structure of the content and better indexing and searching capabilities.

Incentivized

• It allowed us to deliver the right files to our customer without "clobbering" previous releases, making for a far more satisfied customer.
• It allowed our developers to work on two releases in parallel (plus an occasional third, for emergency fixes).
• With some simple hooks, it allowed us to set up a system where code was was automatically deployed to test servers as soon as developers committed it, making testing easier. This was made easier by virtue of being a ColdFusion project, which requires no compilation. However, that is possible for compiled code with a continuous integration system like Jenkins.

Incentivized

• We've recently implemented Microsoft SharePoint access via iPads for our Template teams out on job sites. They can easily upload CAD / Laser files into Microsoft SharePoint for our production team to review in real time. Serious ROI when we don't have to wait for our Template team to get back to the shop!
• We have multiple physical locations. Microsoft SharePoint allows users at each location to collaborate by working on documents simultaneously. Allowing us to solve multi-site problems & strategize on multi-site initiatives much faster!
• We can also share key information with external partners. As long as they have a registered MS account (not necessarily an O365 account) we can share our information with them in a variety of ways. This allows consistent & concise communication with our partners.

Incentivized