Community mailing list archives
Re: Reflection about documentation.by
@Eric, good point, I was enchanted at first.
But I realized, that this aproach will be proned to fail. Thes statistics, that Fabien presented some time ago are not representing the percieved truth, as good as the basic idea might have been. Honours to the idea: I think this is a good approach for providing answers if you are in your *second or third* round of the hermeneutic cycle of learning.
If you start, however, (and that's the customer perspective, Miguel braught into the discussion), you need guidance, and guidance means structure. Therefore the documentation fundament must be built close to the core (github/rst/sphinx), community enabled (easy editing), up to date and well structured (first from a customer perspective, second from developer perspective sic! - because in this order we have compatibility, the other way round, we don't) and cover probably 70% of the topics with a focus on what an informed customer want's to know. (customer, sic!)
2014-08-12 21:48 GMT-05:00 Eric Caudal <firstname.lastname@example.org>:
Thanks David for the summary!<blockquote cite="mid:CAF111mXAm1NcGhyjhMMfkiAOj-N7Mt8OguydjfixDGxCLn0CvA@mail.gmail.com" type="cite">
Please note that according to the last presentation I have seen from Olivier Dony (opendays 2014:http://www.slideshare.net/openobject/the-new-odoo-community-organization-and-platform), the idea was for the community to provide Answers to the help center and based on the quality of the answers/contributor (gamification here we go), some would become standard "how-to".
I understand and see the value of the idea but I miss from Odoo SA (or point me to the resource if I missed it...):
- more communication on the subject
- Simple rules to contribute (layout, guidelines)
- Mentors/organization/coordinatorOn 08/13/2014 10:33 AM, email@example.com wrote:Eric Caudal OCA Board MemberFew 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 FranceSome 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!Regards, David