Commit responsibilities and Lines of Defense
aph at redhat.com
Tue Feb 22 10:16:33 UTC 2011
On 02/21/2011 08:01 PM, Kelly O'Hair wrote:
> On Feb 21, 2011, at 1:29 AM, Andrew Haley wrote:
>> On 02/18/2011 10:09 PM, Kelly O'Hair wrote:
>>> It is clear to us that we cannot make the system entirely "open",
>>> but we can provide a kind of portal
>>> (I hate that word), or view (a better word) into what is happening.
>>> Exposing what we legally can and
>>> hopefully providing enough information to make the system work for
>>> So what do you think? Any opinions out there?
>> This sounds like a big step forward, and a great way to show everyone
>> that Oracle is determined to work with the community.
> We recognize that a model where all changes must be shepherded through
> by an Oracle employee
> will not scale, so we are being motivated by a bit by how we can make
> it a true community
> contribution situation and also not overload the Oracle engineers with
> needless shepherding tasks.
That's very encouraging. This sounds like a very innovative approach to
working with the community, given that you have a half-open, half-closed
development environment. I hope we don't get too many "No, you can't do
that, but I'm not allowed to tell you why" situations.
More information about the build-dev