RFC Moving Easy My Coop to OCA

[robinkeunen]

Easy My Coop, also developped originally for the BEES coop but is now used by 25+ cooperatives. Additionnaly other IT cooperatives (coopdevs, cooperatic) are starting to use and contribute to the solution for their own customers.

At Coop IT Easy, we believe it's time to go further than just applying the AGPL license and to really make this project Open Source. By that we mean

• bring together a community around the code,
• make the code easier to contribute to
• moving under the OCA umbrella

Why do it ?

• Raise the code quality to the OCA standards.
• Release the project ownership ;
• Become the reference repository for Share Management with Odoo ;
• Make contributions easier for people outside Coop IT Easy ;
• Grow the project visibility and attract new customers and contributors ;
• Give a better understanding of the roadmap ;

What do we need to do ?

Required

1. Rename repositories and modules to more generic names
   • cf Analysis - rename repositories and module beescoop/Obeesdoo#248
2. Remove all references to Obeesdoo and Easy My Coop
   • in python code
   • and xml data
   • cf Remove obeesdoo and easy_my_coop references beescoop/Obeesdoo#249 (archived)
3. Add demo data to demonstrate basic flows
   • cf Demo data and unit tests beescoop/Obeesdoo#250 (archived)
4. Cover main flows with unit tests
   • cf Demo data and unit tests beescoop/Obeesdoo#250 (archived)
5. Rename models

How

The migration will be done incrementally in the order given in the previous section. Each improvement will bring its migration script relying on the OCA Open Upgrade Library.

Following the OCA Repository Policy, the repositories and module will be proposed as a topic repository for Easy My Coop - Share Management

The repositories will be marked as Incubation Repositories. The modules should be marked with the beta maturity levels because, even though they're used in production, they will be heavily refactored.

As we split and improve the modules, some might be extracted to the relevant main OCA repositories (Sale, POS, ...).

In the long run, they should contain only the specific features needed. Features also relevant for other use cases, outside the vertical’s perimeter, should ideally be extracted and moved to the appropriate Main or Topic repository.

Financing

Coop IT Easy received a subsidy from the Bruxelles Region to foster intercooperation around the digital commons. This subsidy will cover three endeavours:

1. Bring together a community of users (cooperative supermarkets) to co-finance their ERP solution ;
2. Build a community of developpers to collaborate on shared code ;
3. Make the Easy My Coop and Obeesdoo modules easier to collaborate to.

This RFC describes the work needed in the 3rd item. The subsidy will cover the costs of 80 days of development and tests by Coop IT Easy.

The subsidy runs from July 2021 to December 2022

Resources

OCA Repository Policy

PYSI project summary (french)

cf beescoop/Obeesdoo#247

[robinkeunen]

[polchampion]

Listing vertical-cooperative modules to be reorganised, by depth wrt easy_my_coop

Depth 1

• easy_my_coop
• partner_age
• website_recaptcha_reloaded

Depth 2

• easy_my_coop_be
• easy_my_coop_fr
• easy_my_coop_ch
• easy_my_coop_es
• easy_my_coop_es_website
• easy_my_coop_api
• easy_my_coop_api_logs
• easy_my_coop_website
• easy_my_coop_website_portal
• easy_my_coop_taxshelter_report
• easy_my_coop_loan
• easy_my_coop_dividend
• easy_my_coop_export_xlsx
• beesdoo_easy_my_coop

Depth 3

• easy_my_coop_connector
• easy_my_coop_website_taxshelter
• easy_my_coop_loan_website
• easy_my_coop_loan_account
• easy_my_coop_loan_bba

Depth 4

• easy_my_coop_loan_account_be