Hi all,

I'd like to open for discussion the state of a multilingual Libcloud and what 
it means to be part of the official repository.

While we have kept the Java port in its own sandbox, I think there needs to be 
more discussion and reconciliation of APIs before we "officially" endorse the 
Java port.

How can bring the Java port closer to the feature set of the original API? How 
can we share test suites so there is coverage outside of Python?

Further down the road, I can see two scenarios for a Python and Java Libcloud 
existence:
1) both fall under the larger Libcloud umbrella and work together to maintain a 
common goal; tests are written, features are developed and matured in Python 
and then adopted/ported elsewhere; or,
2) the Java port becomes unofficially associated with Libcloud and adopts a 
different name to avoid confusion.

Hope that makes sense.

Thanks,
Jerry

Reply via email to