For several years now, I’m complaining about the state of the Spanish modules (account_es and account_es_sii).
The only people who show interest and try to contribute, does not want to follow the requirements nor the guidance that I consider vital to be able for the community to maintain them. Only short-term fixes are proposed.
So I would like to know who is actually using them? And which features? What would be the impact for you of the removal?
Please remove it for 8.0 series! Currently the current modules are badly maintained and we can not create another version unless the official one is removed. This is clearly shown as there are a lot of issues pending to be merged or reviewed.
We (KOPEN) will maintain it by ourselves and end up this never ending drama. We will take care of making the code public and releasing it as we did with some other spanish modules like verifactu or facturae. Of course whoever who want is welcome to share efforts on it the maintenance.
This is irrelevant for the discussion.
Good for you but this is neither relevant.
I am not doing any development of any type for Tryton since a lot, however, as a user, I use account_es to have accountability and present taxes. Not having that modules in Tryton will make me move to another ERP.
I do not see the point in doing that. I would like to see Tryton grow in users and countries, not losing them.
My two cents.
We use both. However, because they lack the latest regulatory updates in their reports and have unapproved issues, we’ve had to fork or patch them.
IMHO, the current situation should be unlocked. Perhaps a solution for now would be to move the projects from the Foundation to tryton-community and work there improving them; with the aim of returning to the Foundation in near future.
For that we need contributors and contributors that are following the Tryton best practices.
I do not see why nor how developing outside the standard workflow will make the module magically more compliant with the standard and bast practice.
For me the only valid goal of developing outside is to not respect the them.
Also where are the contributors who are willing to improve those modules toward the Tryton standards?
They are tired of having useless discussions or just maintaining their own forks because of issuses are not fixed in Tryton standards.
We’re currently using the Spanish accounting modules in our company. So far they’ve been meeting our requirements without major issues.
By “they” I guess you are just talking about you.
The problem is that you do not accept the requirement and you keep pushing for your way. So you are the one how have useless discussions.
That’s not true, I completly accept your requeriments but I’ve always comented in several ways:
I see the benefit of your comments and I understand your concerns. But I do not fully that what you request is the best solution for the community so probably this make you think that I do not accept the requirements.
I always try to understand the reasoning behaing your word and try to understand the reasons of your request. You should try to do the same when others have different opinions than yours.
Of course, did you see anyone else trying to maintain the Spanish modules in core? Did you thought why nobody else is trying to contribute? There is a lot more people tryting to contribute to spanish modules, just have a look at the verifactu which is quite new and had been contributed by several people:
So I guess both of you are not using the AEAT nor SII features but only the chart of accounts and the taxes.
You are right. We handle those externally for now, but we are looking forward to integrating them into our Tryton workflow at some point.
Also we’ve just started using the community modules Verifactu and Facturae and we are very happy with them; many thanks to @pokoli for promoting them as they are very useful. We also hope to start contributing to their improvement and maintenance soon.
It’s your opinion, for me in some situations is good to take one step backward to take two forward later.
Indeed right now the situation is really stuck.
Every attempt to incorporate existing external module has failed. The main reason is that once the code exists, the author does not want (or have the resources) to change it during the review process. And also the review process will request smaller/reduced feature first but the author will not want to break it.
So once a module is gone, it is lost for ever.
Because nobody takes care of fixing it and this time I do not take the responsibility nor take from my free time because I have no interest in it nor enough knowledge.
I am not using SII feature but some AEAT reports. I have to fix some of them manually before to present taxes to authorities.
I am using the account_es Tryton standard module.
So if nobody is taking care of the modules I think its better to just remove them and do not give the false feeling that this part of the software is maintained.
Better to have nothing that something broken
Here is one more complain: Non all taxes should be afected by deductible tax rate (#14133) · Issues · Tryton / Tryton · GitLab
What is the objective of such complaint collection? To create a list of complains or to just move the topic forward and provide solutions?
For me after two weeks are on the same point as when we started the discussion.
This is the reason for what I’m said:
Current situation is nothing is moving forward no mather what we do.