The OCA, explained simply
Hundreds of developers share their Odoo modules in an association. Knowing how to use it means not rewriting what exists, and writing what is missing so that others can use it.
In one image
A neighbourhood library run by its readers: everyone drops off books, a committee checks that they are in good shape, and anyone can borrow them. The OCA is that library for Odoo modules: thousands of bricks, checked by peers, maintained from version to version.
What to remember
-
Look before writing
Before building, we look at whether the brick already exists: in Odoo, in your project, in the OCA. A brick that exists is a brick nobody pays to write, nor to maintain alone.
-
The same rules as everyone
Modules are built by shared conventions, which the OCA keeps current. As a result, any Odoo developer finds their way, and you are tied to no one.
-
Each brick has its licence
Not all of them go together. The licence of each brick is read before choosing, and a tool checks it.
-
Give back to the library
A brick useful to others can be dropped off there, reviewed, and maintained by the community. Not all of them, and not always: only when it is worth the time.
Before writing a line
Three questions, in order, then we write.
-
Does Odoo already do it?
Often, in a corner of the settings.
-
Does your project already do it?
An existing brick, to complete rather than duplicate.
-
Does the OCA already do it?
Thousands of bricks, sorted by domain.
-
Then we write
By the same rules, so that the brick can join the library.
To go further
-
OCA standards, explained to developers
A summary of the conventions, the three questions before writing, and the links to the OCA pages that prevail.
A question?
I answer the curious too: write to me.