Five Steps to Further Success with Subversion
- Beware a Price of Zero DollarsIt Can Cost You Plenty
- Getting Started with a Repository and Working Copy
- 1. Store Any Kind of File
- 2. Multiuser Subversion Folder Setup
- 3. Getting Out of Trouble
- 4. Store Only What Cant be Built
- 5. Scriptability Is a High Priority
- Conclusion
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
It’s important to remember that open source software can be costly to your organization. There’s simply no such thing as free technology. This is beginning to be more generally appreciated as companies start to deploy Linux in mission-critical applications.
Beware a Price of Zero Dollars—It Can Cost You Plenty
The lack of big license fees keeps the CFO happy, but the problem is, of course, support when things go wrong. Who owns what and who should provide the so-called end-to-end support? We’re all happy when things are working, but what happens when a server crashes and nobody in your organization knows why? Fortunately, some of the big vendors (for example, Oracle) are now starting to grasp this particular nettle and provide enterprise-grade support for software written by themselves and others. It isn’t cheap, but it is progress, and it will most likely cement the position of open source in the wider industry.
Subversion is a very trendy open source product and it is no exception to the mistaken notion that open source products are free. Even reading the manual takes time and therefore ultimately costs money. The best way to minimize the cost of an open source product is to know both why you’re using it and how to use it. In this article, I show you five important steps to take with Subversion to get the most out of the deployment and to reduce the cost of ownership. The goal is to keep you and your CFO happy!