Wouldn't using something like google code for bug tracking be better?

analgesic · 03-06-2013, 12:05 PM

Something like this is going to be much, much easier to track issues and focus user feedback than just using a forum.

JeffR · 03-06-2013, 10:19 PM

Quote:

Originally Posted by analgesic

Something like this is going to be much, much easier to track issues and focus user feedback than just using a forum.

We've got our own system like that. I'm checking the bug reports and copying them over to that when appropriate.

analgesic · 03-07-2013, 12:29 AM

Oh, I'm sure. But even with a relatively few number of people posting here so early in the public beta, I've come across things posted in several different places, duplicated reports across multiple threads, etc -- and the problem will only get worse with more users and posts.

Using a public bug tracker designed to streamline discussion of these problems might make it easier. Not only would it give you the chance to have more helpful feedback from better focused user conversations, it would also go a long way towards managing the influx of new bug posts that will inevitably occur as development continues and new users join. The ability to easily merge posts into existing discussion threads and mark new reports as duplicates seems like a rather powerful tool to manage feedback moving forward. If duplicate posts are appearing already after only a few users over a few days, doesn't it stand to reason that it'll only get worse?

03-06-2013, 12:05 PM	#1
analgesic Minors (Triple A) Join Date: Mar 2013 Posts: 208 Infractions: 0/1 (1)	Wouldn't using something like google code for bug tracking be better? Something like this is going to be much, much easier to track issues and focus user feedback than just using a forum.

03-07-2013, 12:29 AM	#3
analgesic Minors (Triple A) Join Date: Mar 2013 Posts: 208 Infractions: 0/1 (1)	Oh, I'm sure. But even with a relatively few number of people posting here so early in the public beta, I've come across things posted in several different places, duplicated reports across multiple threads, etc -- and the problem will only get worse with more users and posts. Using a public bug tracker designed to streamline discussion of these problems might make it easier. Not only would it give you the chance to have more helpful feedback from better focused user conversations, it would also go a long way towards managing the influx of new bug posts that will inevitably occur as development continues and new users join. The ability to easily merge posts into existing discussion threads and mark new reports as duplicates seems like a rather powerful tool to manage feedback moving forward. If duplicate posts are appearing already after only a few users over a few days, doesn't it stand to reason that it'll only get worse?