I'm opening discussion on an RFC to create a policy for PHP project working groups:

https://wiki.php.net/rfc/working_groups

The RFC "establishes a framework for the creation, operation, and dissolution of working groups within the PHP Project. It provides a structured, transparent mechanism for managing discrete projects or activities (whether technical, infrastructural, or otherwise) undertaken by the Community. As such, it ensures that each working group is clearly chartered, time-bound, and actively led, thereby addressing organizational gaps that often leave new and existing volunteers uncertain about who to talk to or how to contribute."

I created the first draft of this RFC a few years ago but decided against formally proposing and discussing it on the list. Roman's recent social media policy RFC[1] made me change my mind. I think the time for defining formal working groups in the PHP project is here.

Under a working groups policy, someone could propose a marketing communications working group to manage and make decisions about how the PHP project communicates with its community.

Another example is that someone (i.e., Derick) could propose an infrastructure working group for managing all the systems, credentials, etc. for the PHP project. This group already exists informally, but a working group would formalize it. (A potential charter for such a working group is provided as an example in the RFC.)

Cheers,
Ben


[1]: https://wiki.php.net/rfc/social-media-policy

Reply via email to