How to Get Involved in OCA Activities (Odoo Open Talk, July 2026 — slides in Japanese)

These slides are in Japanese. They were presented at an Odoo Open Talk held on 31 July 2026, and set out how to start contributing to the OCA (Odoo Community Association) — for people who write code and for people who don't.

The number of companies using Odoo in Japan has grown, but the number giving back to the ecosystem has not. This deck assumes that gap is not about willingness but about knowing where the entry points are, and aims to make the first step concrete.

What the deck covers

• What the OCA (Odoo Community Association) is — its relationship with Odoo S.A., and its AGPL/LGPL output
• Contribution is not only writing code — translation, issues, review, documentation
• Turn what troubles you into an issue — put it in the open instead of solving it internally
• The developer route — start with a small PR
• How a PR reaches merge (the CLA is signed on GitHub from the PR), and how long that realistically takes
• A worked example: how a two-line PR progressed (OCA/account-invoicing#2201)
• Mistakes new contributors commonly make — opening translation PRs directly, and others
• Rules for contributing with AI — the OCA Generative AI / LLM Policy (effective July 2026)
• Beyond individual contribution — why company commitment is necessary
• Realistic entry points for the Japanese community
• Glossary

Links

• OCA repositories (GitHub)
• CLA (Contributor License Agreement)
• Weblate — the OCA translation platform
• OCA Generative AI / LLM Policy
• The PR used as the worked example: OCA/account-invoicing#2201
• OCA Days 2026 — Daniel Reis on how to contribute (in English)
• Unofficial Japanese Odoo community Discord

Updated in October 2026 for the OCA moving CLA signing to a bot on GitHub, and for the new 20.0 branches.

Links inside the slides are clickable once you download the PDF.