>> I call those drive-by bug reports. > > I'd welcome drive-by patches. ;-)
Good one, made me smile today. > But only to a certain extend. We also get the "I can't send > email"-stuff which in 99.99999% of all cases is config related. But I > guess there are various things how we can improve that etc.. Shoot me a top three issues that aren't bugs that you run across. 1) PHP memory limit reached. ( Which actually may be a bug in some cases ) 2) Database misconfigured 3) ??? > I try to confirm them too. I am trying to check Trac's timeline every > day and work through issues. It obviously doesn't work always like > that, but generally that's what I try. And when I say, "I", I really > mean "we". I know are doing the same. Fabulous. >> OK, what about RFE's though ? > Could have a trac ticket, I suppose. There is nothing wrong with it. > But currently it doesn't always work like that. That's what I would like to see, is some responses here on how to best handle RFEs. I think there seems to be an extablished "workflow" for bugs, it is more a matter of getting users to push feedback into what is established. With RFEs it doesn't seem like a similar "workflow" exists. Maybe one doesn't need to exist, I don't know. However, I subscribe to the users mail list and there are some drive-by RFEs there. If I had a page or procedure to point them to . . . Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265 _______________________________________________ List info: http://lists.roundcube.net/dev/
