On May 18, 2002 01:21 am, Conrad Canterford wrote: > My list would be shorter and simpler, for reasons of simplicity for > users. > > My list would be: > Importing > Storage > Reports > User Interface > Translations > Developer interface > Documentation. >
I'd say even this list is too long. Don't think like a programmer; think like a naive converted Quicken user. They don't understand modularity. You'll be lucky if they can identify their Gnucash version. Users just want to get work done. Bugs get reported on a what-the-heck, time-allows basis. Every little hurdle increases the chance that the user will give up and go do something fun or useful. You lose the bug report, and maybe the user. I feel guilty about suggesting work for other people, but ... the bug reports aren't pouring in. What if there were just one component, "GnuCash", and the bug manager sorts and routes bug reports as necessary? When that turns out to be too much work, then make up a component set. The bug manager will have experience (and motivation!) to come up with a good set. _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
