Session 8: Getting started with Contributing on OCA (3 sessions)
Training
Location: Online - 11/5/24, 2:00 PM - 11/5/24, 4:00 PM (+0100) (2 hours)
Tom Blauwendraat AND Ronald Portier

Tom Blauwendraat

Therp

Starting as a developer on Odoo in 2014, originally with Sunflower IT, Tom is now co-owner of Therp BV. Within in the OCA, Tom has become a delegate and PSC of server-tools and l10n-netherlands in recent years. He has experience with teaching junior programmers, within the company and as a hired teacher for some in-house programmers on the client side.

Frequently confused as to what his role should be - developer, consultant, businessman or housefather.

Ronald Portier

Therp

Ronald started his career as a developer 35 years ago when as an unemployed historian he was offered the opportunity to retrain as a programmer. For a long time he worked with fairly large IBM systems on ERP applications. That's where he discovered the need for testing and delivering stuff that actually works, rather than shiny stuff with alot of "features". He developed an understanding of the need for standards, and got enthusiastic about the promises of Unix and later Linux.
Ronald is a strong believer of free software, believing that the free from "freedom" is the way forward for the good of not only programmers but users and society in general.


Sessions 8-10 - Contributing to the OCA:


  • The OCA review process

  • The importance of unit tests

  • The important of pre-commit

  • OCA runboat and CI

  • Translations in OCA

  • Stale / not stale

  • How to contact a PSC member or apply to be one yourself

  • Before you submit your PR: checking if similar work already exists, and deciding on which repository to put it

  • Python dependencies, dependencies between PR's

  • "Rebel modules"


Modules Migration:

  • how migrations are part of the OCA model

  • data migration and openupgrade

  • code migration:

    • The need to keep history

    • Technical method

    • Following all the steps

    • Maintain and increase code quality

    • Improving and adding tests


For technical people. Possible goals:

  1. Get started with Git and flows (pre-requisite)

  2. The contribution process - proposing changes or fixes (pre-requisite)

  3. Ports - forward and back porting, 

  4. Migrating a module