What's the OCA, what are our goals ?
Why working with OCA ?
How it's working, how to contribute ?
Last update from the board and review of what we achieved so far
- Joël Grand-Guillaume -
2. AGENDA
● Introduction & history
● What's the OCA, what are our goals ?
○ OCA Mission
○ OCA governance
○ OCA projects
● Why working with OCA ?
● How it's working, how to contribute ?
● Last update from the board and review of what we achieved so far.
○ Short-term planning
○ Mid-term planning
5. ● OCA created in 2013
● Founder companies:
○ Camptocamp, Switzerland / France / Austria
○ Akretion, France / Brazil
○ Vauxoo, Mexico
○ Savoir-faire Linux, Canada / France
○ Therp, Netherland
○ Elico Corp, China
History
6. OCA’s objectives
● Coordinate and organize collaborative work => reduce
similar/redundant developments
● Improve the partnership with Odoo SA => unified voice
● Promote the use of the Odoo solution
● Facilitate synergies, collaborations and fundraising efforts
● Increase the quality of community contributions
● Provide a partner-independent legal entity to protect intellectual
properties
● Provide resources for all OCA’s projects (infrastructure, funding,
legal support)
8. Members
● Any physical person who accepts the OCA’s bylaws, pays the
membership fees and signs the CLA
● Contribute to the OCA resources
● Can be in charge of an OCA project steering committee
● Member newsletters
● Membership fees: EUR 50.-/year
● At this time, more than 200 members
9. Delegates
● OCA Members who have the voting rights at the Delegate
Assembly.
● Can elect new Delegate & Board Members
● Prevent an hostile takeover from an external company
● At this time, 57 delegates
10. Board
● Executive entity of the OCA
● 7 founders:
○ Luc Maurer, Camptocamp
○ Joël Grand-Guillaume, Camptocamp (President)
○ Sébastien Beau, Akretion
○ Nhomar Hernandez, Vauxoo (Secretary)
○ Maxime Chambreuil, Savoir-faire Linux (Vice-President)
○ Stefan Rhijnhart, Therp (Treasurer)
○ Éric Caudal, Elico Corp
● 2 new members since last Delegate Assembly (June 5, 2014)
○ Alexandre Fayolle, Camptocamp
○ Graeme Gellatly, Openforsmallbusiness.co.nz
11. OCA’s projects
● Project Steering Committee Teams (PSC)
○ Team which is responsible of 1 or more projects
○ Completely autonome on their projects
○ 1 team leader
○ Localization could be a PSC
● PSC Team leader
○ Must be OCA member
○ Decide who is member of the team
○ Control that all contributors have signed the CLA
○ Should communicate and report to OCA Board
● OCA Community Maintainers
○ Include in all PSC Teams
○ Elected by current Community Maintainers (Meritocracy principle)
13. ● A legal document signed by the contributor to waive the copyright of
his/her code to the OCA
● Thanks to the CLA, the code of all OCA’s projects is owned by the OCA
● Guarantees the long-term life of the OCA’s projects
● All contributors must sign the CLA
● 2 CLA types:
○ Entity CLA (ECLA): to be signed by any company having employees working on OCA’s
projects
○ Individual CLA (ICLA): to be signed by all contributors (OCA members or not)
● More info here: www.odoo-community.org
Contributor License Agreement (CLA)
14. Why OCA ?
● Increase quality of community modules
● Improve visibility of projects and modules
● Ensure long term support of modules
● Reduce similar/redundant development
● Provide a partner-independent legal entity to protect intellectual
properties
● Provide a unified voice to discuss with Odoo SA
● Provide resources for OCA’s projects (infrastructure, funding, legal
support)
15. Do you want to join the OCA?
Go to: www.odoo-community.org
Via OCA E-shop
16. Achievements
● Internal processes & Operations
● OCA website
● Migration of the community work from Launchpad to GitHub
● Continuous Integration Server & Automated tests
● Code Sprints
● Collaboration with Odoo
○ Discussion with Odoo SA
○ New version 9.0 : Accounting workshop
17. Mid/long-term planning
● Provide a better quality
○ Split contributions in 3 levels:
■ Community levels
■ Incubator for candidate modules
■ OCA Module Certified (docs, PEP8, migrations assurance for the future)
○ Bring clear rules that define a OCA certified module
● Improve the collaboration with Odoo SA
○ Be involved in the devs of the next releases
○ Communicate the roadmap
● Better docs and processes
○ Share knowledge between contributors
○ Define clear processes (suggest ideas, collaborate on devs, etc.)