contributing to GnuCash [WAS: Re: Upgraded system and GnuCash]

Josh Sled jsled at
Wed May 26 11:58:40 EDT 2004

On Wed, 2004-05-26 at 11:46, Derek Atkins wrote:

> Also, there are lots of non-coding tasks to be done, like documenting
> which features are still unimplemented or don't work right.

Another really good way to help is to flesh out the unit-tests and
infrastructure.  This will not only ensure that the existing code is not
buggy [and it _will_ find new bugs], but also serve as a set of
regression tests for changes made in the future.

It's also something that effort taken to whatever level of technical
depth one is comfortable with can be valuable... i.e., figuring out what
the correct inputs/outputs should be, writing that into english/text,
and then transliterating that into code are all indepdently valuable


-- - `a=jsled;; echo ${a}@${b}`

More information about the gnucash-user mailing list