Community mailing list archives

community@mail.odoo.com

Re: odoo store quality

by
Skillteam, Houssine BAKKALI
- 02/22/2016 06:40:56
For now OCA module are on the appstore... So as I said I only take the app store as a search engine...

What I do then? github and google search... Why github? because I can check knowing issues and acknowledge the current PR on the repo on which I have interest..

It take time? Hell yeah it does! Why I do that? because I like to know what I'm selling...

At the launchpad time I was getting all the bug report on my mails... Didn't found a way to do it on github, no way to filter on some categories of event like issues... I've deactivated the following of odoo repo on december 2014 as it was pointless to get all the infos...

But it would be great to have a way to ease that work... As I said I'm afraid we lack of resources here... we have lot of people for saying what we need to do and how to do it but less people for doing it...

To conclude I'll just quote the Nike leitmotiv : "Just do it"

2016-02-22 6:09 GMT+01:00 Andreas Becker <andi@lisandi.com>:
Hi Houssine

An OCA store which would be listing all OCA modules already would help a lot. It could even create some income i.e. by selling advertising space to people who like to provide Odoo Community Edition Services to others. As long as OCA is not standing 100% on their own 2 feet what they already could do since very long time, there will be a lack of people, time and also of potential income.

Let's ask you a simple question:

What are you doing, when a customer has a request of a certain functionality he wants to have in his Odoo Community Site?
  1. Start creating a new module which fits the needs of the customer - how much time this might take?
  2. Do a Google Search, if already a module is existing - how much time this might take?
  3. Get to some Git repositories in the hope to find a module or at least a similar module - how much time this might take?
  4. Go to Oca jumping from Group folder to Group folder to find a module with this functionality - how much time this might take?
  5. Using http://odoo-code-search.com in the hope finding something - how much time this might take?
  6. ... let us know your way!
I guess the best way at all would be to have a list of all existing modules with links to their repositories available and all those modules get grouped in categories and/or with tags to group them i.e. in verticals.

In other words each single module would have its own way to send PRs if you have an enhancement or fix for a certain problem.
I am sure than modules listed in such a way get much faster be converted to Version 9 or later 10 than they are right now listed as uninstallable.
With a simple "gitup -c" - you would immediately see which of those modules got updated and those updates could be listed i.e. in an rss feed. 
This way developers get informed immediately what is available and where they can and perhaps should contribute or help.

This way could even create much more interest in testing out stuff and of course in giving feedback!

-----------

Below you find a list of updates - a short one as it was weekend and many people did not work and south america is still preparing to get to sleep on sunday.

It only tells you that there has been a branch update, but you don't see what actually happened - which means you would need to search by your self on those repositories to find it out. The same way you would need to find out what modules are actually listed in those repositories. Beside that often forks of modules and copies of modules get updated and there developers don't seem to coordinate their efforts and combine them - I guess as a lack of communication and also because they simply don't know that they both started working on the same feature with exactly the same goal.

Last login: Fri Feb 19 10:42:20 2016 
root@vm:/# gitup -c
gitup: the git-repo-updater
//_GIT/ODOO/acsone (6 repos):
    acsone-addons:
        Fetching origin (33/33): new branch (8.0-new-account_invoice_account_analytic_id-jne), new tag (8.0-LIS-1.1.0), branch update (8.0).
        Updating 8.0: done.
    web:
        Fetching origin: new tag (8.0-LIS-1.1.0).
        Updating 8.0-web_timeline-prototype: up to date.
//_GIT/ODOO/buke (4 repos):
    GreenOdoo:
        Fetching origin (656/656, 665/665): branch updates (8.0-win32, 8.0-linux64).
        Updating 8.0-win32: done.
//_GIT/ODOO/codup (5 repos):
    odoo-eam:
        Fetching origin (4/4): branch update (master).
        Updating master: done.
//_GIT/ODOO/compassionCH (4 repos):
    compassion-modules:
        Fetching origin (8/8): branch update (master).
        Updating master: skipped: not possible to fast-forward.
    compassion-switzerland:
        Fetching origin: branch update (8.0).
        Updating master: up to date.
//_GIT/ODOO/equitania (4 repos):
    myodoo-server:
        Fetching origin (286/286): branch updates (develop, develop9.0).
        Updating 8.0: up to date.
    odoo-addons:
        Fetching origin (19/19): branch updates (8.0, develop, master).
        Updating 8.0: done.
//_GIT/ODOO/ingadhoc (9 repos):
    odoo-argentina:
        Fetching origin (9/9): branch update (8.0).
        Updating 8.0: done.
//_GIT/ODOO/JayVora-SerpentCS (6 repos):
    hotelmgmt_v8:
        Fetching origin (266/266, 269/269): branch updates (8.0, 9.0).
        Updating 8.0: done.
//_GIT/ODOO/microcom (1 repo):
    Odoo_Basic_AddOns:
        Fetching origin (10/10): branch update (8.0).
        Updating 8.0: done.
//_GIT/ODOO/OCA (123 repos):
    OCB:
        Fetching origin (621/621, 902/902): branch updates (9.0, 8.0).
        Updating 9.0: done.
    account-financial-tools:
        Fetching origin: branch updates (7.0, 8.0).
        Updating 9.0: up to date.
    account-fiscal-rule:
        Fetching origin: branch update (8.0).
        Updating 9.0: up to date.
    account-invoice-reporting:
        Fetching origin (17/17): branch update (8.0).
        Updating 9.0: up to date.
    connector-telephony:
        Fetching origin (8/8): branch update (8.0).
        Updating 9.0: up to date.
    connector-woocommerce:
        Fetching origin (1/1): branch update (9.0).
        Updating 9.0: done.
    geospatial:
        Fetching origin: branch update (9.0).
        Updating 9.0: done.
    l10n-brazil:
        Fetching origin (5/5): branch update (8.0).
        Updating 9.0: up to date.
    l10n-italy:
        Fetching origin: branch updates (9.0, 8.0).
        Updating 9.0: done.
    l10n-spain:
        Fetching origin (47/47): branch update (8.0).
        Updating 9.0: up to date.
    maintainer-quality-tools:
        Fetching origin: branch update (master).
        Updating master: done.
    maintainer-tools:
        Fetching origin (6/6): branch update (master).
        Updating master: done.
    management-system:
        Fetching origin (14/14): branch updates (9.0, 8.0).
        Updating 9.0: done.
    manufacture:
        Fetching origin: branch updates (9.0, 8.0).
        Updating 9.0: done.
    partner-contact:
        Fetching origin (6/6): branch update (8.0).
        Updating 9.0: up to date.
    project:
        Fetching origin (37/37, 113/113): branch updates (9.0, 8.0).
        Updating 9.0: done.
    reporting-engine:
        Fetching origin: branch updates (9.0, 8.0).
        Updating 9.0: done.
    server-tools:
        Fetching origin (58/58): branch updates (9.0, 8.0).
        Updating 9.0: done.
    stock-logistics-barcode:
        Fetching origin: branch update (8.0).
        Updating 9.0: up to date.
    stock-logistics-workflow:
        Fetching origin (35/35): branch update (8.0).
        Updating 9.0: up to date.
   vertical-medical:
        Fetching origin (6/6): branch update (8.0).
        Updating 9.0: up to date.
    web:
        Fetching origin: branch update (8.0).
        Updating 9.0: up to date.
//_GIT/ODOO/odoomrp (3 repos):
    odoomrp-utils:
        Fetching origin (8/8): branch update (8.0).
        Updating 8.0: done.
    odoomrp-wip:
        Fetching origin (28/28): branch update (8.0).
        Updating 8.0: done.
//_GIT/ODOO/OpenAT (1 repo):
    cu_hofe:
        Fetching origin: branch update (master).
        Updating master: done.
//_GIT/ODOO/openjaf (1 repo):
    openerp_travel:
        Fetching origin (13/13): branch updates (master, develop).
        Updating master: skipped: not possible to fast-forward.
//_GIT/ODOO/therp (1 repo):
    Therp-Addons:
        Fetching origin (2/2): branch update (7.0).
        Updating 8.0: up to date.
//_GIT/ODOO/thinkopensolutions (1 repo):
    tkobr-addons:
        Fetching origin: branch updates (8.0, imp/discount_cards_company_m2m).
        Updating 8.0: done.
//_GIT/ODOO/thitithub (1 repo):
    ineco_addons:
        Fetching origin: up to date.
        Updating 8.0: up to date.
//_GIT/ODOO/Trust-Code (2 repos):
    trust-addons:
        Fetching origin: branch update (8.0).
        Updating 8.0: done.
    trust-themes:
        Fetching origin: branch update (master).
        Updating master: done.
//_GIT/ODOO/version9 (11 repos):
    access-addons:
        Fetching origin: branch update (9.0).
        Updating 9.0: done.
    addons-yelizariev:
        Fetching origin (116/116): branch update (9.0).
        Updating 9.0: done.
     odoo-saas-tools:
        Fetching origin (17/17): branch update (9.0).
        Updating 9.0: done.
    pos-addons:
        Fetching origin (270/270): branch update (9.0).
        Updating 9.0: done.
//_GIT/ODOO/vertelab (37 repos):
    odoo-account-extra:
        Fetching origin: branch update (master).
        Updating master: done.
    odoo-stock-extra:
        Fetching origin: branch update (master).
        Updating master: done.
    odoo-website-sale-extra:
        Fetching origin: branch update (master).
        Updating master: done.
//_GIT/ODOO/yelizariev (5 repos):
    access-addons:
        Fetching origin: branch updates (9.0, 8.0).
        Updating 9.0: done.
    addons-yelizariev:
        Fetching origin (51/51, 117/117): branch update (9.0).
        Updating 9.0: done.
    odoo-saas-tools:
        Fetching origin (13/13): branch update (9.0).
        Updating 9.0: done.
    pos-addons:
        Fetching origin (91/91, 270/270): branch update (9.0).
        Updating 9.0: done.
root@vm:/# 

--------

Now if you would have an exact list of all updates which have been made in those branches, than it would very easy to read it and developers would simply know what is actually going on and what is actually existing already. They could much better coordinate and nourish the Odoo Community Univers with their ideas instead of probably creating just another module which is nothing more than reinventing already existing wheels.

The actual list of repositories checked until now is much much longer - all not updated repositories have been stripped out!

Currently it only holds Version 9 repositories and where a Version 9 repository is not existing our students integrated it in the list of repositories if the modules the repository is holing has a certain value also for version 9.

----

But as you can see - take as example the OCA branches! - you won't see what has actually been done in what certain module!

This means you would need to get to the OCA repository - or any other one listed above.

i.e.

Here you would see that 4 and 6 days ago something happened.

and immediately you would know that this module is now available for version 9.

as comparison take on of those oca-verticals:

and you will know that project_task_default_stage is now available for Version 9
but often you need to search in those verticals long time to see those actual changes and see if a module is available or would need some support etc.

========

Andi







With kind regards,
Mit freundlichen Grüßen,
Con un cordial saludo,
Cordialement,
с сердечным приветом,
เรื่องที่เกี่ยวกับชนิด,
與親切的問候,

 ANDI BECKER

CEO/General Manager LisAndi Co., Ltd.

--------------------------------------------------

LisAndi Co. Ltd., Phuket, Thailand (lisandi.com)
15/21 M.2 Viset Road, Rawai, Muang, Phuket, Thailand 83130

VoIP:   +49 (0)711 50 88788 50
Fax:     +49 (0)711 50 88788 50
Skype:          lisandi
Facebook:     andibecker
Google Talk/Facetime/eMail:  andi@lisandi.com

--------------------------------------------------


On Sun, Feb 21, 2016 at 5:08 PM, Houssine BAKKALI <houssine.bakkali@gmail.com> wrote:
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.

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.

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 ;)



2016-02-21 7:42 GMT+01:00 Andreas Becker <andi@lisandi.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

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe