incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Woods <>
Subject Re: [libcloud] Java Skeleton Available
Date Mon, 24 May 2010 21:21:19 GMT
Hey guys,

While we continue to work out details of the repository, mailing list, etc,
I've posted an update to the Java framework to JIRA:

I'd also like to cast my vote:

> libcloud is a python project and should remain purely python
> throughout incubation
YES []
NO [X]

> libcloud is an abstraction interface for various cloud hosting
> service providers, the current implementation happens to be Python,
> but other bindings for Java etc will make libcloud more convenient
NO [ ]

For the time being, I agree with Matt's approach of housing a separate but
parallel sandbox for Java development.  This will enable community
observation and feedback while the framework is developed.


While we iron out the details of the repository, mailing list, etc, I've
posted an update the Java framework to JIRA:

On Mon, May 24, 2010 at 12:13 PM, Matt Hogstrom <> wrote:

> Another approahc would be to put the code into a "sandbox" in the libcloud
> tree (your proposal of a parallel environment) and see how things go?  If
> Eric is ammenable (since he's offering the code) to work in parallel the
> community would get a first hand perspective on what things would look like.
>  If it doesn't work out because either party isn't happy you delete the
> sandbox, Eric chooses another project and it was a noble attempt.
>  Otherwise, the two implementations don't look so bad, people are interested
> in consuming them and the community grows.
> Just my 2c
> On May 22, 2010, at 1:07 AM, Jerry Chen wrote:
> >
> > It would be great to see the Java libcloud enthusiasts begin committing
> code to a central repository outside of Apache Incubator while this issue
> stalls. There might be value in an external mailing list, or at least a way
> for everyone here to see exactly how much support there is, both code-wise
> and discussion-wise.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message