I looked at the Wikipedia article that you wrote. I think the content is good, but there is too much subjective wording in it, which makes it read more like an advertisements... I think that's why they rejected it.
As I didn't really know what to do about it, and was looking for a break from coding, I looked at the Mozilla
pages and decided to try a rewrite. Let me know if you think it can be an improvement or if it just makes things worse.
The Odoo Community Association, or OCA, is an open source community of developers of modules for, or tools that can be used in connection with, the [Odoo] ERP software.
It is a nonprofit organization fully independent of Odoo S.A., run by its members and with headquarters in Lausanne, Switzerland. As of 2017, the organization holds around 150 members. It describes its mission as "to promote the widespread use of Odoo and to support the collaborative development of Odoo features". [Source]
The main activities of OCA can be described as maintaining and developing the open source projects under its umbrella, or somehow facilitating their development.
All software currently maintained by the OCA is distributed free of charge under the terms of [AGPL] (link) and is free and open-source software (FOSS). It is either created by OCA members or donated to the OCA by the original author. All content is accessible as a collection of [Github] repositories (link) under the OCA flag.
The following is a non-exhaustive list of software maintained by OCA:
- Odoo modules, grouped around a certain theme such as accounting, HR, MRP, etc. Modules are available for Odoo versions 8.0 until the most recent version. OCA modules run on the free and open source Odoo Community core as well as on the licensed Odoo Enterprise version distributed by [Odoo S.A.].
- The Odoo Community Branch (OCB), a branch of the Odoo software with community bugfixes and enhancements not done by Odoo S.A.
- The OpenUpgrade project, a toolkit/framework that offers a free upgrade path from one major version of Odoo to the next
- OdooRPC, a tool to connect to Odoo externally through the RPC API.
OCA also facilitates development by maintaining a translation platform [Link] for Odoo modules and a Runbot [Link] to continuously monitor code quality of the modules. The OCA also maintains a set of guidelines for good practices in the creation of Odoo modules [Link] and a set of best practices the upgrading of Odoo modules between different versions. [Link]
Each contributor is asked to sign the Contributor License Agreement (CLA). [Link] Each code repository is managed by a self-selected team of technical experts (the Project Steering Committee or PSC) who are active contributors to the project. Any code that is contributed by an OCA member needs to be reviewed and approved by at least two other members before being merged into the the main branch by one of the PSC members. In this way, code quality is ensured and the PSC retains some control over the direction of the project.
The OCA organizes biannual Code Sprints, involving 2 or 3 days of collaborating programming on OCA projects. [Link].
In 2014, The organisation was renamed from "OpenERP Community Association" to "Odoo Community Association" in line with the name change of the product provided by Odoo S.A.
In October 2016, the OCA joined the Open Source Initiative .
The OCA relies on contributions from members and donations or sponsorships  from companies (mostly Odoo integrators) that are sympathethic to the cause of OCA.