14
i've been wanting to work on a payment class useable for paypal and other payment systems, so this might be an extra goal that i could aim for
i'm thinking (regarding the request module), have a multi-step procedure. modules/addons get requested, requests are cleaned up or expanded upon by a team monitoring the module, and then posted for review. a general price range estimate for the end result would be determined by qualified individuals on the monitoring team, as a guideline of what to expect.
users will 'sign up' showing their interest in using this module/addon, feedback on features, and interest in paying for this module/addon
once the pay pledges have reached the estimated cost, the module could be put 'on the market', whether on xoops.org or something like scriptlancer, with a note that the estimated range is the max of what we're willing to pay for the work.
once a dev signs up showing interest with an approved bid, the pledges are called in, and donations would be made to a XOOPS donation acct which would be managed separately from regular XOOPS site donations (a pool of money, if you will). the XOOPS core team (like herko or whoever does it currently) would be admin over the funds
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
, and development on the module/addon would then begin
how's that sound?