# Standard module maintained by externals
**URL:** https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178
**Category:** Organisation
**Created:** [March 30, 2026, 3:11pm UTC](https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178 "2026-03-30T15:11:17Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [March 30, 2026, 3:11pm UTC](https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178/1 "2026-03-30T15:11:18Z")
Here are my conclusions for [Is there anybody caring about Spanish modules?](https://discuss.tryton.org/t/is-there-anybody-caring-about-spanish-modules/9094) and [Is there anybody caring about German module?](https://discuss.tryton.org/t/is-there-anybody-caring-about-german-module/9095)
To maintain such locale modules, we need to rely on external maintainers because the code maintainers do not have the required knowledge.
Before inclusion, it is often easy to push the requirements to the same level as the other core modules because the contributor has the incentive to be included.
Once included, this incentive is gone and we must rely only on the goodwill of the external maintainer.
Over time, the requirements for the core modules evolve and we need to push them also to those modules. And this is where the friction starts, the external maintainers may not have the resources or may disagree with the new requirements. This means that only the technical minimum is done to keep them operational.
De-facto those modules become second citizen of the core modules. Indeed this situation is no different than if they were maintained outside the project. This is why I think the new rule should be that locale modules that core maintainer can not maintain should not be included in the core (at least until the external maintainer has shown for a long time (maybe 5 years) the willing to maintain to the core standards).
So this means that the `account_es*` and `account_de*` modules will be removed from the coming release.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [April 1, 2026, 9:01am UTC](https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178/2 "2026-04-01T09:01:09Z")
Reference:
- [Remove account\_es and account\_es\_sii modules (!3140) · Merge requests · Tryton / Tryton · GitLab](https://foss.heptapod.net/tryton/tryton/-/merge_requests/3140)
- [Remove account\_de\_skr03 module (!3213) · Merge requests · Tryton / Tryton · GitLab](https://foss.heptapod.net/tryton/tryton/-/merge_requests/3213)
---
### Author:  [@pokoli](https://discuss.tryton.org/u/pokoli)
#### Post date: [April 1, 2026, 11:22am UTC](https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178/3 "2026-04-01T11:22:52Z")
Just for reference, we moved the maintenance of the modules into tryton community repositories:
- [https://foss.heptapod.net/tryton-community/modules/account\_de\_skr03](https://foss.heptapod.net/tryton-community/modules/account_de_skr03)
- [https://foss.heptapod.net/tryton-community/modules/account\_es\_sii](https://foss.heptapod.net/tryton-community/modules/account_es_sii)
- [https://foss.heptapod.net/tryton-community/modules/account\_es](https://foss.heptapod.net/tryton-community/modules/account_es)
We welcome any other external modules that wish to share maintenace of the modules with a more flexible requirements.
---
### Author:  [@pnunez](https://discuss.tryton.org/u/pnunez)
#### Post date: [April 8, 2026, 7:30am UTC](https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178/4 "2026-04-08T07:30:19Z")
```auto
```
What are the steps to switch to extracted modules from the core?
From what I’ve seen, extracted modules change their prefix to “trytoncommunity”. Is it enough to uninstall the core module (using pip) and install the external module?