I think you've missed my points.
Grants
Writing a grant is usually not difficult or time consuming, once you've done it a few times. I've helped apply for several grants for a local non-profit, and the information is usually the same across applications. Last year I did most of the work to apply for the Google Season of Docs for Plone, and I reused material from both Plone and GSoD itself. We didn't get selected. I'll try again next year, as we can pretty much reuse what we submitted last year.
That's the key. Much of the grant writing material is reusable. It's easily adaptable to specific grants or programs.
I would like the Board to produce a Grant Writing Kit (reuse our GSoD or GSoC material), then publish to its members that the Board will actively collaborate with members to apply for a grant to develop any component of Plone that aligns with its road map.
Employees
I would prefer the Board first tap its members as grant writers before hiring someone to raise funds out of which that person would be paid. Hiring staff has risk and requires a lot of time from Board members. Of course, if the Board is actually considering this option, then they'll need to apply for a grant anyway because it has insufficient cash on hand to hire someone even part-time. It does not have sufficient cash on hand to pull this off, and has nowhere near the resources of the Django Software Foundation which has a paid Fellowship Program. Nonetheless, I think it would be a good goal if the required resources appear in the future.
New ideas
I would like the Board to consider crowd-source fundraising through Polar. From my linked post:
Polar.sh allows funding specific GitHub issues and saying how much money would be needed to fix them. See discussion at polar.sh - funding specific issues · collective/icalendar · Discussion #697 · GitHub . This would be an interesting fundraising experiment to compensate developers for their time, so they can take out their sweetie on a date night.
This option also serves as a poll for Plone feature development. Desirable features get pledges to fund.
Blockers
There seems to be resistance within the Board that the Plone Foundation shall not pay people to develop Plone. I assume that that might have been done in the past and ended badly. But neither of these options that I propose involve the Plone Foundation directly hiring someone, nor paying out of its own budget. Time commitments are minimal, there is no financial cost to the Foundation, and there is no risk. Right now it's a lost opportunity.
In Plone, the blockers to diverse fundraising include the following.
- Members don't know that they can take the lead on a grant application to enhance Plone.
- The Board does not actively solicit requests for grant applications.
- The Board has not actively solicited, nor responded to, new ideas for fundraising from its Members.