Reviews and Ratings
PhysicsFS (aptly known as PhysFS) is the best low-level library I've ever used. Small, fast and easily integrated, PhysFS is, hands down, one of the best file system abstraction API's to date and is especially useful for games and embedded systems needing a very small memory footprint.
That being said, there are a few issues to be concerned with. First and foremost, PhysFS is not for the feint of heart or the absolute beginner. If you're not comfortable building your own libraries from scratch, this is not your library (although the CMake system does indeed make the process much less painful).
The lack of really good tutorials coupled with some of the worst examples I've ever seen (said examples are not from the developer or linked from the official website) makes for a bit of a learning curve but this can be easily overcome by looking at the official tutorials and reading the libary documentation (which is actually really good).
Once you get the basics down, PhysFS proves to be extremely useful, efficient and safe. It makes file-system operations virtually transparent (there are some differences in the directories you would use to initialize the library depending on platform) and is capable of working with highly compressed archives in a number of popular and not-so-popular formats.
After looking around for a long time and using one bug tracking system after the next only to be disappointed by one thing or another I eventually settled on Mantis but I was never thrilled with it. Mantis is entirely designed for programmers to use, not end-users.
I had avoided Bugzilla for a long time (and I'm embarassed to say this) because of its name. I really hate the '-zilla' suite of names but once I saw how a live system worked with SDL's installation I immediatly knew that this was the bugtracking system I wanted.
It was a little tough getting it installed properly on a web host that I wasn't physically sitting at but once I learned how to log in to a terminal session remotely the installation was actually pretty straight-forward and went pretty smooth.
There are a few things that I would change about Bugzilla's interface but the reality is they're really minor points (and more than likely I can customize it... just need to read the docs). Ultimately the system is much better suited for knowledgable non-programmer end-users (you know, the ones you actually *want* sending you bug reports) and has a superior administrative back-end.
I've only been using Bugzilla for a short time but, quite frankly, I'm thrilled I installed it.
Redmine is, hands down, the best task management solution I've ever come across. The only drawback I've experienced with it is that if you're unfamiliar setting up Rails applications there's definitely a learning curve.
Beside that, Redmine has been a major boon to the development of my current project. With a very clean, well designed and well polished interface, Redmine looks and feels professional. It's interface is very intuitive with a short learning curve which is a key point for our particular needs.
Also included with it is a built-in Wiki which, while not as powerful as MediaWiki, is well integrated with Redmine and makes internal linking very easy. It also includes the ability to upload files which is very useful as well.
The other key feature is the repository feature which works with several of the most popular source version control schemes (we use Subversion). It's extremely helpful to be able to link commit notes with issues.
Other interesting features that I haven't had the chance to take advantage of yet include Project News, Forums and a few others that I can't remember off the top of my head. I'll leave the reviews for these features up to others but if they're anything like the rest of Redmine than I'm sure they're more than adequate for anybody's needs.
If you're not afraid of learning how to set up Rails applications (or to learn how) than this is absolutely the solution you should be using! Redmine raises the bar for FOSS task management solutions.