Contributors mailing list archives

contributors@odoo-community.org

Re: The future of OCB

by
Narayana Moturi
- 08/10/2016 10:15:15
Mike - For distributed Odoo you can investigate to use containerised micro services

On Sat, Oct 8, 2016 at 8:22 PM, Michael Telahun <miket@clearict.com> wrote:
Although I agree with the general sentiment that Odoo has made major
strides in stability in the latest versions I'm pretty sure there will
still be a few fixes that the community wants that Odoo S.A. will not
(for whatever reason) accept. So, even if for the moment it ends up
being an exact copy of Odoo I am in favour of keeping OCB (I assuming it
does not take up too many resources).

However, I also like the idea of another branch in which the community
can tackle more audacious ideas while still maintaining compatibility
with Odoo. Some of my ideas:

1. Distributed Odoo
I would like to see a more loosely-coupled Odoo. For example, I might
want to run the financial module on a separate server from the other
modules, but still have sales, POS, warehouse modules interact with the
financial modules seamlessly.
Another example is the projectexpert-pmis modules. I would like to setup
separate project databases for our clients which exclusively runs the
projectexpert-pmis modules only. But I want to still be able to connect
it with the Odoo database we use for our own business for things like
billing, etc.
We are currently in talks with a large agro-business with multiple farm
sites about implementing an Agricultural Management System. We want to
install the AMS at each farm but the other modules (like finance,
warehousing, etc) should be installed at the HQ.

2. I would like to see the redis session store become a core addon

3. We are currently using connector queues to parallelize some large
workloads, which has led us to experiment with various concurrent
locking mechanisms (beyond what the db provides). I would eventually
like to see this land in the OCA repos either as a core functionality of
this new branch or in one of the other repos.

4. I would like to see multi-database functionality in Odoo. For
example, this could come in handy for routing long-running BI queries to
a replicated read-only database.

So, as you can see I am currently focused on distributed systems, but
other people will have other itches they need scratched that the OCA
community would greatly benefit from if we had a central repo that we
could merge such features into and collaboratively maintain as a
community. In the end such features would benefit everybody, including
Odoo S.A.

Regards,
Mike.

On Fri, 2016-10-07 at 23:08 +0000, Stefan Rijnhart wrote:
> Thank you, Houssine. Your clarification is very much along the lines
> of what I had in mind, rather than choosing a diverging path from Odoo
> at this point.
> 
> 
> 
> 
> On October 7, 2016 2:53:18 PM GMT+02:00, Houssine BAKKALI
> <houssine.bakkali@gmail.com> wrote:
>         I think that some of you are mislead.
>         
>         
>         The point of having an OCX branch instead of OCB is too free
>         the resources that was maintening the OCB for this new project
>         that if if it's technicallay a fork has not this purpose.
>         
>         
>         The aim is to have a branch depending on the Odoo version on
>         which the enhancing PRs would be merged as it was done for
>         OCB. This looks more like a OCE(Odoo Community Edition) that
>         allows the community to make use of monkey addons patch due to
>         the core limitation.
>         
>         
>         This could also be a playground for more experimental things
>         on the framework, the webiste or in the web ui. 
>         
>         
>         
>         OCA needs Odoo and Odoo needs OCA, in top of that OCA alreadt
>         lacks contributors for code review so it's a bit unrealistic
>         to think about a full maintained Odoo detached from the head.
>         
>         
>         I like the idea of Stefan so let's begin with is not so simple
>         idea and see what happen!
>         
>         
>         2016-10-07 14:23 GMT+02:00 Michael Delvoye
>         <mdelvoye@misyl-services.com>:
>                 Hi
>                 I think like jean Sebastien 
>                 Maybe oca needs to become an Erp free and not
>                 depending on Odoo versions
>                 
>                 
>                 
>                 
>                 Michael Delvoye 
>                 
>                 Le 7 oct. 2016 à 11:08, Jean Sébastien HEDERER
>                 ASPerience <hedererjs@asperience.fr> a écrit :
>                 
>                 
>                 > Hi all,
>                 > 
>                 > I'd like to say that if most OCA members want to cut
>                 > links between "Odoo official core" and "Odoo OCA
>                 > core" in order to create a new way for all, I'm
>                 > interested in participating. I do not participate
>                 > for the moment because I see no value to run after
>                 > Odoo SA versions from year to year, porting modules
>                 > version after version, keeping some, letting others
>                 > unported because of lack of time. If OCA wants to
>                 > create value, it can only be with a stable core
>                 > version on which we will be able to add enterprise
>                 > functionalities, not shareholders functionalities.
>                 > 
>                 >  
>                 > 
>                 > ----------------message d'origine-----------------
>                 > De: Stefan Rijnhart [stefan@opener.amsterdam]
>                 > A: Contributors [contributors@odoo-community.org]
>                 > Date: Tue, 04 Oct 2016 14:09:01 -0000
>                 > ----------------------------------------------------------
>                 > >   
>                 > > Dear OCA collaborators,
>                 > > 
>                 > > as a follow up to the lightning talk at the OCA codesprint today, let me
>                 > > expand on my ideas.
>                 > > 
>                 > > The OCB project (https://github.com/oca/ocb) was created in a time when
>                 > > Odoo itself was a lot more unstable and many core bug fixes needed to be
>                 > > included in a production instance. It was a feast to collaborate with
>                 > > the OCA community to share the effort and enjoy the benefit of each
>                 > > other's fixes. Nowadays, there is a lot less interest in the project.
>                 > > Not a lot of PRs are proposed, mainly I feel because Odoo itself is a
>                 > > lot more stable, and smaller changes from the community are adopted more
>                 > > quickly in the core project. Meanwhile on OCB, not a lot of reviews are
>                 > > being posted either and some of the PRs that are still being proposed
>                 > > are not valid against the policy of stability, as they would create
>                 > > incompatibilities with Odoo (defined as: does a change allow the
>                 > > creation of community modules that are compatible with OCB but not with
>                 > > Odoo or the other way around).
>                 > > 
>                 > > It thus seems that the OCB project outlived its usefulness. My
>                 > > suggestion would be to freeze the OCB project: no branch for 10 will be
>                 > > created, and no more merges will take place on the existing branches. We
>                 > > can still keep merging the upstream changes to the existing branches as
>                 > > a form of limited support.
>                 > > 
>                 > > This would free up some resources for a replacement project. I would be
>                 > > very interested for the OCA to host a version of Odoo that does allow
>                 > > for more radical changes to the Odoo core. Currently, the ideas in the
>                 > > community on what could be improved in the Odoo core just get lost,
>                 > > because Odoo SA is not very open to them, and neither is OCB. I would
>                 > > like to see what the community members come up with, and see if this
>                 > > leads to a more vibrant project. Some restrictions would still apply of
>                 > > course. If an improvement could be made in a separate addon, there would
>                 > > be no reason to include it in the project.
>                 > > 
>                 > > As a part of the project, we would have to think about managing
>                 > > dependencies, as it might be the case that community modules are created
>                 > > that are only compatible with this new version (or worse, when
>                 > > incompatibilities are introduced that break additional modules). We
>                 > > would also have to think about clearly documenting the changes and
>                 > > providing an upgrade path to later versions of the project.
>                 > > 
>                 > > Please share your thoughts on the topic.
>                 > > 
>                 > > Regards,
>                 > > Stefan
>                 > > 
>                 > > -- 
>                 > > Opener B.V. - Business solutions driven by open source collaboration
>                 > > 
>                 > > Stefan Rijnhart - Consultant/developer
>                 > > 
>                 > > mail: stefan@opener.am
> > > tel: +31 (0) 20 3090 139 web: https://opener.am > > > _______________________________________________ > > > 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 > > > > > > _______________________________________________ > 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