Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116487
MIME-Version: 1.0
References: <CAESVnVoCMUqT+P+J55pC3Pg11CRcqS51xrw97O+ZXJfOnhY_iQ@mail.gmail.com>
 <BB084A41-CED9-4B21-8999-28D0A51FF540@gmail.com> <7f2f3814-6545-1d5b-cb44-607fff9f7edd@naderman.de>
 <867A507F-4320-4341-AEA9-9C7523B5E742@gmail.com>
In-Reply-To: <867A507F-4320-4341-AEA9-9C7523B5E742@gmail.com>
Date: Tue, 23 Nov 2021 14:04:49 +0000
Message-ID: <CA+kxMuSyAQZdVh1b2yo73z8QuxVMnEf_T2aRALNEO6Y3cgBaaw@mail.gmail.com>
To: Kim Hallberg <hallbergkim@gmail.com>
Cc: Daniele B via internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Sponsor link on github.com/php
From: Danack@basereality.com (Dan Ackroyd)

On Tue, 23 Nov 2021 at 10:43, Kim Hallberg <hallbergkim@gmail.com> wrote:
>
> For GitHub sponsors the organisation, in this case PHP, would need to connect a
> bank account directly to the organization.

I believe Nils is referring to this:
https://blog.opencollective.com/double-the-love/

Sara wrote:
> An alternative may be to link to the various foundations from php.net (and
> github.com/php) with some text stating that they are all independent
> organizations

One of the advantages of having the repos split on github is that each
repo could list the most appropriate sponsor links for the people
doing the work on that repo. For example php/doc-fr could have a
completely different place to sponsor, rather than the 'PHP
Foundation', to avoid burdening the 'PHP Foundation' with managing
doc-fr finances.

Kim wrote:
> PHP has always remained unbiased in the past for things of this nature.

PHP has always been rubbish at:
* long term support of versions.
* long term support of tools e.g. is PEAR/PECL dead or not? bugs.php.net
* having enough contributors to the docs and extensions.

Pointing to how things have been done in the past is a less strong
argument than you might think.

cheers
Dan
Ack