Thank you Chris for the input. I would like to remind everyone though that the "Sponsor" button on GitHub would simply be a link toward our OpenCollective account, it wouldn't allow to capture any funding there. So, to go through funding, it would only send the user to our page, where we clearly state all the required information that our bylaw requires.
The config would still be useful to point the ecosyste.ms (and possibly others) process toward OC. Il giorno lunedì 2 febbraio 2026 alle 20:09:43 UTC+1 [email protected] ha scritto: > I'm fine with this, but I think it's getting into the granularity of > exactly what defines "solicitation." Many US states consider a "Donate Now" > button (or in this case "Sponsor" button) to be a form of solicitation. > Since it's not via the OpenCollective, which is our exception to our rule, > we might be running afoul of our non-solicitation policy. Using > OpenCollective is the safe way to handle that since the burden is on them > for all the legal stuff. > > I am not a lawyer though, but I don't personally see a reason why I would > be against adding a FUNDING.yml and GitHub Sponsor button to the repos in > question, as our bylaws should make sure the money is handled correctly. > > -Chris > > On Mon, Feb 2, 2026 at 5:02 AM Alessandro Lai <[email protected]> > wrote: > >> These are the pending PRs: >> - https://github.com/php-fig/log/pull/86 >> - https://github.com/php-fig/container/pull/51 >> >> I created them in draft state to avoid merging them inadvertently. >> >> Il giorno lunedì 2 febbraio 2026 alle 10:35:17 UTC+1 Alessandro Lai ha >> scritto: >> >>> Hi all, >>> this is a notice mainly directed toward our Core Committee. >>> >>> We just received notice that *we could receive two 50$ donations* from >>> the *PHP Ecosystem Fund*: >>> https://funds.ecosyste.ms/funds/php/allocations/february-2026 >>> >>> This is a platform that redistributes the grouped funding of some >>> companies and organizations, and which is the redistributed toward the >>> "most critical packages published to packagist.org". Our *psr/log and >>> psr/container made into their list.* >>> >>> We could either accept the donation personally (as secretaries, which I >>> would discourage) or as a group via OpenCollective. which would be ideal, >>> and in line with our bylaws: https://www.php-fig.org/bylaws/funding/ >>> >>> Only caveat: to accept it as a group *we have to set GitHub's >>> `FUNDING.yaml` file in (at least) those two repositories*. I wouldn't >>> classify that as "soliciting funding" (and hence against our bylaws) but I >>> would still like to give out this notice, to give to any CC which would be >>> against this a chance to speak up. >>> >>> *We have until February 15 to accept this invitation.* >>> I will soon create the PRs for this and link them back here. If no one >>> object to this by February 13, I will proceed with merging them. >>> >> -- >> > You received this message because you are subscribed to the Google Groups >> "PHP Framework Interoperability Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/d/msgid/php-fig/acedfcc0-76ad-4d76-8429-fca9226d1e71n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/php-fig/acedfcc0-76ad-4d76-8429-fca9226d1e71n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Chris Tankersley > http://ctankersley.com > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/php-fig/7063361f-629d-4e04-81dd-b915d48bf3d7n%40googlegroups.com.
