Archiving old transations
Bob Brush
bobbrush3 at gmail.com
Fri Jun 21 01:37:15 EDT 2013
Thank you, this is how the ball gets rolling, usually it takes thousands more than hundreds, but perhaps more people will read and have a similar interest. I also hope no potential problem solver is offended by this kind of back and forth, and certainly don't intend to say that any developers are obligated to even read this, much less jump. Just maybe it will be a mutual need of some one with the ability to help :)
Bob Brush
Sent from my iPhone
On Jun 21, 2013, at 1:22 AM, Jonathan Kamens <jik at kamens.us> wrote:
> I pledge $100 toward a bounty to go to the developer who implements the functionality that I need within GnuCash, payable in US dollars, bitcoins, or beer, developer's choice.
>
> The exact functionality is TBD. Here's a first stab at what I think is needed, which is obviously up for debate:
>
> * The ability to mark all transactions prior to a certain date in an
> account as reconciled without having to go through the
> reconciliation process, e.g., I don't actually "reconcile" any of my
> "Expenses" accounts, but the transactions will need to be marked
> reconciled, because of the need for...
> * The ability to export all fully reconciled transactions in selected
> accounts prior to a specific date into a separate gnucash file, with
> the appropriate account records and other metadata for those
> transactions also exported into that file so that it is a valid,
> standalone file, after which the exported transactions are removed
> from the current file and replaced with initial-balance transactions
> in all the accounts from which transactions were exported.
>
> jik
>
> On 06/21/2013 01:09 AM, Bob Brush wrote:
>> It is frustrating, and I have felt the pain, my four year old file is 87mb and I have tried a lot of crazy ideas to speed things up. I know one thing that can really slow down startup is when I leave the customer summary page or a report open and the results are sorted by money owed, it literally takes minutes, if I have the same thing but sorted by name it is minimal in delay. Performance is really important to me and I intend to find improvements in this area, unfortunately my contribution would be in other people's time, which cost money, I don't think any one on this list would mention money, but I would be bold and say that if the need is constant and wide spread and there was an interest in making improvements, donations to that end increase the speed mor
>>
>> Sent from my iPhone
>>
>> On Jun 20, 2013, at 7:25 PM, Jonathan Kamens <jik at kamens.us> wrote:
>>
>>> On 06/20/2013 07:14 PM, David T. wrote:
>>>> As Open Source software, Gnucash is built, maintained, documented and supported by volunteers (like Colin Law, whom you skewer in your rant). The development team volunteer their time, their expertise, AND their code (hint hint) to benefit all users of GnuCash.
>>> I have been maintaining free software for >20 years. I have a Thunderbird add-on with >30,000 users, and another with >10,000 users.
>>>
>>> I have submitted patches to GnuCash in the past.
>>>
>>> I am not someone with no understanding of how free software works, nor am I someone who does nothing but complain without contributing anything to the free software community in general or to the specific projects about which I provide feedback.
>>>
>>> However, even if I were such a person, that would not disqualify me from criticizing the maintainers of GnuCash or any other project if I felt that they were failing to meet the needs of their users over a long period of time. Just because the software is free does not render its maintainers immune from criticism.
>>>
>>> I am worked up about this issue for five reasons:
>>>
>>> 1. It is an obvious, basic piece of functionality.
>>> 2. In fact, it is so obvious that the GnuCash maintainers have
>>> themselves said, in response to requests for it, that a solution was
>>> in the works. They said this numerous times spanning numerous years.
>>> No solution has emerged.
>>> 3. It has been asked for many times by many people over the years.
>>> 4. This has resulted in at least three different people developing
>>> independent solutions to the same problem, which is rather
>>> inefficient and counterproductive. None of these were integrated
>>> directly into GnuCash because, frankly, the GnuCash code base is so
>>> huge and convoluted that people find it difficult to work with it.
>>> The learning curve before productive work can be done within its
>>> source tree is quite steep.
>>> 5. It is rude and patronizing for the maintainers of a piece of
>>> software to tell it's users, "You don't need that, even though you
>>> think you do," as Colin did (and others have done in past, at least
>>> the ones who weren't instead apparently falsely claiming that a fix
>>> was in the works).
>>>
>>>> Since you've already written a script to perform the archiving function (sucky though it might be), why didn't you submit it to the GnuCash project years ago, so that other developers might have built upon and perhaps improved upon it--and then incorporated it into the project?
>>> I did. Over eight years ago. http://lists.gnucash.org/pipermail/gnucash-user/2005-January/012817.html
>>>
>>> Jonathan Kamens
>>> _______________________________________________
>>> gnucash-user mailing list
>>> gnucash-user at gnucash.org
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> -----
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
Sent from my iPhone
On Jun 21, 2013, at 1:22 AM, Jonathan Kamens <jik at kamens.us> wrote:
> I pledge $100 toward a bounty to go to the developer who implements the functionality that I need within GnuCash, payable in US dollars, bitcoins, or beer, developer's choice.
>
> The exact functionality is TBD. Here's a first stab at what I think is needed, which is obviously up for debate:
>
> * The ability to mark all transactions prior to a certain date in an
> account as reconciled without having to go through the
> reconciliation process, e.g., I don't actually "reconcile" any of my
> "Expenses" accounts, but the transactions will need to be marked
> reconciled, because of the need for...
> * The ability to export all fully reconciled transactions in selected
> accounts prior to a specific date into a separate gnucash file, with
> the appropriate account records and other metadata for those
> transactions also exported into that file so that it is a valid,
> standalone file, after which the exported transactions are removed
> from the current file and replaced with initial-balance transactions
> in all the accounts from which transactions were exported.
>
> jik
>
> On 06/21/2013 01:09 AM, Bob Brush wrote:
>> It is frustrating, and I have felt the pain, my four year old file is 87mb and I have tried a lot of crazy ideas to speed things up. I know one thing that can really slow down startup is when I leave the customer summary page or a report open and the results are sorted by money owed, it literally takes minutes, if I have the same thing but sorted by name it is minimal in delay. Performance is really important to me and I intend to find improvements in this area, unfortunately my contribution would be in other people's time, which cost money, I don't think any one on this list would mention money, but I would be bold and say that if the need is constant and wide spread and there was an interest in making improvements, donations to that end increase the speed mor
>>
>> Sent from my iPhone
>>
>> On Jun 20, 2013, at 7:25 PM, Jonathan Kamens <jik at kamens.us> wrote:
>>
>>> On 06/20/2013 07:14 PM, David T. wrote:
>>>> As Open Source software, Gnucash is built, maintained, documented and supported by volunteers (like Colin Law, whom you skewer in your rant). The development team volunteer their time, their expertise, AND their code (hint hint) to benefit all users of GnuCash.
>>> I have been maintaining free software for >20 years. I have a Thunderbird add-on with >30,000 users, and another with >10,000 users.
>>>
>>> I have submitted patches to GnuCash in the past.
>>>
>>> I am not someone with no understanding of how free software works, nor am I someone who does nothing but complain without contributing anything to the free software community in general or to the specific projects about which I provide feedback.
>>>
>>> However, even if I were such a person, that would not disqualify me from criticizing the maintainers of GnuCash or any other project if I felt that they were failing to meet the needs of their users over a long period of time. Just because the software is free does not render its maintainers immune from criticism.
>>>
>>> I am worked up about this issue for five reasons:
>>>
>>> 1. It is an obvious, basic piece of functionality.
>>> 2. In fact, it is so obvious that the GnuCash maintainers have
>>> themselves said, in response to requests for it, that a solution was
>>> in the works. They said this numerous times spanning numerous years.
>>> No solution has emerged.
>>> 3. It has been asked for many times by many people over the years.
>>> 4. This has resulted in at least three different people developing
>>> independent solutions to the same problem, which is rather
>>> inefficient and counterproductive. None of these were integrated
>>> directly into GnuCash because, frankly, the GnuCash code base is so
>>> huge and convoluted that people find it difficult to work with it.
>>> The learning curve before productive work can be done within its
>>> source tree is quite steep.
>>> 5. It is rude and patronizing for the maintainers of a piece of
>>> software to tell it's users, "You don't need that, even though you
>>> think you do," as Colin did (and others have done in past, at least
>>> the ones who weren't instead apparently falsely claiming that a fix
>>> was in the works).
>>>
>>>> Since you've already written a script to perform the archiving function (sucky though it might be), why didn't you submit it to the GnuCash project years ago, so that other developers might have built upon and perhaps improved upon it--and then incorporated it into the project?
>>> I did. Over eight years ago. http://lists.gnucash.org/pipermail/gnucash-user/2005-January/012817.html
>>>
>>> Jonathan Kamens
>>> _______________________________________________
>>> gnucash-user mailing list
>>> gnucash-user at gnucash.org
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> -----
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
More information about the gnucash-user
mailing list