FaultTrack is a new kind of bug tracker for .NET developers.
FaultTrack is a new kind of bug tracker for .NET developers.
Innovating and raising the bar by bringing real-time bug tracking, killer UI design, and productivity.
Innovating and raising the bar by bringing real-time bug tracking, killer UI design, and productivity. Read more
About this project
There will be an official announcement regarding the future of FaultTrack sometime between 4-7PM GMT.
Please share the following link: http://kck.st/MT1LWT on Facebook and Twitter, even if you cannot back the project or choose not to.
Major shifts are happening in software. Windows 8, "Metro" design principles, and more and more is expected from a piece of software. Developers especially demand that their tools be of the highest quality, and actually work for them. With FaultTrack, I am to not just innovate, but set the bar for future bug tracking systems. Why can't a bug tracker have a kick-butt interface design? Why can't it have a productive experience for the developer? Why haven't bug trackers actually helped during the debugging process?
I honestly believe that I can do better, and FaultTrack is going to re-define how bug tracking integrates into your debugging experience.
I've taken extremes to ensure that not just most, but all user interfaces in FaultTrack are well designed. I've used a mix of Metro inspired design principles and proven practices in UI design to deliver outstanding designs. And yes, I've themed FaultTrack to look much like Visual Studio 2010, because let's face it, it looks great.
FaultTrack is based around some very simple ideas.
- Bug tracking is intrinsically part of the debugging process, whether a developer acknowledges it directly or not.
- Automate things that make a developer slow, like copying exception data from the Visual Studio Exception Assistant into a bug tracker.
- Keep the tool out of the way of the developer, but have it ready when the developer needs it.
- Bug tracking should not be confined to the web. Let it live on the desktop, and work for all developers - those who have internet connectivity, and including those who do not. (eg. traveling, developing on a non-connected secure network).
- If you write in C#, Visual Basic, C++/CLI, F# or any other CLR compliant language, let's give you a tool that actually caters to that. The CLR and .NET platform have a user base of its own, its time that user base had a better tool for their specific needs.
- And while FaultTrack will be catered to CLR languages, there is nothing stopping you from using it for other languages.
See anything familar? Play, Pause, Stop, Restart? We have full access to the Visual Studio Debugger Services for Automation, and are fully interested in taking advantage of them in FaultTrack. This is the core of how I am doing real-time bug tracking for you, and will open up an entire box of goodies for the future. Right now I am focusing only on real-time bug tracking, but trust me, I have a ton of things planned.
So you're probably wondering right? Who the heck is this random guy? Hello, it's nice to meet you, my name is David Anderson. I linked to my blog where I talk about C# and .NET (I want to become a C# MVP) and I also want to create a software company and create jobs while writing kick-ass software. And, with a twist, I seriously want to prove to the world that anyone can do it without a college degree. People are smart, you just need to get them passionate about something, and generally the rest falls into place. It's alot of hard work, no doubt, but I'm ready for it. I've been doing it for two years already, and I'm still as motivated if not more than when I started.
FaultTrack will probably be somewhere between $35 and $125 as a one-time purchase, with very low prices for additional, extra keys. That's why we're offering product keys as part of the reward tier, so that you can save some money on top of feeling wonderful that you helped build our software.
I have developed software professionally for 4 years, and of those 2 has been through my own business. I have written software for many local businesses such as the Pueblo HARP Foundation, Pueblo Medal of Honor Foundation, and Friends of the Library. I've delivered countless desktop applications as well as complicated custom solutions. I have also been developing FaultTrack for a year and a half already, so this isn't something I'm just now starting.
Absolutely. The more we can raise, the more I can add to the schedule and feature list. Some ideas that have been suggested are Team Foundation Server and other Source Control Integration, Visual Studio Integration, and more advanced bug tracking features. The sky is the limit.
FaultTrack requires Microsoft Windows XP SP3 or later, and the .NET Framework 4. Other than that, FaultTrack has no other requirements or dependencies on other software. The setup installer, which I fully developed, deploys any additional dependencies so the user does not have to worry about prerequisites.
FaultTrack actually does not require Visual Studio to work, but the real-time bug tracking features will.
We are also working on ways for the real-time bug tracking features to work without Visual Studio as well, because there are situations where you might want to do some manual testing (perhaps in a release environment) where Visual Studio is not installed.
We have future plans to provide extensibility points for such reasons, and we actually will be developing integration support for Team Foundation Server using those extensibility points. This will open up the possibility for not only us, but other developers to implement support for version control systems.
Our maximum projection is to release by September 2013. The entire project and all remaining work has been estimated with padding, so it is also very likely that we can finish before September and release even earlier. Throughout the project we will be doing screencasts, and posting updates to keep everyone up to date on the progress. We will even be having a closed beta, and have plans for a CTP (Community Technical Preview) and RC (Release Candidate).
Absolutely. You don't have to use the real-time bug tracking features, and there is nothing stopping you from entering bugs manually into the bug tracker. We would never exclude this functionality because you may not always have Visual Studio when you need to enter a bug.
Two years ago I quit my day job to start DCOM Productions, and I've done many projects. During that time I've worked full-time on FaultTrack, and it evolved into a dream and an idea that no other bug tracker is doing. I want to finish that dream, and I want to share it with developers. I can't finish it in any reasonable amount of time without working full-time on the project, and that requires money. Up until now, I have put all my own money into this, I have risked everything to bring this thing into reality and people want it, and I want to give it to them. The $15K, after taxes, fees, and rewards will help me by allowing me to work on FaultTrack full-time, help keep me fed and clothed. I did this project by myself. There isn't a project manager, there isn't a QA team, there aren't any code monkeys or DBA's or anything else. I've filled every role for two-years. If we raise more, I would like to even put together a team, and create some jobs. By the end of September 2013, or even sooner, I will have delivered a full published product to you, but I need your support. Without your support and donations, there really isn't a way for me to make this project happen.
The project will be cancelled permanently since it cannot be afforded otherwise.
Support this project
- (30 days)