Community mailing list archives
Re: Odoo: Understand Culture & Managementby
There seems to be missing a chapter that explains why it is bad to answer questions or cooperating with the community when shaping core or future of odoo.Sorry, I don't get your point?We try to share a maximum (although we can certainly do more) and explain things we do. As an example, yesterday, we had a partner meeting with partners to discuss about the strategy, roadmap, business, etc. (you should have participated by the way)Can you send me example of issues you have had in private: email@example.com?
And when you add this chapter it might include explanations why odoo should avoid to train and educate the developer "out there" on a constant base and why it is evil to give the the impression that they are an important and respected part of odoo.List of projects we do to train and educate:- A lot of documentation (both developer and functional) (*)- We often share documents on any topic (business, competitors, features, etc.): http://odoo.com/slides- We organize free webinars every week. (some for partners, others are public): https://odoo.com/events- When launching big features, we do a tour worldwide in >10 cities, e.g.: https://t.co/QZncTlWVUP- Partners get a free access to the sales academy in Belgium (one week full training)- In addition to regular events/meetups, once a year, we do 180 free conferences during Odoo Experience- We help new visitors through the live chat on our website- We have setup great community tools: mailing lists, forum, transifex, ...- We wrote a New API to ease developers on boarding and experienceFor sure, we can do more. But I don't understand why you have the feeling that we try to not educate people. We actually try very hard to educate and inform developers and users; But Odoo is huge and evolving very quickly, so it's not easy. So, for sure, we can probably do more.(*) yesterday we improved the global navigation of the documentations, check on the website: https://www.odoo.com/documentation