The Question has been closedby
Like fpinckaers say, Saas offer doesn't accept custom module or development. That a choice and I agree with this. Fabien said that the only way is that my wonderfull module become part on official OpenERP version.
- What is the correct way to propose my module ?
- I make some modules that correct some view and try to correct some usabililty defect. Should I propose module or patch core of OpenERP with a merge proposals ?
Thank in advance for your reply.
What is the correct way to propose my module ?
There is no way to propose a module. The R&D team decides which module they will incorporate based on usual feedback channels (customer feedback, launchpad discussions, most downloaded modules on apps, ...).
In other words: you can not push your module, the R&D pull the ones that fit their priorities.
So, the chances to integrate you new modules in the official distribution is extremely low as we want to avoid increasing the number of official module. (we currently focus on improving the quality rather than the quantity of official modules)
The real question is not "how to make my module become official" but rather "how to give more visibility to community modules" and better integrate them in OpenERP so people can use them easily (one click install, update, better apps plateform...)
Being official should not be a requirement for a module to be widely used, maintained and visible. --> otherwise contributors will get frustrated. So, one of our goal is to allow users to easily use, update and find community modules.
I make some modules that correct some view and try to correct some usabililty defect.
If you fix or improve the usability of existing module, please do a merge proposal on the trunk branch.
If you want to add new features, you should develop a new module because we usually refuse merge proposals which are new features.
About This Community
|Asked: 2/12/13, 6:46 AM|
|Seen: 1562 times|
|Last updated: 3/16/15, 8:10 AM|