Re: [PHP-DEV] Defining the PHP Group

This is only part of a thread. view whole thread
  107117
September 15, 2019 19:33 smalyshev@gmail.com (Stanislav Malyshev)
Hi!

> Does anyone object to any of those words ?
Yes. I do not think precommitting to implement anything that has been put on wiki and passed the vote is a good thing. Its a good conflict resolution mechanism when we're talking about where or not to implement certain technical feature. But IMO it would be terrible as a sole governance mechanism for the whole project.
> Do we need to vote on changing the introduction (I'm happy to start an rfc > for this, if necessary) ?
I don't think RFCs were meant to essentially remake all project governance structure. They were meant for solving technical questions, not governance model. I am not sure which way would be the best (haven't thought about it) but certainly neither just putting some words on wiki nor voting on it within the RFC process looks like a good way to do it. -- Stas Malyshev smalyshev@gmail.com
  107118
September 15, 2019 20:05 cmbecker69@gmx.de ("Christoph M. Becker")
On 15.09.2019 at 21:33, Stanislav Malyshev wrote:

>> Do we need to vote on changing the introduction (I'm happy to start an rfc >> for this, if necessary) ? > > I don't think RFCs were meant to essentially remake all project > governance structure. They were meant for solving technical questions, > not governance model.
Then we should undo all changes (as far as possible) caused by the RFCs listed in the Process and Policy section[1], probably starting with the Voting (aka. RFC) process RFC itself, which by the way, states as introduction since its very first version from 2011 (emphasis mine): | This document describes the procedure to propose an *idea* for | adoption by the PHP community and decide if the community accepts or | rejects the idea. Thanks, Christoph [1] <https://wiki.php.net/rfc#process_and_policy>
  107119
September 15, 2019 20:22 smalyshev@gmail.com (Stanislav Malyshev)
Hi!

> Then we should undo all changes (as far as possible) caused by the RFCs > listed in the Process and Policy section[1], probably starting with the > Voting (aka. RFC) process RFC itself, which by the way, states as > introduction since its very first version from 2011 (emphasis mine): > > | This document describes the procedure to propose an *idea* for > | adoption by the PHP community and decide if the community accepts or > | rejects the idea.
Proposing an idea for adoption is not the same as precommitting on implementing anything that has been voted on, including whole governance of the project. I did not suggest undoing anything, and there's really no need to put words in my mouth, I can speak for myself. Thanks, -- Stas Malyshev smalyshev@gmail.com