Hi Katie, Thanks for your interest. A little of both, I think, if I understand your example options.
My goal is possibly the same as yours, that is, to maximize OSAF developer productivity towards new features and functions, as compared to following up on bug reports that have questionable reproducibility instructions at best, or have a root cause in a misconfigured user environment at worst. It seems to me there might be/are probably others like me who encounter issues that occur more than once, but are unable to reproduce these issues consistently such to be able to craft a coherent bug report for further investigation by a developer. I think there may be an opportunity to provide a bit of structure to the community of "some-what technical, but non-developer" dogfooders through perhaps a list. It could happen, for example, that more technically-skilled dogfooders step in are assist others in distinguishing between known issues (a.k.a. duplicate bug prevention), user environment issues, and user expectation mismatches (expectations speeding ahead of the release plan). Dogfooders might be able to assist each other in verifying instructions for reproducing issues, all prior to intial triage <grin> by the developer(s) covering the relevant component. It seems to me that developers and dogfooders share a common lack of interest in bug research that results in a "works for me" tag though the dogfooder continues to experience the issue. The opportunity for OSAF as preview approaches is to shape and manage actively the expectations of the eventual beta users by working out in advance the mechanics of the support of early adopters. Hope that makes sense and is helpful. Please let me know if you have any questions. Thanks, Andre On Tue, 19 Dec 2006 17:02:21 -0800, "Katie Capps Parlante" <[EMAIL PROTECTED]> said: > Andre Mueninghoff wrote: > > Following the draft instructions for dogfooders, I took the liberty of > > mentioning the issue on this list. Perhaps I should have mentioned it on > > the Design list. > > > > On that note, I would suggest a DogFooding specific list with the goal > > of applying some preliminary filtering to minimize the submission of > > bugs that end up with the "works for me" resolution and potentially > > waste valuable developer time. > > Hi Andre, > > By "dogfooding specific list", did you mean a list of known bugs, or a > list of areas that should work/be tested? > > Its always good to see more dogfooders -- much appreciated! > > Cheers, > Katie -- Andre Mueninghoff [EMAIL PROTECTED] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
