Community mailing list archives
Re: Reflection about documentation.by
On Tue, Aug 12, 2014 at 11:11 AM, Miguel Acebes <email@example.com> wrote:
@Nhomar have not understood any of my mail. Who released the new versions is OpenERP SA and not the community and should be responsible for making a great documentation.
Be careful, I am not saying Odoo is "inocent" I am saying it is "co-responsable" it is different men.Look, I am using v8.0 since 1.5 years, testing, improving, validating "yes I am programmer" can some functional people invest them job too! ¿? , I think "yes".It is freely available with everysingle commit.
If that means we will all need help there to help. But they have to understand that they can not release the modules undocumented. What means an saas client that can make a website without documentation?Yes they can, and they did ;-) the issue is that the early adopters are not documenting, everybody thing easy.
Odoo must include documentation of the project as part of a new version or module. I'm not inventing the wheel gentlemen, just ask to be at least as good as SAP, ORACLE and MICROSOFT.Well, I think Odoo is better (but other history), I can see the heart of the tool, read the code, and be absolutly sure something is good or not.But yu are right (but not totally) we MUST improve as "community" the OpenSource software we are building.My point is that it is a metter of "co-responsability",Ugly question just to test the retoric:Are you agreed to invest 100k USD in build 4 books and then put them freely availables for community?If you say "yes":- Do it, you have the infomartion available and the community process to acheve that.If you say "no":- Don't worry, work as "community" and put your seed.If you say "May be if Odoo pay me (it is the must frequently given answer)":- Ok, then you are pushing to Odoo SA to close the code, and simple find a way to raise the necessary money to pay you (As the good tools you mentioned before which has built an incorrect model from my PoV)
I think are obvious deficiencies in the documentation, it's not a problem of my knowledge of where the contents.
If we do not recognize areas for improvement never advance.I didn't say "No there are deficiencies" I said "It is a matter of co-responsability", that's all. If you have the knowledge or not I am not in the position of evaluate that, that's a total different point, I only can say, "Where did you look for?" to help you as community to move in the right direction.Regards.