Of course. My +1 was for listing the compute capabilities. On Sep 28, 2010, at 2:42 PM, Jerry Chen wrote:
> I would rather hold off on announcing Java storage capabilities until Python > has the equivalent. > > Jerry > > On Sep 28, 2010, at 4:35 PM, Mike Mayo wrote: > >> +1 >> >> libcloud is more about a clean and simple design than a particular language. >> i think we/you should showcase the Java work as well as any other future >> languages that follow the libcloud design. >> >> >> On Sep 28, 2010, at 2:21 PM, Peter Haggar wrote: >> >>> This looks very good to me as well. I think this will highlight this work >>> and let people know that libCloud is a multi-language solution. >>> It's obvious that's the case with your new graphics. >>> >>> Peter >>> On Sat, Sep 25, 2010 at 8:51 AM, Sengor <[email protected]> wrote: >>> >>>> >>>> On 24/09/2010, at 9:38 AM, Eric Woods <[email protected]> wrote: >>>> >>>>> I propose that we recognize this maturing state in both the website and >>>> in the repository. I've drafted a revised homepage with additional charts >>>> to present Java's current support, much like what exists for python today. >>>> I've uploaded a snapshot of the proposal to JIRA: >>>> https://issues.apache.org/jira/secure/attachment/12455447/proposed_libcloud_homepage.zip. >>>> I'd also be willing to tweak the site where applicable to indicate Java's >>>> support. Thoughts? >>>> >>>> Proposed website update looks viable to me. Are there any plans to >>>> introduce storage cloud capabilities within the Python branch of libcloud? >>>> > Mike Mayo 901-299-9306 @greenisus Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at [email protected], and delete the original message. Your cooperation is appreciated.
