1. Mailing Lists
  2. Contributors
  3. Re: The future of OCB

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: The future of OCB

Re: The future of OCB

Avatar

Re: The future of OCB

by
ForgeFlow, S.L., Jordi Ballester Alomar
- 10/10/2016 19:44:41
Hi!

May I ask, OCX is to be an integration of PR's that "power up" odoo in some sense, or allow for experimentation, wouldn't it make more sense to maintain a separate OCX branch per experiment?

That way is clearer for all that OCX is not a fork of Odoo. For example: 

  • OCX-DOCS: Power up of Odoo with extended document management
  • OCX-IMPORT: Power up of Odoo to allow faster import
If you think about it, OpenUpgrade IS a fork of Odoo, that has been modified to a point that assists in the migration of the database across versions.

For the same purpose, specific repos could be created inside OCA-DEV, linked to the specific experimentation taking place.

Regards,
Jordi.




On Mon, Oct 10, 2016 at 6:53 PM, Sebastien Beau <sebastien.beau@akretion.com> wrote:
Ok for me too

2016-10-10 13:53 GMT+02:00 Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com>:
OK, let's try that way and see how this evolves.

Regards.

2016-10-10 13:37 GMT+02:00 Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>:
Hi there,


May be we should start with the OCX branch in OCA-dev team first and create the repo only when needed ? I mean, it is not mandatory to replicate everything after a second though...

My question is: Are you agree on the principle (having another OCA-dev team, allow OCX there, communicate on the purpose of this branch (not a fork, but for innovation), ... ?

Regards,

Joël




On Mon, Oct 10, 2016 at 12:53 PM, Nhomar Hernandez <nhomar@vauxoo.com> wrote:

On Mon, Oct 10, 2016 at 3:53 AM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

We currently are barely keeping the head out of water... Let's make sure about the priorities


Hello.

I think we should left that as it is, because we are already facing a huge overhead in the maintainance of thing, and let's thin of a proper way to manage a secdn branch.

Even inside my team I trust only in one editor have a new set of not well maintained OCX repository can bring an incorrect starting point for some people.

In the meanwhile we can continue managing our own copy of branches with eternal PR opened to OCB just to say "This is my branch and I did this and this improvements (with proper commit messags)".

Regards.


--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

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




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager


_______________________________________________
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


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




--
Jordi Ballester Alomar
CEO & Founder | Eficent

Reference