Draft: Updates to funding bylaw

[KorvinSzanto]

This PR updates the funding bylaws to clarify disbursement, expand allowed funding options, and more.

Key changes are:

• Remove Tidelift as a collection option since they have been purchased and their mission has changed
• Grant permission to collect funding via opencollective directly
• Grant permission to set up print on demand swag options, at the discretion of the secretaries with (essentially) implicit approval from the core committee
• Define clear policy for when, how, how much, and to whom disbursements are made
• Explicitly allow repayment to individuals who have covered an expense, so funding at a later date in the year can be used to reimburse folks that quietly cover costs out of their own pocket

And here's what copilot thinks changed (Reviewed by me, no changes were needed):

This pull request updates the PHP-FIG funding bylaws to refine the organization's approach to raising and managing funds. Key changes include clarifying the funding sources, introducing new methods for contributions, and revising spending guidelines to ensure transparency and alignment with PHP-FIG's mission.

Updates to funding sources and methods:

• Revised the language to emphasize PHP-FIG's focus on funding from commercial entities benefiting from the PHP ecosystem, rather than private individuals.
• Added provisions for accepting contributions via Open Collective with detailed requirements for transparency and accountability, including itemized reporting of transactions.
• Introduced a new option for generating revenue through print-on-demand swag, with specific guidelines for product creation, ethical sourcing, and community oversight.

Spending guidelines and overfunding management:

• Updated rules for spending funds to allow reimbursement for approved expenses paid out-of-pocket by Secretaries, while maintaining restrictions on personnel payments.
• Defined "overfunding" and established a process for disbursing surplus funds annually to the PHP Foundation, with safeguards for tax and fee considerations.

Administrative adjustments:

• Clarified the approved expenses section and updated the formatting for consistency.

[Crell]

Why? Given our expenses are super minimal, 3 individuals offering $5 would cover us. An organization would probably want to start at three digits to make it worth their time to even notice us, and then we have too much money. :-)

[KorvinSzanto]

I worry a lot about the conflict of interest money brings into the organization. I don't want to start down the (in my opinion) slippery-slope of trying to increase funding from individuals and find ourselves buying advertisements or begging at conferences. I concede that it's unlikely especially when we have no funding, I just want to be sure that we have as much "undoing" as "doing" to do to go that route.

Additionally, if we don't end up with any alternative options for individuals we'd not have any (read a requirement for any) statement making it clear we don't intend to collect monthly subscription style payments from individuals.

I totally agree that a corp would pay a lot more than individuals, that's why we disburse overfunding via fee/tax free options so there's effectively no difference at all between giving us $500 and us giving $500 of overpayment to PHP Foundation through collective to collective transfers.

[Copilot]

Pull Request Overview

This PR updates the funding bylaws for PHP-FIG to clarify funding sources, expand approved funding methods, and define clear guidelines for disbursements and expense approvals.

• Removed TideLift as a collection option
• Introduced new provisions for contributions via Open Collective and print-on-demand swag
• Defined policies for overfunding disbursement and updated approved expenses guidelines