Return-Path: Delivered-To: apmail-incubator-libcloud-archive@minotaur.apache.org Received: (qmail 35525 invoked from network); 20 May 2010 20:19:39 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 May 2010 20:19:39 -0000 Received: (qmail 52210 invoked by uid 500); 20 May 2010 20:19:39 -0000 Delivered-To: apmail-incubator-libcloud-archive@incubator.apache.org Received: (qmail 52186 invoked by uid 500); 20 May 2010 20:19:39 -0000 Mailing-List: contact libcloud-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: libcloud@incubator.apache.org Delivered-To: mailing list libcloud@incubator.apache.org Received: (qmail 52176 invoked by uid 99); 20 May 2010 20:19:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 May 2010 20:19:39 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=10.0 tests=AWL,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul@querna.org designates 209.85.221.172 as permitted sender) Received: from [209.85.221.172] (HELO mail-qy0-f172.google.com) (209.85.221.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 May 2010 20:19:32 +0000 Received: by qyk2 with SMTP id 2so308413qyk.20 for ; Thu, 20 May 2010 13:19:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.235.202 with SMTP id kh10mr188470qcb.78.1274386751247; Thu, 20 May 2010 13:19:11 -0700 (PDT) Received: by 10.229.239.205 with HTTP; Thu, 20 May 2010 13:19:11 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 May 2010 13:19:11 -0700 Message-ID: From: Paul Querna To: libcloud@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [libcloud] Java Skeleton Available On Thu, May 20, 2010 at 12:39 PM, Adrian Cole wrote: > Is there anyone who isn't from IBM that would like to add a java or C > rewrite of libcloud to the project? it doesn't matter where someone works in apache projects. I don't believe this is moving the discussion forward by somehow devaluing someones comments because of their employer. I don't appreciate your continued down-trodden view of people trying to contribute to libcloud -- I understand you have your own project, great, but by the same token, you aren't a libcloud developer either, and if the people who are involved in libcloud do want to do something, you don't need to rain on their parade. Thanks, Paul > On Thu, May 20, 2010 at 12:24 PM, Peter Haggar wrote= : > >> I think a Java version makes sense and would like to contribute to it. >> >> >too early to create fragmentation in the cloud communities. >> That's exactly what I am trying to avoid and why I think Eric's suggesti= on >> is sensible. =C2=A0There's too much fragmentation now and his idea is a = way to >> coalesce some of that under one umbrella. >> >> >Libcloud is undeniably python focused, and Java doesn't make sense here= . >> No argument that it is python focused today, but the question is does it >> make sense to expand to other languages? =C2=A0I think the answer is Yes= because >> then there is a single API abstraction that supports a wide variety of I= aaS >> vendors in multiple languages. =C2=A0Can you explain why that doesn't ma= ke >> sense? >> >> >I suggest joining a community like jclouds >> Again, the goal is a single API abstraction, not multiple. =C2=A0Moving = this to >> jclouds would create fragmentation and would require users to use the >> libCloud API for an IaaS abstraction if they are coding in Python, but a >> different IaaS API if they use Java. =C2=A0Presumably if the community w= anted to >> add other languages you'd suggest yet another API? =C2=A0That makes no s= ense. >> I'd prefer one API. >> >> >...and find it a bad fit, submit your apache incubator proposal. >> I would like to avoid that as that creates fragmentation. >> >> Peter >> >> On Thu, May 20, 2010 at 2:14 PM, Adrian Cole wrote: >> >> > My thoughts are its too early to create fragmentation in the cloud >> > communities. =C2=A0Libcloud is undeniably python focused, and Java doe= sn'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" wrote: >> > >> > Hey guys, >> > >> > I've been following this discussion about libcloud's future direction >> very >> > closely, and thank you all for the great input. =C2=A0I'm trying to ma= ke sense >> > of >> > all this and how it relates to the Java development. =C2=A0I'm still v= ery >> > interested in developing a Java code base for libcloud, but I'm not >> getting >> > a clear sense of the community's support. =C2=A0I, of course, don't wa= nt 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 >> > >> >