[Internal] Incoming funding & GitHub settings

30 views
Skip to first unread message

Alessandro Lai

unread,
Feb 2, 2026, 4:35:17 AM (2 days ago) Feb 2
to PHP Framework Interoperability Group
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 Fundhttps://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.

Alessandro Lai

unread,
Feb 2, 2026, 5:02:41 AM (2 days ago) Feb 2
to PHP Framework Interoperability Group
These are the pending PRs:
 - https://github.com/php-fig/log/pull/86

I created them in draft state to avoid merging them inadvertently.

Alex Makarov

unread,
Feb 2, 2026, 5:19:28 AM (2 days ago) Feb 2
to php...@googlegroups.com
Looks alright to me. I think that technically we can use a single public meta-repo "php-fig/.github" and put the file there so it applies to everything. See https://github.com/yiisoft/.github



--
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 php-fig+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/php-fig/acedfcc0-76ad-4d76-8429-fca9226d1e71n%40googlegroups.com.

Alessandro Lai

unread,
Feb 2, 2026, 5:44:48 AM (2 days ago) Feb 2
to PHP Framework Interoperability Group
Thank you Alex, this is a very useful suggestion. Since it requires a new repository, I'll postpone going in that direction for now, but if no one has any objection, I'll follow that route.

Chris Tankersley

unread,
Feb 2, 2026, 2:09:43 PM (2 days ago) Feb 2
to php...@googlegroups.com
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

--
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 php-fig+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/php-fig/acedfcc0-76ad-4d76-8429-fca9226d1e71n%40googlegroups.com.


--
Chris Tankersley
http://ctankersley.com

Alessandro Lai

unread,
Feb 2, 2026, 3:10:52 PM (2 days ago) Feb 2
to PHP Framework Interoperability Group
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. 

Larry Garfield

unread,
Feb 2, 2026, 5:54:49 PM (2 days ago) Feb 2
to PHP-FIG
On Mon, Feb 2, 2026, at 3:35 AM, Alessandro Lai wrote:
> 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.

I see no issue with this. IANAL so I don't know if "passive solicitation" is something we care about, but assuming not, I think it's fine.

I don't personally care if the FUNDING file is in one repo, several, or even all. I leave that implementation detail up to the Secretaries to figure out.

--Larry Garfield

Jordi Boggiano

unread,
4:16 AM (5 hours ago) 4:16 AM
to php...@googlegroups.com, Alessandro Lai

IMO we should do this via the global org repo, so we don't have to do this on any more repos in the future if they get flagged as well, given the noise that every PR generates in those repos..

Reply all
Reply to author
Forward
0 new messages