Hi Michael,
I suspect you may not be familiar with the history on this; there's a fair amount of background.
The "ingest" code that lives inside of Beancount today was born in a different project I made, called LedgerHub, whose intent was precisely to do this. You can read more about it here:https://docs.google.com/document/d/11u1sWv7H7Ykbc7ayS4M9V3yKqcuTY7LJ3n1tgnEN2Hk/ (design doc) Beancount wasn't originally going to contain any importing code, it was to be done there, and the dream was to have people contribute many importers.
It did not really take off; I have found that people do not share their importers, or that there is insufficient overlap between all our institutions that it's not worthwhile to share them. I wrote a detailed post-mortem here: https://docs.google.com/document/d/1Bln8Zo11Cvez2rdEgpnM-oBHC1B6uPC18Qm7ulobolM/
Moveover, anonymizing downloads from institutions is really time-consuming and uncertain and I found myself unable to really do that, even for all the importers I shared. The best way to test your importers is to run regression tests on real files, and that is best done in the privacy of a personal code repository. Finally, I think that even sharing the list of the particular financial institutions you use can consist in a security liability.
I have since ported over all the "common" code to beancount.ingest, where it lives today. The CSV importer that lives there is intended as an example, though it's growing to become more and more useful (it's the basis for my own CSV importers, for instance).
If you really believe in the importer sharing idea I would encourage you to start another repository and do this. This should not be integrated in the Beancount repo, however.
Thanks, and happy to discuss more on the mailing-list,