Thursday, June 11, 2009 | 2:36 PM
If you've been looking at our code repository history at all, you might be forgiven for assuming that Antoine and I are the only ones who work on O3D code, and that we're really sporadic about when we submit code (but look at how much we get done!).
Since our launch, we've been syncing our internal repository intermittently with the public Google Code repository while we made the transition to some new tools and did some rearranging. Now that transition is complete.
The plan for O3D in the near future is to become more closely integrated into Chromium (while continuing to support plugins for other browsers). To make this integration easier, our code now has a new home in the Chromium.org Subversion repository. From now on, we're going to stop doing merely intermittent pushes and just do our daily work directly on the public repository, so you'll get to see all the changes as they happen, and you can follow along (and maybe now you'll see some other developers do some work! Or maybe you'll be one of those developers! ).
If you want to download the O3D source, or have downloaded it in the past, you'll want to use the Chromium server by following our updated build instructions. Don't worry, you don't need to download all of Chromium to build O3D.
We will continue to use our current issue tracker on the code.google.com site to track and log bugs and feature requests so you can see if they are being worked on, or pick one out to work on yourself.
If you've been itching to fix one of those bugs, you can now submit patches to our source using the same process that Chromium developers use. Look at the Chromium guidelines for patch submission if you're interested in contributing. Some things, like the buildbots, aren't set up for O3D yet, but will be available in the future. The reviewer mailing list for o3d is firstname.lastname@example.org, if you are looking for a reviewer.
The code on the Google Code site will be available for some time to come, but will not be updated, and eventually we'll just redirect visitors directly to the Chromium repository. It currently contains the latest code as of Friday May 29th.
The API documentation will remain where it is.
Posted by Greg Spencer, Senior Software Engineer