PHP technical committee RFC

[bukka]

This is just to leave comments on the specific parts of text for PHP technical committee RFC: https://wiki.php.net/rfc/php_technical_committee

[Girgias]

Thanks for writing words!

I think a couple technicalities should be thought about first before being released to the public in how membership is handled.

But in general looks good :)

[dstogov]

This looks great.

[Girgias]

Looks mostly good to me! A couple of minor comments and nits but then I think it should be good!

[weierophinney]

I've provided a few changes to either clean up grammar (I'm a native English speaker), or to make the text more clear.

I've also provided some questions that I think are likely to be asked earlier rather than later, and which you might want to address before taking it to the internals list.

[weierophinney]

Suggested change

	This RFC proposes an introduction of the PHP Technical Committee (TC) that would decide about all technical aspects of
	php-src when there is a disagreements between core developers.
	This RFC proposes an introduction of the PHP Technical Committee (TC) that would mediate code contribution conflicts between core developers proposing or committing changes to php-src.

"Decide about all technical aspects" is vague and will be argued back and forth. The goal is to mediate conflict which arise due to changes to php-src.

[bukka]

The technical aspects are actual defined so it should be clear what it is and if it is not, we should update the definition. The current statement is more vague IMO as it basically covers RFC proposed changes which is explicitly limited later in the RFC. It means that TC should never decide about commits that introduce user visible changes unless there are technical issues with that.

[bukka]

Btw. I'm fine if this gets rephrased in the way that will still make clear that the RFC user visible changes are not part of the decision.