Comments on: A Different Kind of Bug Database http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/ On Mac OS X programming Thu, 12 Aug 2010 19:25:08 -0400 http://wordpress.org/?v=2.8.5 hourly 1 By: mr_noodle http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-855 mr_noodle Fri, 23 Mar 2007 19:43:50 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-855 I think the key is that the search is primarily on the symptoms. It is meant to solve problems not be something that is browsed. Keywords/tags/categories of some sort are also needed. Maybe at some point, have a "20 questions" style interface where successive questions are asked until the problem is narrowed down. A virtual bug doctor, if you will. I'm wondering if using a modified version of Mantis or Trac would work to start off with. Otherwise, Joachim, are you volunteering do to a rails version :) ? I think the key is that the search is primarily on the symptoms. It is meant to solve problems not be something that is browsed. Keywords/tags/categories of some sort are also needed. Maybe at some point, have a “20 questions” style interface where successive questions are asked until the problem is narrowed down. A virtual bug doctor, if you will.

I’m wondering if using a modified version of Mantis or Trac would work to start off with. Otherwise, Joachim, are you volunteering do to a rails version :) ?

]]> By: Conor http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-852 Conor Fri, 23 Mar 2007 08:59:19 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-852 The idea is a good. The most important thing is a place for the crash log, stack trace, error or warning. As we would all describe a bug differently but not the computer, it would make the database very useful if you could limit the search just to that field. If it's built on Cocoadev it should be like the Cocoadev users page where any new bug page has a tag that would make it show up alphabetised on an index page to be searched by title and description. Maybe I am asking for too much and not doing anything about it. I'll go away now and think. The idea is a good. The most important thing is a place for the crash log, stack trace, error or warning. As we would all describe a bug differently but not the computer, it would make the database very useful if you could limit the search just to that field.

If it’s built on Cocoadev it should be like the Cocoadev users page where any new bug page has a tag that would make it show up alphabetised on an index page to be searched by title and description.

Maybe I am asking for too much and not doing anything about it. I’ll go away now and think.

]]> By: Joachim Bengtsson http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-851 Joachim Bengtsson Thu, 22 Mar 2007 21:34:50 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-851 Excellent idea! I know Google works pretty good for finding answers by just googling the error message, but not rarely you just get unanswered forum posts or stupidly designed message list archives. However -- NOT on a wiki! Please oh PLEASE! Can't be pretty-presented as Scott says, the data can't be consolidated or bitshuffled or handled in any way except as strings. Euch. Could probably be thrown together pretty fast in rails. Excellent idea! I know Google works pretty good for finding answers by just googling the error message, but not rarely you just get unanswered forum posts or stupidly designed message list archives.

However — NOT on a wiki! Please oh PLEASE! Can’t be pretty-presented as Scott says, the data can’t be consolidated or bitshuffled or handled in any way except as strings. Euch.

Could probably be thrown together pretty fast in rails.

]]> By: Scott Anguish http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-850 Scott Anguish Thu, 22 Mar 2007 21:25:22 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-850 It's a wiki, it isn't cant be properly presented or organized. That's the problem with not having a central body responsible for that. It’s a wiki, it isn’t cant be properly presented or organized.

That’s the problem with not having a central body responsible for that.

]]> By: mr_noodle http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-849 mr_noodle Thu, 22 Mar 2007 16:47:49 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-849 The information is out there. Like Jonathan said, it's an issue of presentation and organization. As it is, we have the resource in the form of the internet and a search engine. My thought was that it would be more like a reference, not a discussion. The entries would be concise and to the point and well-structured. It would be as if someone condensed the Cocoadev discussions on a topic into a Wikipedia article. I don't care who said what when, just what the final conclusions are. Maybe a Cocoadev subsection? The information is out there. Like Jonathan said, it’s an issue of presentation and organization. As it is, we have the resource in the form of the internet and a search engine.

My thought was that it would be more like a reference, not a discussion. The entries would be concise and to the point and well-structured. It would be as if someone condensed the Cocoadev discussions on a topic into a Wikipedia article. I don’t care who said what when, just what the final conclusions are. Maybe a Cocoadev subsection?

]]> By: Jonathan Wight http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-848 Jonathan Wight Thu, 22 Mar 2007 16:20:20 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-848 Dan, Probably not a bad idea. Things do tend to get burried in cocoadev though. It is a great resource I just wish it did a better job presenting and organising the data. Dan,

Probably not a bad idea. Things do tend to get burried in cocoadev though. It is a great resource I just wish it did a better job presenting and organising the data.

]]> By: Dan Wood http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-847 Dan Wood Thu, 22 Mar 2007 16:11:25 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-847 Would it make sense just to put this into the cocodev.com wiki tht already exists, so there is a cross reference to what's there now? There actually is a lot of diagnostic information there already.... Would it make sense just to put this into the cocodev.com wiki tht already exists, so there is a cross reference to what’s there now? There actually is a lot of diagnostic information there already….

]]> By: mr_noodle http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-846 mr_noodle Thu, 22 Mar 2007 15:45:05 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-846 I'm all for it. Post the link here if you set it up. I’m all for it. Post the link here if you set it up.

]]> By: Jonathan Wight http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/comment-page-1/#comment-845 Jonathan Wight Thu, 22 Mar 2007 15:37:48 +0000 http://www.noodlesoft.com/blog/2007/03/22/a-different-kind-of-bug-database/#comment-845 Sounds like a job for a wiki. How about starting it under the venerable #macsb wiki: http://macsb.ironcoder.org/ ? Sounds like a job for a wiki. How about starting it under the venerable #macsb wiki: http://macsb.ironcoder.org/ ?

]]>