<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 21, 2011, at 1:29 AM, Andrew Haley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 02/18/2011 10:09 PM, Kelly O'Hair wrote:<br><br><blockquote type="cite">But there have been some roadblocks for the open source community.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It has been observed (for a long time now) that:<br></blockquote><blockquote type="cite">* The Mercurial jcheck extension needs to be open sourced<br></blockquote><blockquote type="cite">* The bug tracking system needs to be completely open<br></blockquote><blockquote type="cite">* We need an open build and test system for the OpenJDK developers who don't have access to all the systems<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We are working on it. And of course you have heard that before, but we are, really.<br></blockquote><br>That's very good news, especially the bug tracking system. I thought<br>that the plans to open that up had been abandoned with the Oracle<br>acquisition of Sun.<br></div></blockquote><div><br></div>No, we just have a different internal bug tracking system to interface with now.</div><div>I've asked the person in charge to consider discussing the plans more publicly.</div><div><br><blockquote type="cite"><div><br><blockquote type="cite">It's that last item that involves myself and a group of Oracle engineers in Stockholm, hopefully we<br></blockquote><blockquote type="cite">can come up with a solution that works for everybody. I have tentatively named it BAT for<br></blockquote><blockquote type="cite">Build And Test, but it is just in the infancy stage, nothing official yet. But we would like some input.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The intent would be to accept repository paths, tips, and changeset bundles or diffs (for test runs),<br></blockquote><blockquote type="cite">run it through a matrix of builds and tests, and return back status or even do the Push if requested.<br></blockquote><blockquote type="cite">Internally, we have such a system, but it's not clear exactly how much we can reuse.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Due to the proprietary nature of some of the tests and systems, and also a need for security, it's not<br></blockquote><blockquote type="cite">exactly clear how much data we can expose. But we should be able to run selected and critical tests for<br></blockquote><blockquote type="cite">everyone, and of course verify there have been no build issues introduced by a change.<br></blockquote><br>Fabulous.<br><br><blockquote type="cite">When all goes well, that is one thing, but when it doesn't and non-open tests fail, then it gets tricky.<br></blockquote><blockquote type="cite">(yeah yeah we should open source the tests, that just can't happen in all cases).<br></blockquote><br>It'll be tricky if some crucial flaw is revealed by a private test. I<br>suppose in that case that an Oracle engineer will have to analyse the<br>problem.<br></div></blockquote><div><br></div>Yes, and at that point the question will be, 'can we open up this test' or 'can we find an open replacement'</div><div>or 'can we at least create an isolated testcase we can make open'.</div><div><br><blockquote type="cite"><div><br><blockquote type="cite">It is clear to us that we cannot make the system entirely "open", but we can provide a kind of portal<br></blockquote><blockquote type="cite">(I hate that word), or view (a better word) into what is happening. Exposing what we legally can and<br></blockquote><blockquote type="cite">hopefully providing enough information to make the system work for everyone.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">So what do you think? Any opinions out there?<br></blockquote><br>This sounds like a big step forward, and a great way to show everyone<br>that Oracle is determined to work with the community.<br></div></blockquote><div><br></div>We recognize that a model where all changes must be shepherded through by an Oracle employee</div><div>will not scale, so we are being motivated by a bit by how we can make it a true community</div><div>contribution situation and also not overload the Oracle engineers with needless shepherding tasks.</div><div><br></div><div>Of course I have to clarify,</div><div><b><i> The views expressed in this email are my own and do not necessarily reflect the views of Oracle.</i></b></div><b><i><div><br></div></i></b><div><div>Everything does take time. ;^)</div><div><br></div><div>-kto</div><div><br><blockquote type="cite"><div><br>Andrew.<br></div></blockquote></div><br></div></body></html>