Interest in developing account_tr, edocument_ubl Turkish extensions, and a generic R&D module

Hello Tryton community,

I am a developer based in the UK, currently building and testing localisation modules for Turkey while also exploring a generic module that could benefit the broader community. I wanted to share my roadmap here to get early feedback and understand whether these contributions would be welcome upstream.

What I have built so far (locally, under real-world testing):

account_tr: A Turkish accounting localisation module following the same pattern as account_de_skr03, account_es, etc. It defines the Turkish chart of accounts aligned with the Turkish Uniform Accounting System (Tek Düzen Hesap Planı).

Turkish e-document support: Rather than creating a separate module, I have extended the existing edocument_ubl module using the specification concept pattern already established in the codebase, to support Turkish e-invoice (e-fatura) and e-dispatch note (e-irsaliye) formats as required by the Turkish Revenue Administration (GİB). I believe this is the correct upstream approach.

Both are currently being validated in a real production environment at a manufacturing company in Turkey. Once I am satisfied with the test coverage and stability, I plan to split the work into focused MRs for community review.

Future interest: generic Research&Development module:

After the above contributions are settled, I am interested in proposing a generic project_research or similar module to support Research & Development activity tracking. This would build on top of project, timesheet, and analytic_account, and would not be Turkey-specific. I have not seen this discussed before and wanted to gauge whether there is broader interest before investing time in a blueprint.

Further down the road:

I also intend to work on a account_gb module and Making Tax Digital (MTD) compliance for the UK, though these are longer-term goals.

I would greatly appreciate any early feedback — particularly on whether the edocument_ubl extension approach is acceptable to the core team, and whether a generic R&D module is something the community sees value in.

Thank you for the work you do on this platform.