I've got to throw in a plug for the Spiffy UI framework. It's a set of build utilities, security libraries, REST integration and a whole lot more on top of GWT. It scales up well for large teams and large projects and let's you build awesome web applications in a strongly typed environment. http://www.spiffyui.org/

I've worked in a virtual team for over 10 years and the short answer is that making it work takes work. Most engineers are solitary and it takes a lot of communication to keep a virtual team together. I wrote a book about it. The One Minute Commute. It is available free.

I completely understand what you mean here. I was really torn about what to say. I went the way I did because I was the creator of the project. I wanted to highlight not only programming skills, but organizational and product design skills as well. Designing an open source project and getting it off the ground takes a different set of skills than contributing to an existing project. If you're the creator of the project you should highlight that. Having said all of that, I really like your copy. It is tight and clear while doing a good job describing what you did.

Keeping a portfolio of your open source contributions is a wonderful idea. Creating a narrative really shows that you can speak well about your projects. This is what hiring managers are looking for, strong coders who can speak English and communicate well.