Backe, Martin G
2015-01-29 20:35:30 UTC
Having been a fan of Richard's work during my Tcl days, it wasn't much of a leap of faith when I chose Fossil for our SCM for a new internal project. I loved the fact that it was extremely easy to install and that it included a ticketing system, Wiki, and all the features one would want in a modern distributed SCM system. The built-in web server is brilliant. I wish all open source software was as easy to build, install, and use as Fossil is.
As stated in my lead-in, we've been using Fossil for about four years. I compile the server version that runs on our Linux host, and we use Windows binaries for the team members. Our team is small at two to four people, and at times are distributed across the country. We've been developing a mission critical Java application, and have used Fossil continually throughout the day for the last four years. The ticketing system was tailored to be used as our Scrum Task Board. The Wiki is used for some key documentation, but its use has been limited by the lack of a search capability (in practical terms, it's impossible to find information in the Wiki).
We've had zero problems with Fossil; no data corruptions, unresolvable conflicts, etc.
289500160 bytes (289.5MB)
Number Of Artifacts:
58707 (25417 fulltext and 33290 deltas)
Uncompressed Artifact Size:
36238 bytes average, 28208782 bytes max, 2127344919 bytes (2.1GB) total
Number Of Check-ins:
Number Of Files:
Number Of Wiki Pages:
Number Of Tickets:
Duration Of Project:
2212 days or approximately 6.06 years.
Off to grab my copy of 1.30 ...
Boeing Network & Space Systems