I much prefer a middle way approach rather than the nuclear option (i.e., the community starting their own "J2" conference). The problem as I see it though is the sheer size of Oracle OpenWorld makes it very difficult for JavaOne to co-exist with that event. I do accept the practical necessity to have them in close proximity. However, the use of adjacent hotels for the JavaOne 2010 sessions was a logistical nightmare and dismal failure this year. Since holding a separate JavaOne conference at a different time is a non-starter in discussions with Oracle, I propose here some slight modifications to the current organization of the combined events that I believe would significantly improve the situation.
Instead of relegating all the developer sessions to the hotels, the primary goal of this proposal is to move the developer sessions back to Moscone. The way I propose accomplishing this is by having the JavaOne developer sessions start one day earlier on Saturday and the OpenWorld sessions shift their start/end dates by one day. The old format was:
- User Group Sunday
- Oracle Open World/JavaOne on Monday-Thursday
- JavaOne on Saturday-Sunday
- User Group Monday
- Oracle OpenWorld on Tuesday-Friday
By the way, this would allow Oracle Develop and a new MySQL conference to also move back to Moscone for the weekend. There is plenty of room at Moscone to co-locate all three developer focused conferences. They could follow the same overlapping schedule as JavaOne. I truly believe this is a middle way approach that could work. My biggest logistical fear is that it is already too late to change the Moscone reservation for next year's event to include the additional days required to do this.
As an aside, a JavaOne pass could have the same benefits as the Discover Pass this year did for OpenWorld. That way, JavaOne attendees that choose to hang around could still network with the OpenWorld attendees later in the week.