Community mailing list archives

Re: Technical documentation state - could someone at odoo take care of it ?

David Arnold
- 08/21/2014 16:20:24


I hope one day we will get the insight that we should tear down organisational/ecosystem silos of dividing knowledge into functional and technical.
Semi-off topic end.

There has been a very long discussion about both in another thread with some state of specificity and also quite concrete proposals from Odoo. I think we should keep this discussion alive there until we have a solution.
Regards, David

Am Donnerstag, 21. August 2014 schrieb Christophe Hanon :
Could somebody from Odoo have a look at the tech documentation on the odoo website?

Technical memento link goes to nowhere or at best an old Peugeot model.
Documentation for 7 goes to trunk - nearly empty.
Old documentation, I fear content is lost for example
- well there is not a single method listed there.

I hope this will be fixed soon. I know functional doc is an eternal discussion, but the framework documentation should be accurate, exhaustive and available since long time.



Christophe Hanon - ADINS

Post to:


El Alemán S.A.S

David Arnold BA HSG / Gerente
315 304 13 68/ david²

El Alemán S.A.S Office: +57 (1) 651 3766 / Fax: +57 (1) 651 3772 
CRA 13 93 40 P4, Bogotá, Colombia


This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. El Aleman S.A.S is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.