Community mailing list archives
Re: Reflection about documentation.by
David Arnold BA HSG / Gerente
315 304 13 68/ david²elaleman.co
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.
> In this point, is good have all methods on the orm documented (it is a > layer) and the external is the "how to helper guide", right? > > IMHO a PR to the core fixing doc desn't bring too much problem, but I > think all the api's: > > openerp/ > web/ > mail/ > website/ > > __must__ be related to the code. The problem is that it's a huge overhead to do a pull request just to fix a typo. It has to be super easy for documentation writers to contribute. We need to support the "Edit in Github" button. -- Fabien Pinckaers Odoo Founder Phone: +220.127.116.11.00 Web: https://www.odoo.com Twitter: @fpodoo Instant Demo: https://odoo.com/start