On Tue, Apr 10, 2012 at 10:12 PM, Stas Malyshev <smalys...@sugarcrm.com>wrote:
> Hi! > > > Well, technically it's discussion /and/ vote. I know we've been wanting > > to get out of the habit of "push first, ask later," which is precisely > > what RFC helps us avoid. Personally, I think any commits for a > > Nobody's pushing anything. We're talking about implementing it in a > fork, it's completely different thing. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > I must've missed that part. Who was it that said this would be a separate forked project? If so, then yeah obviously it's not up to us one way or another. And if he's just committing changes locally and/or pushing to an unmerged branch, then there's no harm because it's not actually touching the trunk. What I'm saying is that, before such changes are merged into the actual PHP 5.4 branch, the idea needs to be voted on through the RFC process. Besides, it's a better idea to wait anyway because the simple act of drafting the RFC helps the author to clarify exactly what s/he wants to do before jumping into the code. Furthermore, subsequent input from users may change the direction, forcing the author to rewrite code, which wastes time. And if the proposal is rejected, that person would've written all that code for nothing. So either way you look at it, it seems to me at least that drafting the RFC is the logical first step. --Kris
