I haven't seen that page mentioned in the lists; do you mean that there have been discussions on the list related to GnuCash design generally?
If the latter, then I'd point out that a wiki page covering this active project's design and development that has seen edits only once every three years since its creation 10 years ago might not be as primary a source as it could be. GnuCash's wiki has many such pages buried in plain sight. Attempts to remove such aspirational but ultimately inaccurate and misleading information in the past have met with strong resistance, so there you are. As I understand it, the developers focus on entries in bugzilla (bugs.gnucash.org) to address problems and proposals. It is better advice to suggest that users with specific suggestions for improvement submit requests for enhancement (RFEs) there. David T. On Sep 8, 2024, 4:32 AM, at 4:32 AM, flywire <flywi...@gmail.com> wrote: >I've seen >https://wiki.gnucash.org/wiki/Project_and_Design_Documentation >raised a bit in the gnucash-user mail list recently and I recall >Geert's >comments about updating the csv importer and not documenting it. That >wiki >hasn't effectively been updated for a decade with the meaningful part >written in html. I updated it to markup so it is not such an arduous >task >to make a few comments. > >It would be handy if someone with an oversight of development over the >last decade would update it to be more meaningful. > >Regards >_______________________________________________ >gnucash-user mailing list >gnucash-user@gnucash.org >To update your subscription preferences or to unsubscribe: >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@gnucash.org To update your subscription preferences or to unsubscribe: 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.