Move modules to the OCA

[robinkeunen]

Depends on

• Integrate partner_contact_address to cooperator module #350
• Remove jquery.inputmask.bundle.js #227
• Remove dependency to email_template_config #356
• Migration to version 14 #357

[ferdymercury]

Thanks for your wonderful work on moving towards OCA!

One question, is there a (very rough) time estimate when the migration will be complete? Will it target 14.0 and 12.0? Or also 16.0 once it is released?

Thanks again, regards.

[robinkeunen]

Hey @ferdymercury ,

• cooperators modules in v14 are here : https://github.com/coopiteasy/vertical-cooperative/tree/14.0
• we're moving modules to the oca/cooperative repository starting this week
• 16.0 is not yet planned, it will depend on the customers we get. If you want to start working on it, please feel free, we will review eagerly :-)

[ferdymercury]

• cooperators modules in v14 are here : https://github.com/coopiteasy/vertical-cooperative/tree/14.0

Thanks for the info! Do you know by chance if the obeesdoo modules are also available for v14?
We are now using all these from odoo v12:

• beesdoo_account
• beesdoo_base
• beesdoo_easy_my_coop
• beesdoo_pos
• beesdoo_pos_coop_status
• beesdoo_product
• beesdoo_shift
• beesdoo_shift_attendance
• beesdoo_website_eater
• beesdoo_website_shift
• beesdoo_worker_status
• easy_my_coop
• easy_my_coop_easy_migration
• easy_my_coop_es
• easy_my_coop_website
• easy_my_coop_website_portal

• we're moving modules to the oca/cooperative repository starting this week

Nice, thanks!

• 16.0 is not yet planned, it will depend on the customers we get. If you want to start working on it, please feel free, we will review eagerly :-)

Not sure if I can be of any help with it, I don't know what are the steps involved towards it.

[robinkeunen]

Nice to hear that our modules are used elsewhere :-)

We won't port the beesdoo modules to v14, we'll jump directly to v16. You probably noticed we're busy splitting all these modules as well. Tell us if you have trouble upgrading those, we might give a few pointers.

To port on v16, you will need to adapt the code of v14 to the new code that will be out next week. Then you must write migration scripts for the data. We can also arrange a call sometimes to get you started.

[ferdymercury]

Our coop supermarket (in Valencia) is planning to migrate from a closed-source ERP to odoo around the end of the year. The script I am writing just ports the data (excel files) to Odoo via its API. My question is, could I just migrate from the Excel files to Odoo v16? Or your modules won't just be available in Odoo16 unless someone has written migration scripts for them?

[robinkeunen]

If you're importing data directly to v16, you won't need migration scripts for you data. You will only need the code available in v16. We will probably port cooperator modules in early 2023 and beesdoo modules later in the year, nothing sure though.

[ferdymercury]

Thanks for the clarification and congrats for the OCA v14 migration!

Just in case I find some time in the future, how many hours do you estimate it would take me to port the OCA cooperators module from v14 to v16? I have experience with C++ and Python programming, but none with your modules / addons.

[robinkeunen]

I'm afraid it's a bit hard to tell because we don't know much about odoo 16 yet. Plus you'd need to get familiar with the odoo framework first. For all the modules, without the migration scripts, I'd say between 40 and 80 hours ?

[ferdymercury]

Ok, good to know, thanks for the info. Then it's something I surely can't do, as I am just volunteering a couple of hours here and there during my free time apart from my normal job :) .

[robinkeunen]

module	[12.0][REM]	[14.0][REM]	[12.0][ADD]	[14.0][ADD]	time	comment
cooperator	☑️	☑️	✅	✅	0
cooperator_api		✖️		✖️	0	not ported in v14
cooperator_api_logs		✖️		✖️	0	idem
cooperator_portal	☑️	☑️	✅	✅	0
cooperator_website	☑️	☑️	✅	✅	0
cooperator_website_recaptcha					?
cooperator_website_uppercase_lastname	✖️	✖️	✖️	✖️	0	leave and rename repo to cie-cooperative
easy_my_coop_connector	✖️	✖️	✖️	✖️	0	not working
easy_my_coop_dividend	✖️	✖️	✖️	✖️	0	not installable
easy_my_coop_export_xlsx	✖️	✖️	✖️	✖️	0	not installable
easy_my_coop_loan	✖️	✖️	✖️	✖️	0	not ported, move out of cooperator app
easy_my_coop_loan_account	✖️	✖️	✖️	✖️	0	idem
easy_my_coop_loan_account_be	✖️	✖️	✖️	✖️	0	idem
easy_my_coop_loan_bba	✖️	✖️	✖️	✖️	0	idem
easy_my_coop_loan_website	✖️	✖️	✖️	✖️	0	idem
l10n_be_cooperator	☑️	☑️	☑️	☑️	0	oca/l10n-belgium
l10n_be_cooperator_portal					?	oca/l10n-belgium
l10n_ch_cooperator					?	oca/l10n-switzerland
l10n_es_cooperator					?	oca/l10n-spain
l10n_fr_cooperator					?	oca/l10n-france
portal_recaptcha			☑️		?	oca/website

Legend

• [12.0][REM]: PR to remove module from coopiteasy/vertical-cooperative on branch 12.0

• [14.0][REM]: PR to remove module from coopiteasy/vertical-cooperative on branch 14.0

• [12.0][REM]: PR to add module to oca/cooperative on branch 12.0

• [14.0][REM]: PR to add module to oca/cooperative on branch 14.0

• PR opened : ☑️

• PR merged : ✅

• nothing to do : ✖️

@huguesdk fyi

[huguesdk]

moving some modules to other repos might need some extra work. for example, OCA/website#914 is currently blocked because it lowers test coverage, so it has been flagged as “needs tests”.

[huguesdk]

current status

• [12.0][ADD] l10n_be_cooperator OCA/l10n-belgium#150 is blocked by failing tests due to the fact that cooperator removes the unique constraint on bank accounts. [REM] cooperator: Unique bank constraint on partner #310 must be re-created in OCA/cooperative (in 12.0 and 14.0) and a migration script must be added to re-enable the unique constraint.
• [12.0][ADD] portal_recaptcha OCA/website#914 is blocked by missing tests (it lowers coverage). a test for this function must be added.
• cooperator_website_recaptcha is blocked by [12.0][ADD] portal_recaptcha OCA/website#914.
• l10n_be_cooperator_portal is blocked by [12.0][ADD] l10n_be_cooperator OCA/l10n-belgium#150.

here’s the order in which i think things should be done:

1. fix the unique constraint on bank accounts in cooperator ([REM] cooperator: Unique bank constraint on partner #310)
2. check that tests on [12.0][ADD] l10n_be_cooperator OCA/l10n-belgium#150 now pass and add the same pull request for 14.0.
3. add a test for [12.0][ADD] portal_recaptcha OCA/website#914 to ensure test coverage stays the same, then add the same pull request for 14.0.
4. create the pull requests for cooperator_website_recaptcha and l10n_be_cooperator_portal.

regarding the other modules (api & other l10n), i think that the pull requests should be able to be created at any time.

[huguesdk]

current status

everything stated in the previous message is resolved. portal_recaptcha has been given tests and a refactoring, which also needed a refactoring in cooperator_website_recaptcha. here are the pending pull requests:

• [12.0][ADD] portal_recaptcha OCA/website#914 [12.0][REM] portal_recaptcha #407
• [14.0][ADD] portal_recaptcha OCA/website#928 [14.0][REM] portal_recaptcha #408
• [12.0][ADD] cooperator_website_recaptcha OCA/cooperative#43 [12.0][REM] cooperator_website_recaptcha #409
• [14.0][ADD] cooperator_website_recaptcha OCA/cooperative#44 [14.0][REM] cooperator_website_recaptcha #410
• [12.0][ADD] l10n_be_cooperator OCA/cooperative#58 [12.0][REM] l10n_be_cooperator OCA/l10n-belgium#181
• [14.0][ADD] l10n_be_cooperator OCA/cooperative#59 [14.0][REM] l10n_be_cooperator OCA/l10n-belgium#182
• [12.0][ADD] l10n_be_cooperator_portal OCA/cooperative#60 [12.0][REM] l10n_be_cooperator_portal #411
• [14.0][ADD] l10n_be_cooperator_portal OCA/cooperative#61 [14.0][REM] l10n_be_cooperator_portal #412