Deprecate base_contact and split it in other modules about partner-contact HOT 10 CLOSED

I agree, but prefer to prepend partner_ to all modules

from partner-contact.

No problem. Do you mean for instance partner_contact_birthdate or partner_birthdate?

from partner-contact.

It seems to be more coherent to name them partner_contact_base, partner_contact_birthdate...

from partner-contact.

👍

from partner-contact.

IMO a contact being a partner I don't see the need of adding partner_ to all module technical names

And indeed a split of functionalities would be better.

from partner-contact.

Then please come to a consensus. For now I've started with @pedrobaeza suggestion. You can track progress if you want in https://github.com/grupoesoc/partner-contact/tree/deprecate-base_contact.

from partner-contact.

@yvaucher, partner prefix identify the "area" you are working with.

from partner-contact.

@pedrobaeza area should be given in __openerp__.py as category and partner_contact isn't an area in term of object. Plus renaming modules makes difficulties in migrations and we have no naming convention for module written in https://github.com/OCA/maintainer-tools/blob/master/CONTRIBUTING.md

from partner-contact.

This was also debated in the past, because partner itself is not an area as you say, but it's a very important topic not to be included in the names. Odoo itself was debating to split base module to include all res.partner related stuff in a partner module. I was the one to think on not to put partner_ also until I speak with @hbrunn about it.

from partner-contact.

@pedrobaeza What about a talk with a PR on https://github.com/OCA/maintainer-tools/blob/master/CONTRIBUTING.md ?

from partner-contact.