Automated Bug Reporting Tool
One of the new Fedora 11 features is a project called ABRT (read "ABoRT") - an Automated Bug Repoting Tool - https://fedoraproject.org/wiki/Feat ures/ABRT . Even though the name explains a lot there's still a lot to say about this cool tool. First thing - it's brand new and it's still work in progress. Some of the features are already working in Fedora 11, some of them are being implemented right now. The full list of features working in F11 and plans for 2.0 release is available at https://fedorahosted.org/abrt/wiki . Second thing - it needs testing and it needs interest from other maintainers and developers.
So how does it work? There' are already similar tools out there right? Like bug buddy - but wait, bug buddy is tight to gnome and it's not much useful for your apache or even kernel. Ok, so kernel has kernel oops .. it's nice and neat, but also just kernel specific. So the goal was to implement a framework which would work for all use cases - from kernel to desktop, from compiled code to scripting languages, and reporting bugs where ever you would like to have them. ABRT is the tool.
Now I can start talking about the architecture and plugins structure but I won't. I'd rather invite your for FUDCon in Berlin, which happens in few days and where I and Zdenek Prikryl, one of the ABRT developers, plan to talk about ABRT and show you the tool itself, but also how to tune it for your purpose and how to help us improving it. Stay tuned, we'll be on stage soon!
So how does it work? There' are already similar tools out there right? Like bug buddy - but wait, bug buddy is tight to gnome and it's not much useful for your apache or even kernel. Ok, so kernel has kernel oops .. it's nice and neat, but also just kernel specific. So the goal was to implement a framework which would work for all use cases - from kernel to desktop, from compiled code to scripting languages, and reporting bugs where ever you would like to have them. ABRT is the tool.
Now I can start talking about the architecture and plugins structure but I won't. I'd rather invite your for FUDCon in Berlin, which happens in few days and where I and Zdenek Prikryl, one of the ABRT developers, plan to talk about ABRT and show you the tool itself, but also how to tune it for your purpose and how to help us improving it. Stay tuned, we'll be on stage soon!

GNOME dependencies
But so is ABRT, at least the current GUI frontend. It depends on GTK+ and other GNOME stuff. And it won't work on KDE apps because KCrash intercepts the crash before ABRT gets to see it and starts drkonqi instead (and there's no way we're going to disable that in favor of a GNOME-based tool). Also note that upstream KDE has just spent a lot of time on improving KCrash/drkonqi for KDE 4.3, so I don't think you'll find high enthousiasm for a KDE frontend to ABRT over there.
Re: GNOME dependencies