Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44321
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: Derick Rethans <derick@php.net>,
 'PHP Internals' <internals@lists.php.net>
Message-ID: <0FCAD6EF-803C-43BE-B2DB-09F5AE4D66ED@pooteeweet.org>
To: Stanislav Malyshev <stas@zend.com>
In-Reply-To: <4A37EA3F.3010704@zend.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 16 Jun 2009 21:02:09 +0200
References: <4A31462B.1070302@zend.com> <alpine.DEB.2.00.0906161005210.5761@kossu.ez.no> <E313C99E-EB76-490F-917D-C4D1A8648AB5@pooteeweet.org> <4A37CEC2.7050001@zend.com> <0FD8F38A-205D-4B79-AE8A-E7AFE475BC17@pooteeweet.org> <4A37EA3F.3010704@zend.com>
Subject: the role of RM's (as I see it)
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 16.06.2009, at 20:53, Stanislav Malyshev wrote:
> We don't need to delay it if we decide to commit my (incomplete) fix  
> now. Anyway, it's your decision, one of the three: 1. leave it as  
> is, 2. commit incomplete fix now, 3. wait for complete fix. I agree  
> 3 is the worst, I'd go with 2 but if you decide to go with 1 that's  
> OK.


Just to clarify how I see the job of an RM. Its not chief decision  
maker. Its decision facilitator. Only when with reasonable amount of  
time and input from the community no agreement/compromise can be  
found, I can see the RM act as a tie breaker. As such I prefer to get  
feedback from as many people as possible in a clear and concise manner  
that makes it easy for us RM's to understand the view points of the  
community, so that we can then simply sum of the conclusion of the  
discussion and ask someone to make the necessary changes.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org