Re: [RFC] Working Groups
| From: | Tim Düsterhus | Date: | Mon, 08 Jun 2026 13:56:12 +0000 |
| Subject: | Re: [RFC] Working Groups | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131169@lists.php.net to get a copy of this message | ||
Hi
Am 2026-05-26 18:15, schrieb Ben Ramsey:
I'm opening discussion on an RFC to create a policy for PHP project working groups: https://wiki.php.net/rfc/working_groupsThank you for the RFC. Purely policy-wise, any policy RFC should consist of a PR to https://github.com/php/policies/ as the “source of truth” with the RFC text itself only being a stub that references the PR and that provides supplementary information. See: https://wiki.php.net/rfc/policy-repository As for the RFC itself, as I think I had already mentioned on social media back then, it is unclear what value this additional policy brings. Given that everything relating to a working group needs to go through an RFC anyways (which is a good and important rule), I don't quite see why we would need another policy on top of the (policy) RFC process itself. For language RFCs, RFC authors are already working with the list and their co-authors to figure out the best possible version for a given proposal without any official “working group”. In practice, these kinds of RFCs work best when done with a very small team of “subject matter experts” that have done their research before proposing the RFC and where the discussion only makes minor adjustments. This leaves the non-language tasks, such as marketing. I expect there to be a need for less than a handful of this kind of “working group” or “team”, which I believe can easily be handled with the existing RFC process. In fact Roman's social media RFC that you referenced in your email is already proposing to create a “working group” (or officially delegating responsibilities) even without the featured RFC being accepted. Best regards Tim Düsterhus