Community Mailinglisten Archive
Re: odoo store qualitydurch
For the actual committement we lack of resources. It means we, the community, needs more reviewers and testers(people that test the PR on runbot). Keep in mind that it's not easy to find an good balance between the ongoing projects and deadlines for customer(we have to make a living) and the contribution to OCA and answer to very long mails from you, in fact even just reading them take quiet a long time ;)
It's easy to push any module to one of the OCA repo through pull request, it's another thing to comply with code quality, standard, implementing tests, taken reviews under account about the functionnality or the way it has been implemented. So this cost quiet lot of time from people that review the PR and for the people that have to modify their code.
Andreas,This is not the purpose of the OCA. Organizing the work to have an OCA umbrella under which modules can be proposed is one of the service that propose OCA in a benevolent way and with the limited resources, read contributors, they have.
2016-02-21 7:42 GMT+01:00 Andreas Becker <email@example.com>:
Probably best would be a OCA Store which lists all those modules in a much cleaner way.To Houssine:You are on the one hand right as many market places or repositories look like a mass. The TYPO3 repository had the same problem and since 2008 it got cleaner and cleaner and meanwhile all modules which are no more working in the current stable version get filtered out by default, there are also now much more enforced rules which help to keep the repository clean.A much much bigger problem actually with the Odoo S.A. Store is that it lists not seldom modules which are not even installable in the version they mention. Some companies and developers seem to use the Odoo S.A. store only to promote and represent as a company who does a lot of modules no matter what they actually do.Many of those modules listed in the store still don't provide links to repositories to check the code quality before buying.A general problem we figured out with both OCA and ODOO is that there isn't at all a centralized place where all module information gets gathered.With our students we analyze the Odoo Univers since several months now and still we don't see an end as every day we find new repositories somewhere else. Therefor it would be great to have a centralized place - which could be OCA - which gathers all those new developments.We experimented with several solutions and currently are using the gitup repository updater to see what is going on.Unfortunately one problem is here, that often many modules get gathered in a group together with many other modules. This makes it very difficult to see changes of a certain module immediately.Perhaps there are better solutions to keep track of changes in the Odoo Univers and it would be nice to learn about them!Much more helpful would be if each single module would be listed separately. This way you would immediately see what has been modified, created, added, deleted etc.. Also updating Odoo installations could be made much easier with that approach.Another even bigger problem is actually the fact that most OCA modules have been set to uninstallable. Now all those appear in those lists even only some small text changes have been made to them and the module itself is still uninstallable.Andi