Possible way forward for Gnucash bug 721822

[Christian Stimming]

Dear Paul,

in addition to the other reply for this idea, I'd like to add some more 
thoughts from myself.

I think it is a good proposal to ask what it would take to have some specific 
bug worked on. I've reacted on such requests earlier and successfully solved 
somebody's issues as contract work. In this case I might be interested too, 
except that the bug report at hand seems to be a hard one and it might take a 
few investigations until one could state whether there is a possibility for 
improvement at all.

However, this developer list has grown more quiet over the years. Hence, even 
if that request had been sent to the list initially, there might have been 
very little reaction, too. Feel free to contact me personally if you still 
would like to follow on about this issue. Other people might have contacted 
you, too, but on the list there doesn't seem to be much additional interest. 
Sorry for that.

Best Regards,

Christian Stimming

Am Donnerstag, 1. September 2016, 07:19:17 schrieb John Ralls:
> > I'm writing to ask whether either or both of you (or perhaps other members
> > of the team) might be interested in digging deeper into this performance
> > issue <https://bugzilla.gnome.org/show_bug.cgi?id=721822> in exchange for
> > cash?  There are so far two candidates who've indicated this is causing
> > them continued frustration and might be willing to contribute something. 
> > I'm hoping there are others.
> > 
> > I believe that others might come out of the woodwork if there was a target
> > figure to aim for.  Is this something you (or other maintainers) might be
> > willing to quote on? Coming from a software background myself, I
> > understand that this can be a "how long is a piece of string" question.
> > But perhaps you could provide an initial quote which is simply to spend
> > some limited time period on further analysis - to confirm the problem for
> > yourself and then determine a solution?  A separate quote could be done
> > on the actual implementation.
> Dear Mr. Phillips,
> 
> First of all, it is considered rude in the open source community to send
> mail directly to developers rather than communicating via the mailing list.
> We have one and I've copied it on this reply for your convenience. You'll
> need to subscribe in order to post. I've already gotten spam caused by you
> in the form of two bug comments on Bugzilla promoting your company. That's
> a violation of Gnome policy. Since you're promoting your company this
> letter is spam, too.
> 
> We have tried bounty programs in the past without success, as have many
> other open source projects. Per-item payments do not seem to attract
> developers to projects. The only successful approach in that regard seems
> to be for corporations to hire developers and assign them to open-source
> work; the best known examples would be Red Hat, which pays for most of the
> development on the Gnome Desktop and its infrastructure, and Canonical,
> which publishes Ubuntu.
> 
> Aside from that, the GnuCash team has set goals for future development.
> Performance is on the list, but not in the context of the bug you're
> referring to. I don't appreciate at all your attempts to override those
> goals by attempting to bribe me.
> 
> Regards,
> John Ralls
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel