[GNC-dev] Introduction

[Christopher Lam]

Welcome, Dean. My goals have been:
- push reports forward to extract as much information as possible from the
rich data available for use
- refactor report infrastructure, homogenise API
- pushing non-report code from guile to C
- improve UI and usability

Bugzilla is a good place to start, but many old bugs are now obsolete. The
mailing list archives and the git history are extremely useful.
Good luck!

On Sun, 6 Sep 2020 at 16:30, John Ralls <jralls at ceridwen.us> wrote:

>
>
> > On Sep 6, 2020, at 9:07 AM, Dean Jagels <dpj-gcash at mhtsa.us> wrote:
> >
> > Hello, all.  My name is Dean, and I'm interested in lending a hand.
> I've been doing software design, coding, and requirements definition for
> nearly 40 years.  I now find that I have some time to contribute to an
> open-source project.  I am a Quicken refugee who has been using GnuCash for
> several years now, so I figured I'd give it a go.
> >
> > I see that there are quite a few items in Bugzilla, and some of those
> are quite old.  How do you prioritize them?  Would there be value in me
> picking off some of the old ones to see if they still apply?
>
> Dean,
>
> Welcome!
>
> This being an all-volunteer project, we prioritize largely by individual
> whim. My whim goes something like 1: crashers, 2: breakage likely to affect
> many users, 3: advances my long-term design goals (replacing linked lists
> and hash tables of objects with SQL to replace QofQuery leading to
> multi-user access to the database and ad-hoc reporting, confining Guile use
> to reports, separating view and controller in the GUI code).
>
> Yes, it most certainly would be helpful for you to try to reproduce older
> bugs.
>
> If you haven't already, please review
> https://wiki.gnucash.org/wiki/Development and the pages linked there.
>
> Regards
> John Ralls
>
>
>
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>