Agreed thorfi.
@jamiet: I wasn't consulted about this change and don't expect to be. I don't expect the current team to get every decision right, just like I/my team didn't, but I know they're v pragmatic and effective. If they think PPSC should be an option they'll do so, if not it won't be, and they'll make that decision on their own good judgement.
@stephie: As a past freelance coder, current software developer, past webDip developer, person with knowledge of our income/expenses, who has made paid changes to webDip, and who has seen a webDip fork site held to ransom for $20,000 of developer costs: I can safely say that complex changes to the webDip codebase just won't be made by payments from the donor pool.
It takes some time to be able to trust a freelance developer to publish safe/efficient/neat changes to a busy site (when even a dumb change I make can bring it down!), but it takes even more time to become familiar with a complex 40KLOC project like webDip.
Freelance devs advertise that they're familiar with WordPress / Drupal / Oracle eBusiness / whatever, so they can make a change to it right away. Making a change to a unique 40 KLOC codebase like webDip takes a lot of familiarization that excludes quick jobs from freelance workers (unless you pay a huge amount or don't worry about quality, which means instability).
Rather than expecting to pay for freelance developers we should appreciate those who enjoy working on it as a hobby, and encourage others to try.