1. Mailing Lists
  2. Contributors
  3. Re: OCA Growing Pains

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: OCA Growing Pains

Re: OCA Growing Pains

Avatar

Re: OCA Growing Pains

by
Vauxoo, Moisés López Calderón
- 06/12/2016 03:42:33
Today I saw a PR by Luis Felipe Mileo:
https://github.com/OCA/maintainer-quality-tools/pull/395

This generate a standard documentation and github page with projects indexed by modules.

It's a Work In Progress feature but I think that could help us for this focus.


2016-12-05 20:37 GMT-06:00 David Lasley <dave@dlasley.net>:
Odoo App Store answer just that, when filtered by the OCA author?

Yeah realistically that’s all we need. Not sure why I didn’t think of that

We could add that link to the website.

This may have helped me think of that. Knowing me, I doubt it, but at least there would be no excuse =P

They should have a clear scope statement

+1 this is a must IMO. Right now part of the problem is that it is left up to our interpretation of what the repo is for, which could be skewed by not knowing that other repos exist. Probably not much of an issue for you that have been around for a while, but I’m still finding new repos on a consistent basis.

and have pointers for the other repos that usually complement them.

This would be freaking awesome, but it also seems like kind of a maintenance issue - those ReadMe’s aren’t updated very often in non-automated manor. I’m not sure of a solution on that though, outside of the PSCs maintaining them at some point.

— Dave Lasley

On Dec 5, 2016, at 12:22 PM, Daniel Reis <dgreis@sapo.pt> wrote:

Dave, doesn't the Odoo App Store answer just that, when filtered by the OCA author?
We could add that link to the website.

Regarding what module goes where, we could do more on the repo READMEs:
They should have a clear scope statement, and have pointers for the other repos that usually complement them.

--dr 

No dia 05/12/2016, às 19:37, David Lasley <dave@dlasley.net> escreveu:

Yeah I think that’s a good mix, Pedro. This odoo-code-search is almost perfect, and I’m glad to have learned about it just now. 

The problem I see though is that it is also bringing in code from forks. The advantages to that are are tremendous, but it also makes it hard to differentiate OCA supported code from incubator. 

— Dave Lasley

On Dec 5, 2016, at 11:23 AM, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

My perfect mix is the code of odoo-code-search integrated on OCA website with GitHub connector that auto-register all the repositories from OCA organization.

Regards.

2016-12-05 20:07 GMT+01:00 Jean-Marc Vandel <jmv@open-net.ch>:
+1 for odoo-code-search

De: "Maxime Chambreuil" <mchambreuil@ursainfosystems.com>
À: "Contributors" <contributors@odoo-community.org>
Envoyé: Lundi 5 Décembre 2016 19:53:01
Objet: Re: OCA Growing Pains

May http://www.odoo-code-search.com fit that purpose?

Ursa Information Systems Maxime Chambreuil
Project Manager / Consultant

Ursa Information Systems
1450 W Guadalupe Road, Suite 132
Gilbert, Arizona, 85233

Office:     1-855-URSA ERP x 710
                1-855-877 2377 x 710
Mobile:   1-602-427-5632

On Mon, Dec 5, 2016 at 12:37 PM, David Lasley <dave@dlasley.net> wrote:

Hi All,


In a different thread, some concerns were raised regarding the amount of modules under OCA umbrella and the fact that it is hard to keep them all straight. I echo these concerns.

I think one of the main issues is that as we start creating more repos, it becomes harder and harder to remember where modules are & should go. This issue stems from a lack of a central index for referencing OCA modules, so we will find ourselves having to go through multiple repos that could possibly match what we are looking for. This issue is exponential, and could detract new contributors due to perceived dependency complexity.

I propose that we create a Module Index in the Resources section of the Odoo Community website. It will provide a listing of the modules available by Name and Summary. It will also allow for some basic searching.

We can fill this data with our pre-existing Github connector using the ReadMe & manifest data. I will look into the changes required from a code perspective to support this, but I don’t feel like this will be difficult. Odoo already includes everything necessary, it’s just a matter of plugging the data into the interface & catching the output.

Anyone have any thoughts on this? Particularly from the Odoo Community website perspective, that’s somewhat of a black box to me in terms of architecture TBH.

— Dave Lasley

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--
  Avec mes plus sincères salutations,


                                              Jean-Marc Vandel
                                              CTO - Ing. info. dipl. EPFL


Open Net Sàrl
Rue de l'Industrie 59
CH-1030 Bussigny

www.open-net.ch
+41 79 212.65.94
jmv@open-net.ch

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe



<smime.p7s>

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--
Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
web: http://www.vauxoo.com
twitter: @vauxoo
           @moylop260           

Reference