Gnucash week

[Damian Dimmich]

+1 on all these suggestions - however I imagine that getting all those changes in in one week may prove difficult. Improving the workflow for invoices certainly would add a lot of value to gnucash, and save people who use it for business significant amounts of time!

D

On 23 Jun 2010, at 14:14, Geert Janssens <janssens-geert at telenet.be> wrote:

> Hi Jesse,
> 
> Of the tasks you mention, improving the invoice/bill workflow is the one the 
> would benefit me the most, so I'd vote you work on that ;)
> 
> I had proposed some improvements a while ago on this list [1], but Derek 
> wasn't really happy with them as they didn't really follow the Gnome's human 
> interface guidelines.
> 
> The thread eventually comes up with other useful improvements, like a way to 
> duplicate invoices (even to other customers/vendors/employees), more complete 
> autocompletion, and scheduled invoices (which probably would require code for 
> duplicating invoices first).
> 
> Another great improvement would be a way to have the various importers (qif, 
> ofx, csv) to integrate more with the business functions. It'd be great if 
> either the importers allowed to assign payments found in the import data to 
> unpaid invoices in gnucash. Or the other way around, when paying an invoice 
> via the Pay Invoice dialog, it would be useful if there were a way to indicate 
> the payment is already in some account (gotten there via the import), and not 
> have it create a new entry.
> 
> Anyway, whatever you choose to work on, your contributions are appreciated !
> 
> Geert
> 
> [1] See mailing list thread
>    https://lists.gnucash.org/pipermail/gnucash-devel/2010-January/027168.html
> [2] See mailing list thread
>    https://lists.gnucash.org/pipermail/gnucash-user/2010-March/034072.html
> 
> On Wednesday 23 June 2010, Jesse Weinstein wrote:
>> I'm going to be devoting at least 2 hours a day to working on gnucash
>> from today through Saturday.  Before I get down to it, I'll need to read
>> through my backlog of -devel emails, and update and build trunk; but
>> once I do get started, here are some things I'm thinking of working on:
>> 
>> 1) Get the new check printing features working on Ubuntu 9.10 -- which
>> might be as simple as installing the new release from the Ubuntu
>> backports repo, or as difficult as manually backporting the features to
>> a custom package and hosting it on a PPA.
>> 
>> 2) Work on more complete doxygen documentation of gnucash internals,
>> which would involve (besides studying the code) questions to -devel
>> about the purpose and structure of various files, classes, etc.
>> 
>> 3) Learn and practice designing new reports; I'd see what's been
>> requested, and attempt to create some of them.
>> 
>> 4) Attempt to simplify and streamline the process for inputing invoices
>> and paying bills.  At least as I understand it, there are way too many
>> steps and dialog boxes in this process, and it'd be good to make it
>> easier to handle.
>> 
>> While I've been paying attention, and making limited contributions, to
>> FOSS for some years now, I'm pretty new to actually devoting time and
>> sustained attention to a project, and I feel somewhat anxious about it.
>> 
>> Any comments or suggestions regarding my effort, or any of the specific
>> tasks I mentioned, would be gratefully appreciated.
>> 
>> Jesse Weinstein
>> 
>> _______________________________________________
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> 
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel