By seanharris on Jul 22, 2009
I have been following Project Kenai for some time now. Although it a long while since I have written code in anger (or for a living unless you count the occasional hacking and scripting) my constituency with my customer consists largely of developers, technologists and solutions architects and I want to keep abreast of emerging technologies that may interest or affect them. Kenai provides an interesting set of services to support open communities and open development. Hopefully in the future they will extend this functionality to offer private communities to major enterprises. While I am a huge support of Open Source and Open Development I remain unconvinced that all enterprises are ready for open source development or that it is right for them. Given that these development teams share many requirements with open source development projects having large loosely coupled development teams distributed around the planet that need to collaborate closely around a development project.
Anyway I digress from the main purpose of this post.
At JavaOne they demonstrated a then late beta version of Netbeans 6.7 that has since become the production version. One of the new features of this release was integration between NetBeans and Project Kenai. Allowing developers to be able to open their open source projects within the IDE and develop code, track and fix bugs, collaborate and even in the future deploy applications to the cloud. Once again a great example of "the network is the computer".
Again I think that this kind of working methodology applied to distributed (but closed) enterprise development teams could be a very powerful tool. Also consider the current threat from H1N1. Even if your entire development team is co-located in the same office if there is a pandemic and people are stopped from coming into the office with this development model then development can continue without interruption with the team distributed. Worth consideration at least.