Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116484 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 31534 invoked from network); 22 Nov 2021 21:36:19 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 22 Nov 2021 21:36:19 -0000 To: internals@lists.php.net,Kim Hallberg References: Message-ID: <7f2f3814-6545-1d5b-cb44-607fff9f7edd@naderman.de> Date: Mon, 22 Nov 2021 23:32:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Posted-By: 91.64.134.108 Subject: Re: [PHP-DEV] Sponsor link on github.com/php From: naderman@naderman.de (Nils Adermann) On 22.11.21 23:07, Kim Hallberg wrote: > >> On 22 Nov 2021, at 10:53 PM, Sara Golemon 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.