Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116486 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 73088 invoked from network); 23 Nov 2021 09:46:11 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Nov 2021 09:46:11 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id AE7D21801FD for ; Tue, 23 Nov 2021 02:42:51 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 23 Nov 2021 02:42:51 -0800 (PST) Received: by mail-lf1-f47.google.com with SMTP id c32so90004899lfv.4 for ; Tue, 23 Nov 2021 02:42:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=EWhwI9oTwoprwuwcMvxmQshnpXAPzXPmGybW3edHZK8=; b=LQtehucNKFu/IHAz4/nHTuiAidXC497sIhIE/qzVDP81iunhSuf57I8MV1+ipYcLtN XXjdSajdimmdPCsd+G9gjJwkd7EzYVNh3/42NJuZBAZ8N3HLsXbkoNvgKRYICsWwcvJD V7G7qS48QtzEtjjBEsCOTYG+E3h1bZy+ONv+yDUwNhHdqH9+LQ99HvgkEhjbBHfh5uny l01q9QsJwtzc5pzCR1uN7uD8PU7AYhyCnPi5Aq+CrbvIwp3U4GZerYHavgg/FE9X7EOd 0MbFJw517dwdkBzBDXVu4zsK0DFzw+YnQUlWtyPpCP2jXbPeMqx/znSvaSXlw+w3zLkL ACKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=EWhwI9oTwoprwuwcMvxmQshnpXAPzXPmGybW3edHZK8=; b=1XvEEAfiYd9Pb/n0iKtgo20jTyvBFdNDVghuvq9xIj48pnjdseEmg4pCSvVdOpJLfh 7QahAh8vuXhP8vnK9NPn4h5P+MDzqZxsIiBp22xmIat/QrBVVzXZ1Dz3IFMbI4R3whMe UTq6Bsbc/ORVA+jmvnOMUfhlj9Olp1pEfGX/zmVhGvLlHIIHRBJ14cjUIUzQ10vwq5A0 d3YNiaY1kUPWjYyIseXhQDAO1KAcx0zgRvJXHHviQvSJQ+Wi+oSrDi54lduCu9N9eHQX VaUHLoa4krFb/3+v0ImQC7Y4poQeczQzyxdbVaoP2FaEG98Yqm80cDbe3WNo+RlI9N2W 6/Aw== X-Gm-Message-State: AOAM5300F2FnDWIuLmSCqjmQ/nAHRgv/dXlZwRPqiAHuRi/xpmKv9sfW kIg/Ocan39SpECz+hwC5JONK6wOG2JU= X-Google-Smtp-Source: ABdhPJy39Fh3FRqHMA2+P8osv33lf/4rLVqL6Sl+eWLGboHv8v9pd/ktjqvIqr1kdJL1OLS6zORzlQ== X-Received: by 2002:a05:6512:3182:: with SMTP id i2mr3553863lfe.241.1637664169126; Tue, 23 Nov 2021 02:42:49 -0800 (PST) Received: from [10.6.1.158] ([185.219.140.135]) by smtp.gmail.com with ESMTPSA id o11sm1190089ljc.100.2021.11.23.02.42.48 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Nov 2021 02:42:48 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\)) Date: Tue, 23 Nov 2021 11:42:47 +0100 References: <7f2f3814-6545-1d5b-cb44-607fff9f7edd@naderman.de> To: Daniele B via internals In-Reply-To: <7f2f3814-6545-1d5b-cb44-607fff9f7edd@naderman.de> Message-ID: <867A507F-4320-4341-AEA9-9C7523B5E742@gmail.com> X-Mailer: Apple Mail (2.3445.9.7) Subject: Re: [PHP-DEV] Sponsor link on github.com/php From: hallbergkim@gmail.com (Kim Hallberg) > On 22 Nov 2021, at 11:32 PM, Nils Adermann = wrote: >=20 > On 22.11.21 23:07, Kim Hallberg wrote: >>=20 >>> On 22 Nov 2021, at 10:53 PM, Sara Golemon wrote: >>>=20 >>> 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-y= our-repository >>>=20 >>> Pro: Gives appreciative users somewhere to send their appreciation = and the >>> project doesn't have to worry about all the tax implications. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> Looking forward to thoughts, >>> -Sara >>=20 >> What about a php.net/donate page? GitHub=E2=80=99s funding file works = with custom URLs. >>=20 >> 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. >>=20 >> The page wouldn=E2=80=99t need any forms or anything, a PR directly = to the page could work. >>=20 >> Thoughts? >>=20 >> Thank you, >> Kim. >>=20 >=20 > 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. >=20 > 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 >=20 > Cheers, > Nils. >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php >=20 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=E2=80=99re describing is using the GitHub sponsors platform, = that is not the same as adding PHP Foundation=E2=80=99s Open Collective to PHP=E2=80=99s = 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=E2=80=99t really need non-profit orgs like PHP = Foundation. As for linking to PHP Foundation=E2=80=99s 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=E2=80=99t 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=E2=80=99t 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-y= our-repository=