Hi All, I've been reading the users mailing list to find information about my particular itch that needs scratching by GnuCash: Budgeting.
I realised that this is an issue that you keep getting asked the "when" question... I have had a few ideas about it and after seeing Benoit's "State of the Project" document I want to help. My idea was to get a discussion going on the users list, collecting what we users want. Then I was thinking, depending on activity - maybe once a week, bringing a "this is what we want" discussion over to this list. The point is to simplify the discussion (and your workload) so that than you developers needn't answer every little issue that is brought up. Rather being able to say "Proposal 15 is not implementable in the current code base", or (hopefully) "OK that should be straightforward". This does not mean that the code will be implemented, but if a clear plan of what _is_ to be done, then some of us newly motivated users can have a clear target to aim at. The difficulty I see with implementing budgeting is that there doesn't seem to be a clear idea of what the user base wants to see, and more importantly, what is possible within the architecture that exists. I haven't seen any (formal?) discussions of how budgeting would be implemented, so I'm guessing we (the user list) could perhaps aide in this development. However, before I start stirring on the user list, are their any ideas that people are actually working on at the moment, or does anyone have a reason that I shouldn't do this? Cheers, S.
pgp00000.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
