Community mailing list archives
Re: Reflection about documentation.by
Let us eat our own dog food!
David, set yourself a project with tasks, those you have quite well identified, in a free account of odoo,
Create each item from the topics and you as a leader assign yourself a task and begin with it, complete it, deliver code/docs and prompt to people to do so in kanban view.
So people will chat less a deliver more.
This discussion has faded away. IMO despite the fact, that the topic has been identified and accepted on all sides, it should not...Fabien, maybe you could lead to transform the positive tension we have created jointly into concrete action? Or someone from your team would be able of doing so?The offers/ideas have been:- Student Project with 20 Students- High-Level Table of Content for a central point of contact: odoo.rtfd.org - sadly the pad has gone somehow... (maybe because of the switch to v8? - well dosn't matter here)- Reallocation of the existing material- Contact / Contract Greg Moss for a compendium towards more traditional potential market (maybe crowdfunded, as this is probably the core busniess of implementation partners > indigogo-campaign?)I think also Community was able to give some feedback on tools and strategy of Odoo Documentation which I hope was useful.Let's bring this to it's final rest!Saludos CordialesDavid Arnold
David Arnold BA HSG / Analista
315 304 13 68/ firstname.lastname@example.org
devCO - empresa de consultoría de sistemas (en fundación)
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. devCO 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.2014-08-18 22:22 GMT-05:00 <email@example.com>:Oops, the pad his gone... well, at least somthing has been saved here: odoo.rtfd.orgI think a section for developers should have the name "Reference: Developers" and have the character of a reference rather than a "tutorial". One thing I think is key from a developer perspective is to tell the developer in a structured manner the suggested way to do things (programming patterns / best practices), as I see that even practices within the core diverge sometimes and this is probably one root cause of exponential maintainability costs, and finally buggyness and regressions in this ever more complex software project. So externals AND internals would benefit. Nothing to do directly with customers, but a cleaner codebase enables stability, which directly affects the value proposition over more established competitors.2014-08-16 16:12 GMT-05:00 <firstname.lastname@example.org>:addendum: my calculus is, if we get the stream of affluence to the ecosystem right, this might result in more knowledge assets (and pressure), which in turn might help Fabien argue for a product excellency strategy (not the so often mentioned "excellent is the enemy of the good, we want to be good" - or I think , this is what you called "head-in-the-sand" attitude). But it seems to me that Odoo needs (more of) that "reaching for excellency" notion in order to give it's business model the last twist. Also in the fundamentals. It must move forward to Silicon Vally or Berlin (Rocket Internet) standards of dynamic.