The payment amount must be greater than zero

[Patrik Lermon]

Hi Anndreww.

I know perfectly fine how the free source community works.
And most project that I have been involved it is fine to be on
the devel-list and:
 - not being harassed
 - being able to come with suggestions, without supplying a patch

This is after all the development list (and program development is, as
far as I know)
coding and ideas (and more to that of course).

I never in my life heard a discussion like this on a (serious) devel-list.
Usually you hear: "good idea, put it on the todo!" (may be implemented
in the future), or "bad idea" (won't be implemented, unless you fork).

If you feel that the todo is too long to ever cope with, put that on
the home page.
"We have 3 years work with the current todo, we won't accept any more
ideas right now."

If you have the recursive acronym gnu in you software you should try
to keep up with
the spirit surrounding it.

/Patrik

On 8/20/07, Andrew Wood <andrew at gn.apc.org> wrote:
> Hi Patrick,
>
> GNUcash has taken a huge amount of unpaid voluntary work by people who
> like to code.
>
> The way things get done in a project like this is to raise a bug report
> and wait;  but don't hold your breath as the feature or behaviour you
> want might never get done. That's the nature of projects like this, run
> by volunteers and in this case not sponsored by a corporation or other
> means.
>
> One way in which you might want to try and prioritise your request is to
> offer money. There might be some developer subscribing to the list
> who'll take up your offer. Of course, people might not have the time or
> expertise to take up your offer but it sometimes works. You might be
> supprise how much even the small change your asking for could cost, or
> should cost.
>
> Best wishes,
>
> Andrew
>
> Andrew Wood, Oxford, England
>
> ----------------
>
> Patrik Lermon wrote:
> > On 8/20/07, Derek Atkins <warlord at mit.edu> wrote:
> >
> >> Vahur Lokk <vahur.lokk at gmail.com> writes:
> >>
> >>
> >>> As for the abovementioned payment-merging process, this is in itself an
> >>> architectural mistake that has to be overwritten sooner or later.
> >>> Multiple-payment system that does not allow for picking
> >>> non-consequential invoices to be paid just does not survive in a real
> >>> life very long.
> >>> Negative payment should never look like invoice, but exactly what it is,
> >>> negative payment, correction of a mistake. The same applies to negative
> >>> invoice.
> >>>
> >> I eagerly await your patch to correct this "mistake"!  (See my previous
> >> email to Patrik).
> >>
> >
> > Why don't you start using curse words and calling us names, to get the
> > complete feeling of hostility on this list?
> >
> > Develop-list are usually not only meant for programmers, but for
> > people interested in the development.
> >
> > /Patrik
> > _______________________________________________
> > gnucash-devel mailing list
> > gnucash-devel at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> >
> >