SI Reasoning wrote: > This is just a temporary influx of novice helpers who > are having their first stab at assisting with bug > reports. We all have our first times and wing it as > best as we know how. Maybe a simple reporting faq is > in order to help orient those who want to help? > > I am still trying to learn the ropes myself and only > get better as I get feedback. The faq should contain > some basic debugging commands, as well as a link to > the cooker archive to encourage people to look if > their problem has already been reported. >
8.2 is drawing near, and Cooker has more input. This can only be a good thing, sicne it means more people are using it. I think that if a question/problem has to do with Cooker, then this is the right place. Sometimes I ask more "tech support" type questions when I am reading the list when I am tired, so I think that even if a new user's bug reports "suck", so again, if it's a bug report about Cooker this is probably the right list to stick it on. Should there be a page on how to write good bug reports? Sure. How do we make people read this before subscribing? I don't know, send them an email when they subscribe. Have the bug report (URL) as part of this message. Since bugzilla is restricted, one still doesn't have a nice way to query if a bug is reported if they are a newbie. Due to the high volume of the list, I, too, sometimes miss things even though I try to "read" the whole thing. -- Sincerely, David Walluck <[EMAIL PROTECTED]>
