openerp-community team mailing list archive

[Bidoul, Stéphane <stephane.bidoul@xxxxxxxxx>]

Hi Fabien,

On Sat, Aug 17, 2013 at 4:03 PM, Fabien Pinckaers <fp@xxxxxxxxxxx> wrote:

> Hi,
>
> Some community modules are incompatible with each other, or with core
> modules. It may not be desirable but it is sometimes unavoidable and is a
> fact today.
>
>
> Do you have some examples of incompatible modules where it's unavoidable?
>

Well... should I be more precise by saying unavoidable *in practice*?

Modules do get published that solve the same or different problem in
conflicting ways. Sometimes the conflict has technical roots, sometimes
it's simply a different view on the best way to solve similar business
problems. Or it can be as simple as having two unrelated modules adding a
field to a core class and giving it the same name. That can be considered a
bug yes, but it can be discovered late, and take a lot of time to fix
properly with migration efforts etc.

Avoiding that would require perfect upfront coordination between all
community and core module authors, not to mention agreement on The Right
Way to solve similar functional issues.... That, or an equally unpractical
dictatorship kind of community governance model :)

So full comptability between all modules existing and to come is definitely
not practically feasible, hence the proposal to help manage the landscape.
Bug tracking can then be used to discuss and follow the efforts to make the
modules compatibles.

Cheers,

-sbi