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..

On 02.02.2026 11:44, Alessandro Lai wrote:
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.

Il giorno lunedì 2 febbraio 2026 alle 11:19:28 UTC+1 Alex Makarov ha scritto:

    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



    On Mon, Feb 2, 2026 at 1:02 PM 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 <http://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>.

--
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/42d351a7-0d23-421c-aac6-cb0c24aa10c0n%40googlegroups.com <https://groups.google.com/d/msgid/php-fig/42d351a7-0d23-421c-aac6-cb0c24aa10c0n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Jordi Boggiano
@seldaek -https://seld.be

--
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/a211baca-9192-4722-9f66-357caf118f05%40seld.be.

Reply via email to