My thoughts are its too early to create fragmentation in the cloud communities. Libcloud is undeniably python focused, and Java doesn't make sense here. I suggest joining a community like jclouds or dasein where you don't have to change it into something different. Im not sure what you are so worried about, as IBM cloud is an easy api and on our todolist. If you actually try an existing java community and find it a bad fit, submit your apache incubator proposal.
My 2p Adrian On May 20, 2010 10:36 AM, "Eric Woods" <[email protected]> wrote: Hey guys, I've been following this discussion about libcloud's future direction very closely, and thank you all for the great input. I'm trying to make sense of all this and how it relates to the Java development. I'm still very interested in developing a Java code base for libcloud, but I'm not getting a clear sense of the community's support. I, of course, don't want to spend the development time and effort writing a Java version of libcloud if the community doesn't support it. What are your thoughts on Java development as a sub-project of Apache libcloud? Thanks, - Eric
