Community mailing list archives
RE: Reflection about documentation.by
Thanks @david, I see the issue I have suggested has had an interest in the community, which shows that something is failing with the documentation. Unfortunately not yet posted any comment Openerp SA.
When someone, whether potential customer (prospect) or developer begins to enter the world Odoo first thing you need is to deepen the more information and additional documentation needed.
If a potential client or potential new developer does not find it or need a long time to find the dropout rate for continuing interest in Odoo as product shoots.
OpenERP seems that recently has made some funds put 10 M € on the table. Well, if they are to be used in marketing, please take into account my previous paragraph, good and complete documentation attracts customers, partners and developers in bulk. The other key factor is that is what is sought so agile and quick. Documentation must be structured and easily accessible.
A support forum is fine, but from my point of view is complementary and adds value, but can not replace a quality documentation.
Finally I would like to know what OpenERP SA have to say before we organize to make viable structured and quality documentation covering all functional and technical aspects.
Thank you all for your contributions.
De: email@example.com [mailto:firstname.lastname@example.org]
Enviado el: miércoles, 13 de agosto de 2014 4:33
Asunto: Re: Reflection about documentation.
Few want to read all this discussion, it has got somewhat diluted. But it is of utmost relevance and importance. So I bother to give a resume for you:
Basically we have three (non contradictory) opinion tendencies:
- Odoo has almost grown up, it will become a serious player in the market. Quality root/english is a prerequisite for future growth. It empowers the whole ecosystem, generates dynamic and is a big argument to "more serious" customers and "more serious" implementation partners. How we can fix that?
- Odoo has had a strategy of knowledge retention as part of their revenue model in the past. This explains priorities, which in turn perfectly explain the status quo.
- Responsibility is seen within the community, based in honest principles of reciprocity. This, as being political/opinionated notion, explains part of the heat of this discussion.
Somone (Kurt) already made a link to reconcile all this three opinion tendencies - distilling the basic questions:
How can we transform? How can we achieve the next steps in the odoo ecosystem? How much more do we need to professionalize for the "more serious" customer? He's raising the annoyance of a partial "head-in-the-sand attitude" within the ecosystem - Here: In relation to the documentation.
Furthermore some community "fundamentalists" :) came up with some loosly coordineted "call for action" suggestions:
- Make Student project and engage 20 Students in setting up a documentation based on existing peaces (remarkable suggestion!)
- Move doc.odoo.com to odoo.rtfd.org for better accessibility/ease of use and "dynamic"
- Help with translation from Germany and France
Some additional relevant information has been dropped:
- Odoo plans: Transifex (still not confirmed) as translation tool, gengo as transaltion service. This makes transaltion a secundary issue.
- Odoo has plans to integrate walk-throughs inplace within the UI. (you might have a look: http://qf6iua.axshare.com/#p=sales)
- There are functional books still residing in the launchpad archive. Some might fear them to become "lost in translation" (to github)
- OCA (Odoo Community Assotiation - the organized part of the community) has plans to adress this topic for its own "organized" projects (who's interested should probably contact Eric Caudal !)
I honorour of it's creator, I want cite the author of this thread, Miguel Acebes, who asks OpenERP SA for an opinion on this topic:
"I would like OpenERP opine that what we are discussing. I think it's important to know your position."
Hope this helps you get back on top of this very valuable discussion!