Discussion:
4 Year Fossil Success Story
(too old to reply)
Backe, Martin G
2015-01-29 20:35:30 UTC
Permalink
I thought I'd use Fossil for a bit before posting our success in using it. It's been about four years now, so it's time ;-)

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.


Repository Size:

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

Compression Ratio:

7:1

Number Of Check-ins:

7084

Number Of Files:

5546

Number Of Wiki Pages:

40

Number Of Tickets:

3444

Duration Of Project:

2212 days or approximately 6.06 years.



Off to grab my copy of 1.30 ...


Marty Backe
Boeing Network & Space Systems
Richard Hipp
2015-01-29 20:52:27 UTC
Permalink
Post by Backe, Martin G
I thought I'd use Fossil for a bit before posting our success in using it.
It's been about four years now, so it's time ;-)
Thanks for sharing. I'm glad Fossil is working out for you.

I did note that your repository is not compressing very well. 7:1 is
pretty low. Maybe you have lots of binary files?
--
D. Richard Hipp
***@sqlite.org
Stephan Beal
2015-01-29 20:54:50 UTC
Permalink
:-D

i'd be interested in seeing your ticketing customizations,if you are at
liberty to show them to us.

----- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
I thought I’d use Fossil for a bit before posting our success in using
it. It’s been about four years now, so it’s time ;-)
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.
*Repository Size:*
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
*Compression Ratio:*
7:1
*Number Of Check-ins:*
7084
*Number Of Files:*
5546
*Number Of Wiki Pages:*
40
*Number Of Tickets:*
3444
*Duration Of Project:*
2212 days or approximately 6.06 years.
Off to grab my copy of 1.30 

Marty Backe
Boeing Network & Space Systems
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Warren Young
2015-01-29 22:20:02 UTC
Permalink
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).
It searches titles, but not content. That’s been fine for our purposes, but we’ve only got about a dozen documents in the wiki so far, so it’s not hard to remember at least one word from the title.

Devs: Is there a better reason than round ’tuit why Fossil doesn’t use SQLite’s FTS features for this?
Backe, Martin G
2015-01-29 22:44:13 UTC
Permalink
The Wiki works great for a couple dozen pages. But since you can't search the content, you become reluctant to create new pages because you aren't confident the information will be findable.

So it becomes a self-fulfilling prophecy - The Wiki works great for a small set of pages.


-----Original Message-----
From: fossil-users-***@lists.fossil-scm.org [mailto:fossil-users-***@lists.fossil-scm.org] On Behalf Of Warren Young
Sent: Thursday, January 29, 2015 2:20 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] 4 Year Fossil Success Story
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).
It searches titles, but not content. That’s been fine for our purposes, but we’ve only got about a dozen documents in the wiki so far, so it’s not hard to remember at least one word from the title.

Devs: Is there a better reason than round ’tuit why Fossil doesn’t use SQLite’s FTS features for this?
_______________________________________________
fossil-users mailing list
fossil-***@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Backe, Martin G
2015-01-29 22:50:24 UTC
Permalink
You're correct. We keep all of our jar libraries in the repository. I know that's not always recommended, but it's convenient, and it works!
Richard Hipp Thu, 29 Jan 2015 12:53:38 -0800
Thanks for sharing. I'm glad Fossil is working out for you.
I did note that your repository is not compressing very well. 7:1 is
pretty low. Maybe you have lots of binary files?
Backe, Martin G
2015-01-29 22:59:18 UTC
Permalink
Unfortunately I'm not able to expose any specifics of our configuration. But in general, we've just added some additional fields which allow us to maintain PBIs as tickets within Fossil. Reports are then created which allow us to view completed and to-be-completed work for a given Sprint.

Fossil fits perfectly with an Agile development environment.
Stephan Beal Thu, 29 Jan 2015 12:55:33 -0800
:-D
i'd be interested in seeing your ticketing customizations,if you are at
liberty to show them to us.
Continue reading on narkive:
Loading...