Creating a module base_property to be the base of pms/realestate/other repos that share property concept

[cvinh]

PMS, REMS and other vertical modules need the concept of property.

In that goal we choose to make a new base_property with common fields that could be shared with other vertical modules (starting with pms_base and real_estate)

BTW , why not res_property ? to be aligned with odoo's res_*...

[pedrobaeza]

Usually res is not used in module names. We use base_something or directly the name. The module may be called simply property if you want.

[cvinh]

Usually res is not used in module names. We use base_something or directly the name. The module may be called simply property if you want.

base_property is fine for me because we say in the name that this module is a base for something else...
About the model, can it be res.property then ?

[DarioLodeiros]

There is the module multi_pms_properties, which is designed to add certain common features to property management and could serve as a good foundation for a common properties module across repositories. There is no problem in renaming it to base_property, although since the concept of "property" is widely used in the code for generic purposes, we thought it was more appropriate to introduce the pms prefix to avoid confusion.

[mymage]

Hi all, as I wrote on OCA/vertical-realestate#17 I'm interested in real estate management.
From what I understand the choice is to integrate this repo with lightweight modules to manage "general properties" like real estate instead of continuing with real_estate repo.
I took a look at PMS and found that it is a bit overloaded with information that , in my case, are not useful or out of the context: ie. I do not have hotels with rooms for rent.
So two tough questions:

• is anyone working to this project to merge/simplify repos and models?
• would it be a good choice for me to switch to PMS now (using at least part of the property data) to be "ready" when the repo will be refactored?
  Let me know if I can help in any way.
  Thanks

[github-actions]

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.