El 20/03/18 a les 22:37, Cédric Krier ha escrit: > On 2018-03-20 21:42, Raimon Esteve wrote: >> El dia 20 març 2018 5:10 p. m., "Cédric Krier" <cedric.kr...@b2ck.com> va >> escriure: >> In the last release 4.6, we included a module for the Spanish >> accounting. But it showed that there was many issues with its design: >> https://bugs.tryton.org/issue7150 >> >> Currently, I'm envisaging to remove it from the standard modules (hide >> the only release on PyPI) and move it to the sandbox repositories until >> a proper design is found. >> This way, we will be able to break migration path for it and restart it >> with a good basis. >> >> >> Not LGTM > > I'm not asking for permission here. I'm just warning about the situation > and the ending if nothing changes. > >> You can't simplicy account_es module because an account user need all >> information about taxes and accounts.
We can simplify the account_es and let the user manually create extra account/taxes if they use it. We already do it for accounts. For taxes the spanish comunity always tried to get all the taxes on the chart of account module but this results with having more taxes unused that the ones that the user really needs. And for me this is wrong as it only causes confusion. > >> Trytonspain modules, have extra features (recargo equivalència, >> deducible, SII, etc) > > What are those features? The account_es already contains the recargo de equivalencia taxes definition. Indeed a new feature was introduced on tryton to support this case. [1] The SII is a separate functionality out of the scope of the chart of accounts. For those curious SII is a webservice which is used to send the invoices (with taxes) information to tax authority. This is only required for companies above a revenue threshold (4M€ IIRC). Raimon: Could you explain what do you mean about deducible and which functionalities are implemented? >> Sincerently, I prefer continue to working account_es from trytonspain and >> mark deprecated account_es core module. > It's a pity to read those words. I can understand that people thinks it's easier to stay on their comfort zone. But for sure it's better to move outside of it and improve tryton. > This is very sad to see such non-collaborative behaviour. > Most of the issues you fill have no explanation. So it is not possible > to judge the correctness. And most of them end with unasked questions. Just to have it clear: I will be happy to help resolving the issues but I can not do it without understanding the problem. Sometimes I think it's a communication problem (due to language or written expression, not sure). I'm open to other communication methods if this will help to resolve the issues. > > > PS: this is again a perfect example that modules created outside Tryton > process have all the pain to come back in standard. > I hope others will learn from the pain we are suffering here. This topic is worth a talk on the next unconference :) [1] https://discuss.tryton.org/t/preserve-original-tax-when-appling-tax-rules/397/12 -- Sergi Almacellas Abellana www.koolpi.com Twitter: @pokoli_srk -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/7ab11a9d-0c79-2830-3d4d-8754fd5f6a25%40koolpi.com.
