With the GWT steering committee, Google goes from being a gatekeeper to a peer amongst equals, with the committee controlling the roadmap of GWT. "It will no longer be Google as a dictator," said Ray Cromwell, Google tech lead for GWT. He will serve as committee chairperson for the time being. Other companies represented on the committee include Vaadin, Sencha, and Red Hat, and other members include GWT advocates Thomas Broyer, Christian Goudreau, and Daniel Kurka. "We have to be responsive, and we have to think more about what other people [support]," in GWT, Cromwell said at the Google IO conference in San Francisco.

GWT features a software development kit with core Java APIs and widgets for writing AJAX applications in Java and compiling them to JavaScript. These applications can then run across multiple browsers. The committee already has had a couple of meetings and has decided to move the GWT repository from Subversion to Git. Cromwell said. GWT also moves to two official branches: a master dev line trunk, for testing out bleeding-edge capabilities, and a beta branch, which will hold new capabilities selectively taken from the dev line trunk branch.

Google's handing over control of GWT to the committee is similar to when IBM relinquished control of the Eclipse open source tools project, which is now under the jurisdiction of the , Cromwell acknowledged. "Eclipse is now more of a vibrant community than it was when only IBM controlled it."

GWT 2.5, the last Google-directed release of the toolkit, boasts a host of improvements. "Out of the box, with no changes to your code, you can just compile your application. You're going to get substantial code-size reduction," Cromwell said.