Slashdot Mirror

One simple to setup option would be Fossil's builtin issue tracking. A singles executable to download and "install". Web-based UI and the issue tracker is very configurable. http://fossil-scm.org/

For access outside your home/office LAN, you will need to use stunnel or configure your Internet-facing webserver to forward HTTP to your Fossil server.

Many large companies have a lot of trouble with git. It's not a coincidence that Facebook and Google have been working on Mercurial backends: For their needs, Git is absolutely insufficient.

These companies should consider using Fossil. Fossil is a mature DVCS, BSD-licensed. It is extremely elegantly written, and provides client, server, GUI, CGI executable and web server in a single binary file. It includes a Wiki and a bug tracker for each project. It does not litter your working copy with unnecessary files - only a single dot-file in the highest directory. It was not written in two weeks.

Fossil deserves to be much better known, but for some reason Git gets all the attention.

https://www.fossil-scm.org/

Free project hosting is available here:
http://chiselapp.com/

I'd agree with Fossil for this team - not only does it come with wiki, tickets and all that project management stuff built into it, its also a way of making DVCS use easier - and it doesn't have the dangers of git (the number of times I've seen people work with git only to say "umm, it seems to have..." makes it a poor choice especially for teams that don;t have a git guru to fix it)

Fossil is much under-rated, for this team, its possibly the ideal choice. Written by the same guy who did SQLite so it should be pretty solid. I know its very easy to set up and get going with even though I've not used it in anger.

Its true, git is complex like Linux is - it suits the needs to Torvalds, but I think its popularity exceeds its ability, and many people use it without using it properly - for example a previous company I worked for used git for their SCM and I asked where the backups were I was told they didn't need backups because it was distributed and everyone had a copy of the repo... of course, that relies on everyone having a copy of each repo, or at least 1 other person having an up-to-date copy of each repo which wasn't the case. This kind of thinking wouldn't happen if there was more of a concept of distributed-but-from-a-central-repo. It needs the concept of a golden root from where everything else is sourced (and I know you can have this, but its more convention due to the distributed nature)

Still, it ushered in a new style of version control that wasn't catered for before.

Now we're seeing easier, more accessible systems, such as fossil by that attempts to bridge the gap between DVCS freedoms and centralised repositories and includes other useful features such as bugtracker in the SCM and still geared towards branches that are more collaborative than gits 'private playground' branches. (ie git is designed for people to work on their own and hopefully merge changes back, many other SCMs are designed for branches that are for common code worked on by several people and thus requiring less merging). Git works well because of how the Linux project is structured - a very large hierarchy, but starts to fall down in a small team where people don't have that arms-length working environment, or where they work on multiple branches at the same time (eg at work, I have my big feature and I have bug fixes that come and go regularly - git doesn't help in that environment unless I have multiple repos checked out)

I like Fossil for small projects. Includes tickets and a wiki as well as version control. I don't know how accessible it would be on an iPad but I've played with the Android version a bit. http://fossil-scm.org/index.ht...

I have taken a cursory look at Git but never really developed with it. I understand most of its fundamental characteristics however.

Personally (and professionally), I chose fossil for my development needs. It's small, fast, correct (so far Git is the same), easy, and integrated with a bug tracker and a wiki (all which cannot be said of Git). The author is no lame duck either, he's the guy who created SQLite.

If you're about to start doing decentralized development, check it out. It's worth your time.

JigJag

Personally (and professionally), I use Fossil. It has much of the strength of Git while remaining approachable. Bonus, the built-in cgi server/bug tracking/wiki/timeline tree. All this in a single binary less than 1 Mb.

Just use Fossil (http://www.fossil-scm.org). It does what you want, for free, including disconnected mode. Plus it has built-in bug reports, wiki and authentication.

Tell your boss that you need nothing in terms of hardware, you already have your machines between you and the developer. However that tool allows you to measure your progress (she can see a RSS of your commits), track development, and allows you to develop new features easily without breaking the code.

JigJag

My personal programming hero, D. Richard Hipp, works with a very small team on SQLite (which you may have heard of). He uses his own, home-grown SCM called fossil. It probably doesn't scale to a zillion contributors but, like all of Hipp's work that I'm aware of, it's super clean and easy to use. Sounds pretty great for your use case.

And, as other people on this thread have already said: your habit of throwing stuff into production without testing it is similar to playing Russian Roulette with your company. Stop that. Stop that right now.

• Fossil, a simple, self-contained VCS in a sea of increasingly complicated or bloated systems.
• Quantum GIS, ridiculously fast & user friendly, beats IMO even the most expensive proprietary GIS solutions.
• Ardour multitrack recorder. Less unknown, but still could use a lot more love.

fossil, fuck yeah!

I've found Fossil extremely easy to use as an individual programmer... it incorporates wiki, issue tracking, and version control through a simple interface, the server software is a single executable and runs on the client with no setup required, and it is free. When you begin working in larger teams, the model is distributed version control. Its pretty slick.

Another alternative that I like is Fossil, which is about as easy as it gets to use, and comes with a wiki and bug tracking built in.

Yes, msysgit is pretty fast on mswindows, but too bloated for my smallish projects.
I prefer fossil http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki