On Tue, Jun 10, 2025 at 4:43 AM Vincent de Lau <[email protected]> wrote:
> On Monday, June 9, 2025 at 9:21:33 PM UTC+2 Larry Garfield wrote: > > On Mon, Jun 9, 2025, at 2:00 PM, Korvin Szanto wrote: > <snip> > > 1. Removes Tidelift entirely and replaces it with direct contributions > > to OpenCollective, with provisions that answer to my original concerns > > around conflict of interest and raising funds from individuals > > 2. Allow for repaying Secretaries that so kindly have been paying out > > of pocket to sustain our mission > > 4. Clarifies when, how, how much, and to whom we disburse overfunding > > as well as codifying clearly what overfunding means > > These three seem entirely reasonable. > > > +1 > > I'm a bit surprised that repaying out-of-pocket expenses would not be allowed already. It might be a bit of a too strict interpretation of the current bylaws. The bylaw is currently quite clear in my mind: - PHP-FIG SHALL NOT pay individual contributors to PHP-FIG standards or other personnel, like Core Committee members, Secretaries, Project Representatives or working groups. and I don't think it's wise to start loosely interpreting things when it comes to money, it's easy enough to amend the bylaw to handle the case clearly. > > > 3. Grants the ability for Secretaries to create and maintain a > > print-on-demand swag shop if they so choose to allow individuals to > > contribute while spreading the PHP-FIG mission in their communities. I > > would definitely be in the market for PHP-FIG swag > > This is an interesting idea. I don't know how successful it would be, or > what we'd use any such revenue for, but I'm open to discussing it. However, > this is a much larger question than just cleaning up the Tidelift situation > so it should be kept to a separate discussion and separate vote. > > > I'm wondering if the effort is worth the hassle. This merch store is not a mandate as written, it's up to the Secretaries to decide if it's worth the hassle for them given that they'd be the ones on the hook to do the work. > Instead of doing this ourselves, maybe we should allow the promoting others who raise funds for PHP-FIG. For instance, we could point people to Andreas' store and have him donate the money via OpenCollective. Allowing others to use and sell our logo in swag introduces conflicts of interest, licensing, and oversight issues that I'd prefer we avoid. > The biggest challenge at the moment, IMHO, is not having a way to receive funds. I think that opening up the OpenCollective page for donations will help solve our direct financial needs quickly. I believe there are enough people here on the list that would gladly donate a couple of dollar. For instance, I would consider changing my standing donation to the PHP Foundation over to the FIG, knowing that any excess would end up there anyway. Like I mentioned above, we can't expedite this process fast enough to get ahead of the expenses since they were due last week to my knowledge. Given that we'll certainly reach our funding goal immediately once we open it up, and that we haven't been able to accept money at all up until this point, I'd prefer not expediting the process without a clear reason to do so. > -- > Regards, > Vincent > > > -- > 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/0a39f2eb-358f-4515-bac3-97c4eaef47ean%40googlegroups.com > <https://groups.google.com/d/msgid/php-fig/0a39f2eb-358f-4515-bac3-97c4eaef47ean%40googlegroups.com?utm_medium=email&utm_source=footer> > . > Best, Korvin -- 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/CANeXGWVpN1k%3DCQGKuAmFOhJkGCpxQf6Ys-9F%2BQJkusX2zkBRew%40mail.gmail.com.
