Sponsor link on github.com/php

  116481
November 22, 2021 21:53 pollita@php.net (Sara Golemon)
Now that the new PHP Foundation has been announced, I've been asked if we'd
mind configuring a Sponsor button on our github.com project profile.
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository

Pro: Gives appreciative users somewhere to send their appreciation and the
project doesn't have to worry about all the tax implications.

Con: PHP has always remained unbiased regarding frameworks and libraries,
and I think the same should apply to other external organizations, like the
foundation.  There are, in fact, other foundations already in existence,
and if we send traffic to one, we should send traffic to all.

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 which contributors should assess individually.

Looking forward to thoughts,
-Sara
  116483
November 22, 2021 22:07 hallbergkim@gmail.com (Kim Hallberg)
> On 22 Nov 2021, at 10:53 PM, Sara Golemon <pollita@php.net> wrote: > > Now that the new PHP Foundation has been announced, I've been asked if we'd > mind configuring a Sponsor button on our github.com project profile. > https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository > > Pro: Gives appreciative users somewhere to send their appreciation and the > project doesn't have to worry about all the tax implications. > > Con: PHP has always remained unbiased regarding frameworks and libraries, > and I think the same should apply to other external organizations, like the > foundation. There are, in fact, other foundations already in existence, > and if we send traffic to one, we should send traffic to all. > > 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 which contributors should assess individually. > > Looking forward to thoughts, > -Sara
What about a php.net/donate page? GitHub’s funding file works with custom URLs. So one solution could be a donate page where organisations can submit their links and possible a description. Something like /conferences and the user-groups. The page wouldn’t need any forms or anything, a PR directly to the page could work. Thoughts? Thank you, Kim.
  116484
November 22, 2021 22:32 naderman@naderman.de (Nils Adermann)
On 22.11.21 23:07, Kim Hallberg wrote:
> >> On 22 Nov 2021, at 10:53 PM, Sara Golemon <pollita@php.net> wrote: >> >> Now that the new PHP Foundation has been announced, I've been asked if we'd >> mind configuring a Sponsor button on our github.com project profile. >> https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository >> >> Pro: Gives appreciative users somewhere to send their appreciation and the >> project doesn't have to worry about all the tax implications. >> >> Con: PHP has always remained unbiased regarding frameworks and libraries, >> and I think the same should apply to other external organizations, like the >> foundation. There are, in fact, other foundations already in existence, >> and if we send traffic to one, we should send traffic to all. >> >> 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 which contributors should assess individually. >> >> Looking forward to thoughts, >> -Sara > > What about a php.net/donate page? GitHub’s funding file works with custom URLs. > > So one solution could be a donate page where organisations can submit their links > and possible a description. Something like /conferences and the user-groups. > > The page wouldn’t need any forms or anything, a PR directly to the page could work. > > Thoughts? > > Thank you, > Kim. >
I think a major benefit of linking GitHub sponsors with open collective is that the donation is charged as a line item on regular GitHub invoices, rather than having to go to some separate website and submit billing details. This significantly simplifies sponsoring for some organizations, e.g. where selecting a sponsor target on GitHub is a lot easier than getting some finance department to set up billing for a sponsorship on a third party website. That said, it could still be handled separately from the main php org page on its own github org if sentiment here is against tying them together. Just trying to help explain why GitHub sponsors specifically is beneficial rather than just a link to a donation page somewhere Cheers, Nils.
  116486
November 23, 2021 10:42 hallbergkim@gmail.com (Kim Hallberg)
> On 22 Nov 2021, at 11:32 PM, Nils Adermann <naderman@naderman.de> wrote: > > On 22.11.21 23:07, Kim Hallberg wrote: >> >>> On 22 Nov 2021, at 10:53 PM, Sara Golemon <pollita@php.net> wrote: >>> >>> Now that the new PHP Foundation has been announced, I've been asked if we'd >>> mind configuring a Sponsor button on our github.com project profile. >>> https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository >>> >>> Pro: Gives appreciative users somewhere to send their appreciation and the >>> project doesn't have to worry about all the tax implications. >>> >>> Con: PHP has always remained unbiased regarding frameworks and libraries, >>> and I think the same should apply to other external organizations, like the >>> foundation. There are, in fact, other foundations already in existence, >>> and if we send traffic to one, we should send traffic to all. >>> >>> 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 which contributors should assess individually. >>> >>> Looking forward to thoughts, >>> -Sara >> >> What about a php.net/donate page? GitHub’s funding file works with custom URLs. >> >> So one solution could be a donate page where organisations can submit their links >> and possible a description. Something like /conferences and the user-groups. >> >> The page wouldn’t need any forms or anything, a PR directly to the page could work. >> >> Thoughts? >> >> Thank you, >> Kim. >> > > I think a major benefit of linking GitHub sponsors with open collective > is that the donation is charged as a line item on regular GitHub > invoices, rather than having to go to some separate website and submit > billing details. This significantly simplifies sponsoring for some > organizations, e.g. where selecting a sponsor target on GitHub is a lot > easier than getting some finance department to set up billing for a > sponsorship on a third party website. > > That said, it could still be handled separately from the main php org > page on its own github org if sentiment here is against tying them > together. Just trying to help explain why GitHub sponsors specifically > is beneficial rather than just a link to a donation page somewhere > > Cheers, > Nils. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php >
As far as I know that is not the case. Look as vuejs/vue for instance. They have an Open Collective in their sponsors link and that opens a new tab. What you’re describing is using the GitHub sponsors platform, that is not the same as adding PHP Foundation’s Open Collective to PHP’s funding.yaml file. For GitHub sponsors the organisation, in this case PHP, would need to connect a bank account directly to the organization. You can see more information about that on the documentation regarding setting up GitHub sponsors for your organization[1] If PHP did that we wouldn’t really need non-profit orgs like PHP Foundation. As for linking to PHP Foundation’s Open Collective on a funding file[2]. That would go against PHPs unbiased nature, since as Sara pointed out. PHP has always remained unbiased in the past for things of this nature. So adding them there would create a link between the two orgranization that PHP don’t do for other organizations. Creating a /donate page on php.net where orgs that want to contribute monetarily towards the development of PHP and with a statement from PHP that these orgs aren’t officially affiliated and to use them as their own risk would, IMHO be an option. [1]: https://docs.github.com/en/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization [2]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository
  116487
November 23, 2021 14:04 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
  116488
November 23, 2021 14:36 rowan.collins@gmail.com (Rowan Tommins)
On 23/11/2021 10:42, Kim Hallberg wrote:
> For GitHub sponsors the organisation, in this case PHP, would need to connect a > bank account directly to the organization. [...] > > If PHP did that we wouldn’t really need non-profit orgs like PHP Foundation.
On the contrary, being able to set up a receiving bank account for such purposes is precisely the kind of facility which non-profit organisations are needed for. The point which a few people have made about not wanting to "bless" one particular non-profit org is reasonable though - linking one particular organisation's bank account there carries more implication of "ownership" than "here are places to pool resources if you want to support the project". Regards, -- Rowan Tommins [IMSoP]