On Sat, 2019-11-02 at 19:40 +0100, Joe Watkins wrote: > I would like to question the reasoning behind wanting to "own" the > RFC content: We don't require any such thing for any other kind of PR > although we say we require a patch on bugsnet, we actually don't > require it. So, I have a hard time telling the difference between a > PR for an RFC and a PR for a bugfix or enhancement. > > Can anyone tell the difference ?
In a bug fix or enhancement the relevant information is in the patch, which in the end lives in php-src.git. If a patch isn't self- explanatory it probably needs an RFC as reasoning. That reasoning shall live in a central place to be found by future generations. And some historic context (do with it what you want :-) ) on why php.net instead of GitHub: When we moved to git I (among others) pushed for using our own infrastructure we control, and not binding the process to an external entity. PHP has seen other platforms like sourforge come and go and migrated from CVS, to svn, to git so other platforms coming and going and versioning systems come and go is likely. While GitHub under current Microsoft probably is more likely to stay than the young startup from years back. :-) (that aside from GH requiring accounts on that platform, eventually blocking countries etc.) johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
