The border between JavaOne and CommunityOne is not completely clear to me. Lots of Java technology is currently Open Source and is
developed inside communities. The combination of open source, open development and Java is not a marginal phenomenon anymore.
There was a whole GlassFish track at CommunityOne. During the JavaOne conference, there will be more sessions on GlassFish though.
Important to notice, however, is the growing attention for CommunityOne. If I understood it correctly, there were 3000 attendees compared with 2000 last year.
It is not always clear how projects in a community should be organized. Who is allowed to do what? How do you find contributors for your project?
How can you maintain quality? These are typical issues in software development, and the Java Community world should address these as well.
More specifically, it is a challenge to encourage developers to spend some time on an open source java project that doesn't generate immediate revenues.
Large companies can address this more easily: if they allocate one person on an open-source project, it doesn't have a big impact on their organization.
For smaller companies as LodgON, however, this is more tricky. Assigning one person full-time to an open-source project, has a big impact on the ongoing projects and operations.
In the end, we all expect that working on an open-source project somehow
generates revenue, it can be cash or recognition or something else.
Johan's blog 