If the problem is how quick an identified and fixed bug can be merged in trunk, crowd funding is not the solution. Here is why it takes time:

1. A merger (person in charge of merging) needs to be extremely (if not the most) qualified technically to avoid introducing new bugs or regressions when merging new code,
2. A merger engage OpenERP SA's contractual responsibility at every merge because he adds code that Enterprise contracts will guarantee forever,
3. It is not because a bug has been identified and fixed for a customer that it is a bug and/or that the fix is relevant for the default version of OpenERP (meaning for the whole world). It means there is an additional verification step even if the fix exists and is correctly coded.

These reasons show you that:

• A merger must not only be an exceptional developer and technical analyst but also have a serious experience in OpenERP. It is complicated and long to find and ramp up this kind of resources.
• Money cannot buy engaging OpenERP SA's legal responsibility more lightly. That due diligence needs to be done in any case.

As a final note: if the reason why you ask to get this is to have access more easily to a better bugfixed version of OpenERP without contracting an Enterprise contract, it defies the purpose of the business model. You are asking to receive the result of a service that you are not paying for. In fact, making public the bugfixes of Enterprise customers is already not common practice because you can cherry pick them without a contract. If one day the mergers team is able to have no backlog at all and that all the correct Enterprise bugfixes are consistently merged quickly in OpenERP, it shouldn't shock anyone that this version of OpenERP be available only to the Enterprise customers and that the users not paying anything get a version that doesn't have these merges.