[PROPOSAL] Libcloud Project

[Paul Querna-6]

Hi,

I would like to propose incubating the existing Libcloud project to
join the ASF:

Proposal  Wiki: <http://wiki.apache.org/incubator/LibcloudProposal>

Libcloud is a unified Python API around many common cloud services
provider, and I believe it could benefit greatly by joining the Apache
Software Foundation.  I also believe the ASF needs more Python
projects, and more projects involved in the developing cloud
infrastructure.  We still need a few mentors, so feel free to signup
:-)

We would appreciate feedback and comments on the proposal.

Full proposal is bellow.

Thanks,

Paul

------------------------
Libcloud, a unified interface to the cloud

Abstract

libcloud (<http://www.libcloud.org>) is a pure python client library
for interacting with many of the popular cloud server providers. It
was created to make it easy for developers to build products that work
between any of the services that it supports.

Proposal

    * Provide unified API for manipulating servers instances across
many hosting providers who provide an API to manipulate instances.
Current API includes: list, reboot, create, destroy, list images, list
sizes.

    * (future) Provide utilities for manipulating and creating server
images in many formats. (See the independent Stacklet project for
ideas)

    * (future) Provide unified API for storing large objects on
popular hosting provider storage APIs.

Background

While there are some projects to create open standards for
interoperability within the cloud, most have failed to gain widespread
adoption. Libcloud takes the approach of exposing a unified API to
cover multiple vendor's APIs, and in the future to support standard
APIs, assuming they become prevalent.

Rationale

There is a strong need in the developing cloud infrastructure for a
community supported, high quality, and vendor independent tool set for
managing servers and their resources. When new servers are just an API
call away, traditional infrastructure models are changing quickly.
Having a good library built around Apache's values and tradition will
enable new server infrastructure to evolve much more quickly.

Initial Goals

Libcloud is an existing open source project, with patches from many
different contributors. We view the moving to Apache as a way to
improve this community, and look into future APIs around creating
server images and large object storage.

Current Status

Libcloud is already open source under the ASL 2.0:

    * Libcloud Website <http://www.libcloud.org>
    * Libcloud Mailing Lists <http://groups.google.com/group/libcloud>
    * Libcloud Source Control <http://github.com/cloudkick/libcloud>

Meritocracy

Libcloud has involvement from members of both the ASF and other open
source projects. Communication is driven by both IRC and E-Mail lists.

Community

Currently libcloud has several contributors, but not a large user
community other than a few companies. We would like to increase our
userbase as part of the incubator process.

Core Developers

Alex Polvi who wrote most of the original code is familiar with open
source from working at OSUOSL and at Mozilla. Tom Davis drove much of
the re factoring of the initial code base. Jed Smith, Ivan Meredith,
Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all
contributed mainly to developing provider specific drivers.

Alignment

Currently there are not many Apache communities involved with cloud
computing or python based infrastructure. We believe introducing such
a community is a good thing for the Apache Software Foundation.

Known Risks

Orphaned products

libcloud is being used actively by Cloudkick to develop services. It
is a core part of our ongoing infrastructure improvements.

Inexperience with Open Source

libcloud was open sourced in July 2009, during OSCON. Core
contributors include former employees of Mozilla and an ASF member.

Homogenous Developers

Much of the initial development was done by Cloudkick, but much of the
core design was re-factored by the community, and many of the drivers
for each provider have been contributed by 3rd parties.

Reliance on Salaried Developers

The majority, but not all, of the developers are paid by their
employer to work on libcloud at this time.

Relationships with Other Apache Products

Libcloud doesn't share many attributes with existing Apache projects
due to it being in Python and addressing a new need.

A Excessive Fascination with the Apache Brand

Libcloud project seeks to build a last community around cloud API
interoperability, and is not fascinated with any short term gains of
being associated with the Apache Brand.

Documentation

TODO: links to related material on Cloud APIs/interop (?)

Initial Source

Initial source is contained completely inside the libcloud github repository.

External Dependencies
    * zope.interface
    * For Python =< 2.5, a JSON Parser such as SimpleJSON is required.

Cryptography

Uses standard Python APIs for SSL/HTTPS.

Required Resources

Mailing lists

    * libcloud-dev
    * libcloud-commits
    * libcloud-private

Subversion

    * https://svn.apache.org/repos/asf/incubator/libcloud

Issue Tracking

    * JIRA (LCLD)

Initial Committers

    * Alex Polvi <alex polvi.net>
    * Dan Di Spaltro <dan.dispaltro gmail.com>
    * Ivan Meredith <ivan ivan.net.nz>
    * Jed Smith <jsmith linode.com>
    * Jeremy Orem <jeremy.orem gmail.com>
    * Jerry Chen <github jcsalterego.otherinbox.com>
    * Paul Querna <pquerna apache.org>
    * Tom Davis <tom dislocatedday.com>

Sponsors

Champion

    * Paul Querna

Nominated Mentors

    * Paul Querna

Sponsoring Entity

    * Incubator PMC

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[gavin-105]

This looks interesting, I'd be happy to help Mentor and have already put my
name down.

Gav...

> -----Original Message-----
> From: Paul Querna [mailto:paul@...]
> Sent: Tuesday, 27 October 2009 5:00 PM
> To: general@...
> Subject: [PROPOSAL] Libcloud Project
>
> Hi,
>
> I would like to propose incubating the existing Libcloud project to
> join the ASF:
>
> Proposal  Wiki: <http://wiki.apache.org/incubator/LibcloudProposal>
>
> Libcloud is a unified Python API around many common cloud services
> provider, and I believe it could benefit greatly by joining the Apache
> Software Foundation.  I also believe the ASF needs more Python
> projects, and more projects involved in the developing cloud
> infrastructure.  We still need a few mentors, so feel free to signup
> :-)
>
> We would appreciate feedback and comments on the proposal.
>
> Full proposal is bellow.
>
> Thanks,
>
> Paul
>
> ------------------------
> Libcloud, a unified interface to the cloud
>
> Abstract
>
> libcloud (<http://www.libcloud.org>) is a pure python client library
> for interacting with many of the popular cloud server providers. It
> was created to make it easy for developers to build products that work
> between any of the services that it supports.
>
> Proposal
>
>     * Provide unified API for manipulating servers instances across
> many hosting providers who provide an API to manipulate instances.
> Current API includes: list, reboot, create, destroy, list images, list
> sizes.
>
>     * (future) Provide utilities for manipulating and creating server
> images in many formats. (See the independent Stacklet project for
> ideas)
>
>     * (future) Provide unified API for storing large objects on
> popular hosting provider storage APIs.
>
> Background
>
> While there are some projects to create open standards for
> interoperability within the cloud, most have failed to gain widespread
> adoption. Libcloud takes the approach of exposing a unified API to
> cover multiple vendor's APIs, and in the future to support standard
> APIs, assuming they become prevalent.
>
> Rationale
>
> There is a strong need in the developing cloud infrastructure for a
> community supported, high quality, and vendor independent tool set for
> managing servers and their resources. When new servers are just an API
> call away, traditional infrastructure models are changing quickly.
> Having a good library built around Apache's values and tradition will
> enable new server infrastructure to evolve much more quickly.
>
> Initial Goals
>
> Libcloud is an existing open source project, with patches from many
> different contributors. We view the moving to Apache as a way to
> improve this community, and look into future APIs around creating
> server images and large object storage.
>
> Current Status
>
> Libcloud is already open source under the ASL 2.0:
>
>     * Libcloud Website <http://www.libcloud.org>
>     * Libcloud Mailing Lists <http://groups.google.com/group/libcloud>
>     * Libcloud Source Control <http://github.com/cloudkick/libcloud>
>
> Meritocracy
>
> Libcloud has involvement from members of both the ASF and other open
> source projects. Communication is driven by both IRC and E-Mail lists.
>
> Community
>
> Currently libcloud has several contributors, but not a large user
> community other than a few companies. We would like to increase our
> userbase as part of the incubator process.
>
> Core Developers
>
> Alex Polvi who wrote most of the original code is familiar with open
> source from working at OSUOSL and at Mozilla. Tom Davis drove much of
> the re factoring of the initial code base. Jed Smith, Ivan Meredith,
> Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all
> contributed mainly to developing provider specific drivers.
>
> Alignment
>
> Currently there are not many Apache communities involved with cloud
> computing or python based infrastructure. We believe introducing such
> a community is a good thing for the Apache Software Foundation.
>
> Known Risks
>
> Orphaned products
>
> libcloud is being used actively by Cloudkick to develop services. It
> is a core part of our ongoing infrastructure improvements.
>
> Inexperience with Open Source
>
> libcloud was open sourced in July 2009, during OSCON. Core
> contributors include former employees of Mozilla and an ASF member.
>
> Homogenous Developers
>
> Much of the initial development was done by Cloudkick, but much of the
> core design was re-factored by the community, and many of the drivers
> for each provider have been contributed by 3rd parties.
>
> Reliance on Salaried Developers
>
> The majority, but not all, of the developers are paid by their
> employer to work on libcloud at this time.
>
> Relationships with Other Apache Products
>
> Libcloud doesn't share many attributes with existing Apache projects
> due to it being in Python and addressing a new need.
>
> A Excessive Fascination with the Apache Brand
>
> Libcloud project seeks to build a last community around cloud API
> interoperability, and is not fascinated with any short term gains of
> being associated with the Apache Brand.
>
> Documentation
>
> TODO: links to related material on Cloud APIs/interop (?)
>
> Initial Source
>
> Initial source is contained completely inside the libcloud github
> repository.
>
> External Dependencies
>     * zope.interface
>     * For Python =< 2.5, a JSON Parser such as SimpleJSON is required.
>
> Cryptography
>
> Uses standard Python APIs for SSL/HTTPS.
>
> Required Resources
>
> Mailing lists
>
>     * libcloud-dev
>     * libcloud-commits
>     * libcloud-private
>
> Subversion
>
>     * https://svn.apache.org/repos/asf/incubator/libcloud
>
> Issue Tracking
>
>     * JIRA (LCLD)
>
> Initial Committers
>
>     * Alex Polvi <alex polvi.net>
>     * Dan Di Spaltro <dan.dispaltro gmail.com>
>     * Ivan Meredith <ivan ivan.net.nz>
>     * Jed Smith <jsmith linode.com>
>     * Jeremy Orem <jeremy.orem gmail.com>
>     * Jerry Chen <github jcsalterego.otherinbox.com>
>     * Paul Querna <pquerna apache.org>
>     * Tom Davis <tom dislocatedday.com>
>
> Sponsors
>
> Champion
>
>     * Paul Querna
>
> Nominated Mentors
>
>     * Paul Querna
>
> Sponsoring Entity
>
>     * Incubator PMC
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.423 / Virus Database: 270.14.32/2460 - Release Date: 10/26/09
> 20:22:00

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[antelder]

+1, sounds really interesting, I'd be happy to be a mentor too if you
need another.

   ...ant

On Tue, Oct 27, 2009 at 8:15 AM, Gavin <gavin@...> wrote:

> This looks interesting, I'd be happy to help Mentor and have already put my
> name down.
>
> Gav...
>
>> -----Original Message-----
>> From: Paul Querna [mailto:paul@...]
>> Sent: Tuesday, 27 October 2009 5:00 PM
>> To: general@...
>> Subject: [PROPOSAL] Libcloud Project
>>
>> Hi,
>>
>> I would like to propose incubating the existing Libcloud project to
>> join the ASF:
>>
>> Proposal  Wiki: <http://wiki.apache.org/incubator/LibcloudProposal>
>>
>> Libcloud is a unified Python API around many common cloud services
>> provider, and I believe it could benefit greatly by joining the Apache
>> Software Foundation.  I also believe the ASF needs more Python
>> projects, and more projects involved in the developing cloud
>> infrastructure.  We still need a few mentors, so feel free to signup
>> :-)
>>
>> We would appreciate feedback and comments on the proposal.
>>
>> Full proposal is bellow.
>>
>> Thanks,
>>
>> Paul
>>
>> ------------------------
>> Libcloud, a unified interface to the cloud
>>
>> Abstract
>>
>> libcloud (<http://www.libcloud.org>) is a pure python client library
>> for interacting with many of the popular cloud server providers. It
>> was created to make it easy for developers to build products that work
>> between any of the services that it supports.
>>
>> Proposal
>>
>>     * Provide unified API for manipulating servers instances across
>> many hosting providers who provide an API to manipulate instances.
>> Current API includes: list, reboot, create, destroy, list images, list
>> sizes.
>>
>>     * (future) Provide utilities for manipulating and creating server
>> images in many formats. (See the independent Stacklet project for
>> ideas)
>>
>>     * (future) Provide unified API for storing large objects on
>> popular hosting provider storage APIs.
>>
>> Background
>>
>> While there are some projects to create open standards for
>> interoperability within the cloud, most have failed to gain widespread
>> adoption. Libcloud takes the approach of exposing a unified API to
>> cover multiple vendor's APIs, and in the future to support standard
>> APIs, assuming they become prevalent.
>>
>> Rationale
>>
>> There is a strong need in the developing cloud infrastructure for a
>> community supported, high quality, and vendor independent tool set for
>> managing servers and their resources. When new servers are just an API
>> call away, traditional infrastructure models are changing quickly.
>> Having a good library built around Apache's values and tradition will
>> enable new server infrastructure to evolve much more quickly.
>>
>> Initial Goals
>>
>> Libcloud is an existing open source project, with patches from many
>> different contributors. We view the moving to Apache as a way to
>> improve this community, and look into future APIs around creating
>> server images and large object storage.
>>
>> Current Status
>>
>> Libcloud is already open source under the ASL 2.0:
>>
>>     * Libcloud Website <http://www.libcloud.org>
>>     * Libcloud Mailing Lists <http://groups.google.com/group/libcloud>
>>     * Libcloud Source Control <http://github.com/cloudkick/libcloud>
>>
>> Meritocracy
>>
>> Libcloud has involvement from members of both the ASF and other open
>> source projects. Communication is driven by both IRC and E-Mail lists.
>>
>> Community
>>
>> Currently libcloud has several contributors, but not a large user
>> community other than a few companies. We would like to increase our
>> userbase as part of the incubator process.
>>
>> Core Developers
>>
>> Alex Polvi who wrote most of the original code is familiar with open
>> source from working at OSUOSL and at Mozilla. Tom Davis drove much of
>> the re factoring of the initial code base. Jed Smith, Ivan Meredith,
>> Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all
>> contributed mainly to developing provider specific drivers.
>>
>> Alignment
>>
>> Currently there are not many Apache communities involved with cloud
>> computing or python based infrastructure. We believe introducing such
>> a community is a good thing for the Apache Software Foundation.
>>
>> Known Risks
>>
>> Orphaned products
>>
>> libcloud is being used actively by Cloudkick to develop services. It
>> is a core part of our ongoing infrastructure improvements.
>>
>> Inexperience with Open Source
>>
>> libcloud was open sourced in July 2009, during OSCON. Core
>> contributors include former employees of Mozilla and an ASF member.
>>
>> Homogenous Developers
>>
>> Much of the initial development was done by Cloudkick, but much of the
>> core design was re-factored by the community, and many of the drivers
>> for each provider have been contributed by 3rd parties.
>>
>> Reliance on Salaried Developers
>>
>> The majority, but not all, of the developers are paid by their
>> employer to work on libcloud at this time.
>>
>> Relationships with Other Apache Products
>>
>> Libcloud doesn't share many attributes with existing Apache projects
>> due to it being in Python and addressing a new need.
>>
>> A Excessive Fascination with the Apache Brand
>>
>> Libcloud project seeks to build a last community around cloud API
>> interoperability, and is not fascinated with any short term gains of
>> being associated with the Apache Brand.
>>
>> Documentation
>>
>> TODO: links to related material on Cloud APIs/interop (?)
>>
>> Initial Source
>>
>> Initial source is contained completely inside the libcloud github
>> repository.
>>
>> External Dependencies
>>     * zope.interface
>>     * For Python =< 2.5, a JSON Parser such as SimpleJSON is required.
>>
>> Cryptography
>>
>> Uses standard Python APIs for SSL/HTTPS.
>>
>> Required Resources
>>
>> Mailing lists
>>
>>     * libcloud-dev
>>     * libcloud-commits
>>     * libcloud-private
>>
>> Subversion
>>
>>     * https://svn.apache.org/repos/asf/incubator/libcloud
>>
>> Issue Tracking
>>
>>     * JIRA (LCLD)
>>
>> Initial Committers
>>
>>     * Alex Polvi <alex polvi.net>
>>     * Dan Di Spaltro <dan.dispaltro gmail.com>
>>     * Ivan Meredith <ivan ivan.net.nz>
>>     * Jed Smith <jsmith linode.com>
>>     * Jeremy Orem <jeremy.orem gmail.com>
>>     * Jerry Chen <github jcsalterego.otherinbox.com>
>>     * Paul Querna <pquerna apache.org>
>>     * Tom Davis <tom dislocatedday.com>
>>
>> Sponsors
>>
>> Champion
>>
>>     * Paul Querna
>>
>> Nominated Mentors
>>
>>     * Paul Querna
>>
>> Sponsoring Entity
>>
>>     * Incubator PMC
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.5.423 / Virus Database: 270.14.32/2460 - Release Date: 10/26/09
>> 20:22:00
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Leo Simons]

On Tue, Oct 27, 2009 at 6:59 AM, Paul Querna <paul@...> wrote:
> I would like to propose incubating the existing Libcloud project to join the ASF

Cool! I will try to make the time to help out a little; I'm interested
in this space :)

cheers,

Leo

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Nick Kew]

On 27 Oct 2009, at 06:59, Paul Querna wrote:

> Hi,
>
> I would like to propose incubating the existing Libcloud project to
> join the ASF:

+1.  Looks interesting!

There seem to be more than enough volunteers to mentor already,
so I won't put myself forward for that.  But I'll certainly watch with
interest!

 From your POV as king of infra, what uses of this might you
envisage @apache.org?

--
Nick Kew

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Niclas Hedhman]

+1...

There has been few new, accepted proposals lately...

On Tue, Oct 27, 2009 at 2:59 PM, Paul Querna <paul@...> wrote:

> Hi,
>
> I would like to propose incubating the existing Libcloud project to
> join the ASF:
>
> Proposal  Wiki: <http://wiki.apache.org/incubator/LibcloudProposal>
>
> Libcloud is a unified Python API around many common cloud services
> provider, and I believe it could benefit greatly by joining the Apache
> Software Foundation.  I also believe the ASF needs more Python
> projects, and more projects involved in the developing cloud
> infrastructure.  We still need a few mentors, so feel free to signup
> :-)
>
> We would appreciate feedback and comments on the proposal.
>
> Full proposal is bellow.
>
> Thanks,
>
> Paul
>
> ------------------------
> Libcloud, a unified interface to the cloud
>
> Abstract
>
> libcloud (<http://www.libcloud.org>) is a pure python client library
> for interacting with many of the popular cloud server providers. It
> was created to make it easy for developers to build products that work
> between any of the services that it supports.
>
> Proposal
>
>    * Provide unified API for manipulating servers instances across
> many hosting providers who provide an API to manipulate instances.
> Current API includes: list, reboot, create, destroy, list images, list
> sizes.
>
>    * (future) Provide utilities for manipulating and creating server
> images in many formats. (See the independent Stacklet project for
> ideas)
>
>    * (future) Provide unified API for storing large objects on
> popular hosting provider storage APIs.
>
> Background
>
> While there are some projects to create open standards for
> interoperability within the cloud, most have failed to gain widespread
> adoption. Libcloud takes the approach of exposing a unified API to
> cover multiple vendor's APIs, and in the future to support standard
> APIs, assuming they become prevalent.
>
> Rationale
>
> There is a strong need in the developing cloud infrastructure for a
> community supported, high quality, and vendor independent tool set for
> managing servers and their resources. When new servers are just an API
> call away, traditional infrastructure models are changing quickly.
> Having a good library built around Apache's values and tradition will
> enable new server infrastructure to evolve much more quickly.
>
> Initial Goals
>
> Libcloud is an existing open source project, with patches from many
> different contributors. We view the moving to Apache as a way to
> improve this community, and look into future APIs around creating
> server images and large object storage.
>
> Current Status
>
> Libcloud is already open source under the ASL 2.0:
>
>    * Libcloud Website <http://www.libcloud.org>
>    * Libcloud Mailing Lists <http://groups.google.com/group/libcloud>
>    * Libcloud Source Control <http://github.com/cloudkick/libcloud>
>
> Meritocracy
>
> Libcloud has involvement from members of both the ASF and other open
> source projects. Communication is driven by both IRC and E-Mail lists.
>
> Community
>
> Currently libcloud has several contributors, but not a large user
> community other than a few companies. We would like to increase our
> userbase as part of the incubator process.
>
> Core Developers
>
> Alex Polvi who wrote most of the original code is familiar with open
> source from working at OSUOSL and at Mozilla. Tom Davis drove much of
> the re factoring of the initial code base. Jed Smith, Ivan Meredith,
> Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all
> contributed mainly to developing provider specific drivers.
>
> Alignment
>
> Currently there are not many Apache communities involved with cloud
> computing or python based infrastructure. We believe introducing such
> a community is a good thing for the Apache Software Foundation.
>
> Known Risks
>
> Orphaned products
>
> libcloud is being used actively by Cloudkick to develop services. It
> is a core part of our ongoing infrastructure improvements.
>
> Inexperience with Open Source
>
> libcloud was open sourced in July 2009, during OSCON. Core
> contributors include former employees of Mozilla and an ASF member.
>
> Homogenous Developers
>
> Much of the initial development was done by Cloudkick, but much of the
> core design was re-factored by the community, and many of the drivers
> for each provider have been contributed by 3rd parties.
>
> Reliance on Salaried Developers
>
> The majority, but not all, of the developers are paid by their
> employer to work on libcloud at this time.
>
> Relationships with Other Apache Products
>
> Libcloud doesn't share many attributes with existing Apache projects
> due to it being in Python and addressing a new need.
>
> A Excessive Fascination with the Apache Brand
>
> Libcloud project seeks to build a last community around cloud API
> interoperability, and is not fascinated with any short term gains of
> being associated with the Apache Brand.
>
> Documentation
>
> TODO: links to related material on Cloud APIs/interop (?)
>
> Initial Source
>
> Initial source is contained completely inside the libcloud github repository.
>
> External Dependencies
>    * zope.interface
>    * For Python =< 2.5, a JSON Parser such as SimpleJSON is required.
>
> Cryptography
>
> Uses standard Python APIs for SSL/HTTPS.
>
> Required Resources
>
> Mailing lists
>
>    * libcloud-dev
>    * libcloud-commits
>    * libcloud-private
>
> Subversion
>
>    * https://svn.apache.org/repos/asf/incubator/libcloud
>
> Issue Tracking
>
>    * JIRA (LCLD)
>
> Initial Committers
>
>    * Alex Polvi <alex polvi.net>
>    * Dan Di Spaltro <dan.dispaltro gmail.com>
>    * Ivan Meredith <ivan ivan.net.nz>
>    * Jed Smith <jsmith linode.com>
>    * Jeremy Orem <jeremy.orem gmail.com>
>    * Jerry Chen <github jcsalterego.otherinbox.com>
>    * Paul Querna <pquerna apache.org>
>    * Tom Davis <tom dislocatedday.com>
>
> Sponsors
>
> Champion
>
>    * Paul Querna
>
> Nominated Mentors
>
>    * Paul Querna
>
> Sponsoring Entity
>
>    * Incubator PMC
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Carlos Sanchez-4]

+1 and I'm interested, in case you need a mentor

On Tue, Oct 27, 2009 at 9:56 PM, Niclas Hedhman <niclas@...> wrote:

> +1...
>
> There has been few new, accepted proposals lately...
>
> On Tue, Oct 27, 2009 at 2:59 PM, Paul Querna <paul@...> wrote:
>> Hi,
>>
>> I would like to propose incubating the existing Libcloud project to
>> join the ASF:
>>
>> Proposal  Wiki: <http://wiki.apache.org/incubator/LibcloudProposal>
>>
>> Libcloud is a unified Python API around many common cloud services
>> provider, and I believe it could benefit greatly by joining the Apache
>> Software Foundation.  I also believe the ASF needs more Python
>> projects, and more projects involved in the developing cloud
>> infrastructure.  We still need a few mentors, so feel free to signup
>> :-)
>>
>> We would appreciate feedback and comments on the proposal.
>>
>> Full proposal is bellow.
>>
>> Thanks,
>>
>> Paul
>>
>> ------------------------
>> Libcloud, a unified interface to the cloud
>>
>> Abstract
>>
>> libcloud (<http://www.libcloud.org>) is a pure python client library
>> for interacting with many of the popular cloud server providers. It
>> was created to make it easy for developers to build products that work
>> between any of the services that it supports.
>>
>> Proposal
>>
>>    * Provide unified API for manipulating servers instances across
>> many hosting providers who provide an API to manipulate instances.
>> Current API includes: list, reboot, create, destroy, list images, list
>> sizes.
>>
>>    * (future) Provide utilities for manipulating and creating server
>> images in many formats. (See the independent Stacklet project for
>> ideas)
>>
>>    * (future) Provide unified API for storing large objects on
>> popular hosting provider storage APIs.
>>
>> Background
>>
>> While there are some projects to create open standards for
>> interoperability within the cloud, most have failed to gain widespread
>> adoption. Libcloud takes the approach of exposing a unified API to
>> cover multiple vendor's APIs, and in the future to support standard
>> APIs, assuming they become prevalent.
>>
>> Rationale
>>
>> There is a strong need in the developing cloud infrastructure for a
>> community supported, high quality, and vendor independent tool set for
>> managing servers and their resources. When new servers are just an API
>> call away, traditional infrastructure models are changing quickly.
>> Having a good library built around Apache's values and tradition will
>> enable new server infrastructure to evolve much more quickly.
>>
>> Initial Goals
>>
>> Libcloud is an existing open source project, with patches from many
>> different contributors. We view the moving to Apache as a way to
>> improve this community, and look into future APIs around creating
>> server images and large object storage.
>>
>> Current Status
>>
>> Libcloud is already open source under the ASL 2.0:
>>
>>    * Libcloud Website <http://www.libcloud.org>
>>    * Libcloud Mailing Lists <http://groups.google.com/group/libcloud>
>>    * Libcloud Source Control <http://github.com/cloudkick/libcloud>
>>
>> Meritocracy
>>
>> Libcloud has involvement from members of both the ASF and other open
>> source projects. Communication is driven by both IRC and E-Mail lists.
>>
>> Community
>>
>> Currently libcloud has several contributors, but not a large user
>> community other than a few companies. We would like to increase our
>> userbase as part of the incubator process.
>>
>> Core Developers
>>
>> Alex Polvi who wrote most of the original code is familiar with open
>> source from working at OSUOSL and at Mozilla. Tom Davis drove much of
>> the re factoring of the initial code base. Jed Smith, Ivan Meredith,
>> Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all
>> contributed mainly to developing provider specific drivers.
>>
>> Alignment
>>
>> Currently there are not many Apache communities involved with cloud
>> computing or python based infrastructure. We believe introducing such
>> a community is a good thing for the Apache Software Foundation.
>>
>> Known Risks
>>
>> Orphaned products
>>
>> libcloud is being used actively by Cloudkick to develop services. It
>> is a core part of our ongoing infrastructure improvements.
>>
>> Inexperience with Open Source
>>
>> libcloud was open sourced in July 2009, during OSCON. Core
>> contributors include former employees of Mozilla and an ASF member.
>>
>> Homogenous Developers
>>
>> Much of the initial development was done by Cloudkick, but much of the
>> core design was re-factored by the community, and many of the drivers
>> for each provider have been contributed by 3rd parties.
>>
>> Reliance on Salaried Developers
>>
>> The majority, but not all, of the developers are paid by their
>> employer to work on libcloud at this time.
>>
>> Relationships with Other Apache Products
>>
>> Libcloud doesn't share many attributes with existing Apache projects
>> due to it being in Python and addressing a new need.
>>
>> A Excessive Fascination with the Apache Brand
>>
>> Libcloud project seeks to build a last community around cloud API
>> interoperability, and is not fascinated with any short term gains of
>> being associated with the Apache Brand.
>>
>> Documentation
>>
>> TODO: links to related material on Cloud APIs/interop (?)
>>
>> Initial Source
>>
>> Initial source is contained completely inside the libcloud github repository.
>>
>> External Dependencies
>>    * zope.interface
>>    * For Python =< 2.5, a JSON Parser such as SimpleJSON is required.
>>
>> Cryptography
>>
>> Uses standard Python APIs for SSL/HTTPS.
>>
>> Required Resources
>>
>> Mailing lists
>>
>>    * libcloud-dev
>>    * libcloud-commits
>>    * libcloud-private
>>
>> Subversion
>>
>>    * https://svn.apache.org/repos/asf/incubator/libcloud
>>
>> Issue Tracking
>>
>>    * JIRA (LCLD)
>>
>> Initial Committers
>>
>>    * Alex Polvi <alex polvi.net>
>>    * Dan Di Spaltro <dan.dispaltro gmail.com>
>>    * Ivan Meredith <ivan ivan.net.nz>
>>    * Jed Smith <jsmith linode.com>
>>    * Jeremy Orem <jeremy.orem gmail.com>
>>    * Jerry Chen <github jcsalterego.otherinbox.com>
>>    * Paul Querna <pquerna apache.org>
>>    * Tom Davis <tom dislocatedday.com>
>>
>> Sponsors
>>
>> Champion
>>
>>    * Paul Querna
>>
>> Nominated Mentors
>>
>>    * Paul Querna
>>
>> Sponsoring Entity
>>
>>    * Incubator PMC
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>>
>>
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I  live here; http://tinyurl.com/2qq9er
> I  work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Carlos Sanchez-4]

+1  the idea is very interesting


On Tue, Oct 27, 2009 at 9:56 PM, Niclas Hedhman <niclas@...> wrote:

> +1...
>
> There has been few new, accepted proposals lately...
>
> On Tue, Oct 27, 2009 at 2:59 PM, Paul Querna <paul@...> wrote:
>> Hi,
>>
>> I would like to propose incubating the existing Libcloud project to
>> join the ASF:
>>
>> Proposal  Wiki: <http://wiki.apache.org/incubator/LibcloudProposal>
>>
>> Libcloud is a unified Python API around many common cloud services
>> provider, and I believe it could benefit greatly by joining the Apache
>> Software Foundation.  I also believe the ASF needs more Python
>> projects, and more projects involved in the developing cloud
>> infrastructure.  We still need a few mentors, so feel free to signup
>> :-)
>>
>> We would appreciate feedback and comments on the proposal.
>>
>> Full proposal is bellow.
>>
>> Thanks,
>>
>> Paul
>>
>> ------------------------
>> Libcloud, a unified interface to the cloud
>>
>> Abstract
>>
>> libcloud (<http://www.libcloud.org>) is a pure python client library
>> for interacting with many of the popular cloud server providers. It
>> was created to make it easy for developers to build products that work
>> between any of the services that it supports.
>>
>> Proposal
>>
>>    * Provide unified API for manipulating servers instances across
>> many hosting providers who provide an API to manipulate instances.
>> Current API includes: list, reboot, create, destroy, list images, list
>> sizes.
>>
>>    * (future) Provide utilities for manipulating and creating server
>> images in many formats. (See the independent Stacklet project for
>> ideas)
>>
>>    * (future) Provide unified API for storing large objects on
>> popular hosting provider storage APIs.
>>
>> Background
>>
>> While there are some projects to create open standards for
>> interoperability within the cloud, most have failed to gain widespread
>> adoption. Libcloud takes the approach of exposing a unified API to
>> cover multiple vendor's APIs, and in the future to support standard
>> APIs, assuming they become prevalent.
>>
>> Rationale
>>
>> There is a strong need in the developing cloud infrastructure for a
>> community supported, high quality, and vendor independent tool set for
>> managing servers and their resources. When new servers are just an API
>> call away, traditional infrastructure models are changing quickly.
>> Having a good library built around Apache's values and tradition will
>> enable new server infrastructure to evolve much more quickly.
>>
>> Initial Goals
>>
>> Libcloud is an existing open source project, with patches from many
>> different contributors. We view the moving to Apache as a way to
>> improve this community, and look into future APIs around creating
>> server images and large object storage.
>>
>> Current Status
>>
>> Libcloud is already open source under the ASL 2.0:
>>
>>    * Libcloud Website <http://www.libcloud.org>
>>    * Libcloud Mailing Lists <http://groups.google.com/group/libcloud>
>>    * Libcloud Source Control <http://github.com/cloudkick/libcloud>
>>
>> Meritocracy
>>
>> Libcloud has involvement from members of both the ASF and other open
>> source projects. Communication is driven by both IRC and E-Mail lists.
>>
>> Community
>>
>> Currently libcloud has several contributors, but not a large user
>> community other than a few companies. We would like to increase our
>> userbase as part of the incubator process.
>>
>> Core Developers
>>
>> Alex Polvi who wrote most of the original code is familiar with open
>> source from working at OSUOSL and at Mozilla. Tom Davis drove much of
>> the re factoring of the initial code base. Jed Smith, Ivan Meredith,
>> Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all
>> contributed mainly to developing provider specific drivers.
>>
>> Alignment
>>
>> Currently there are not many Apache communities involved with cloud
>> computing or python based infrastructure. We believe introducing such
>> a community is a good thing for the Apache Software Foundation.
>>
>> Known Risks
>>
>> Orphaned products
>>
>> libcloud is being used actively by Cloudkick to develop services. It
>> is a core part of our ongoing infrastructure improvements.
>>
>> Inexperience with Open Source
>>
>> libcloud was open sourced in July 2009, during OSCON. Core
>> contributors include former employees of Mozilla and an ASF member.
>>
>> Homogenous Developers
>>
>> Much of the initial development was done by Cloudkick, but much of the
>> core design was re-factored by the community, and many of the drivers
>> for each provider have been contributed by 3rd parties.
>>
>> Reliance on Salaried Developers
>>
>> The majority, but not all, of the developers are paid by their
>> employer to work on libcloud at this time.
>>
>> Relationships with Other Apache Products
>>
>> Libcloud doesn't share many attributes with existing Apache projects
>> due to it being in Python and addressing a new need.
>>
>> A Excessive Fascination with the Apache Brand
>>
>> Libcloud project seeks to build a last community around cloud API
>> interoperability, and is not fascinated with any short term gains of
>> being associated with the Apache Brand.
>>
>> Documentation
>>
>> TODO: links to related material on Cloud APIs/interop (?)
>>
>> Initial Source
>>
>> Initial source is contained completely inside the libcloud github repository.
>>
>> External Dependencies
>>    * zope.interface
>>    * For Python =< 2.5, a JSON Parser such as SimpleJSON is required.
>>
>> Cryptography
>>
>> Uses standard Python APIs for SSL/HTTPS.
>>
>> Required Resources
>>
>> Mailing lists
>>
>>    * libcloud-dev
>>    * libcloud-commits
>>    * libcloud-private
>>
>> Subversion
>>
>>    * https://svn.apache.org/repos/asf/incubator/libcloud
>>
>> Issue Tracking
>>
>>    * JIRA (LCLD)
>>
>> Initial Committers
>>
>>    * Alex Polvi <alex polvi.net>
>>    * Dan Di Spaltro <dan.dispaltro gmail.com>
>>    * Ivan Meredith <ivan ivan.net.nz>
>>    * Jed Smith <jsmith linode.com>
>>    * Jeremy Orem <jeremy.orem gmail.com>
>>    * Jerry Chen <github jcsalterego.otherinbox.com>
>>    * Paul Querna <pquerna apache.org>
>>    * Tom Davis <tom dislocatedday.com>
>>
>> Sponsors
>>
>> Champion
>>
>>    * Paul Querna
>>
>> Nominated Mentors
>>
>>    * Paul Querna
>>
>> Sponsoring Entity
>>
>>    * Incubator PMC
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>>
>>
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I  live here; http://tinyurl.com/2qq9er
> I  work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Paul Querna-6]

On Tue, Oct 27, 2009 at 3:29 PM, Nick Kew <nick@...> wrote:

>
> On 27 Oct 2009, at 06:59, Paul Querna wrote:
>
>> Hi,
>>
>> I would like to propose incubating the existing Libcloud project to
>> join the ASF:
>
> +1.  Looks interesting!
>
> There seem to be more than enough volunteers to mentor already,
> so I won't put myself forward for that.  But I'll certainly watch with
> interest!
>
> From your POV as king of infra, what uses of this might you
> envisage @apache.org?

From an ASF Infra POV, cloud computing in the public hosting providers
sense, doesn't make sense for us.  Since we generally only pay for
Hardware, and our BW/Power/Rackspace are all 'free' at most of our
hosting locations, and even amazon's cheapest machines cannot compare
to this.

I do believe there is oppurtunity within our own machines to better
utlitilize resources on many machines, and in the long run it will
make sense to run certain ASF services 'on the cloud', but I don't see
it changing super quickly for the ASF Infrastructure itself.

Thanks,

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[mnour]

Hi Paul...

   Allow me to dis-agree with ya :), cause this could be very
beneficial to any IT Operations Admins. I used to work in IBM Egypt
and you take a suitable time to make up an environment and make it
operations or when you add new hardware and want it to be operational
with other machines. CloudComputing is also about automating the IT
Staff operations and this is what I am doing with my current job
working as out-sourced Software Engineer for Sun microsystems
developing in their cloud computing platform called QLayer. From
QLayer PoV you manage all your physical resources as one big machine
and then you create machine upon request that only consume the
required resources using a very simple User Interface even the user
can have no big idea about the details of the specific operations that
should be done to build up this environment. So IMHO I think something
like LibCloud can be a very good building block to build environments
creation automation that can help ASF Infra admins. And even if it is
possible, using LibCloud and what we can build upon, ASF can provide
IaaS (Infrastructure As A Service) so ASF can have like farms of
machines and we provide building virtual environments to customers
which can provide a source of money to help ASF provide and help more
open source projects.

On Wed, Oct 28, 2009 at 8:57 AM, Paul Querna <paul@...> wrote:

> On Tue, Oct 27, 2009 at 3:29 PM, Nick Kew <nick@...> wrote:
>>
>> On 27 Oct 2009, at 06:59, Paul Querna wrote:
>>
>>> Hi,
>>>
>>> I would like to propose incubating the existing Libcloud project to
>>> join the ASF:
>>
>> +1.  Looks interesting!
>>
>> There seem to be more than enough volunteers to mentor already,
>> so I won't put myself forward for that.  But I'll certainly watch with
>> interest!
>>
>> From your POV as king of infra, what uses of this might you
>> envisage @apache.org?
>
> From an ASF Infra POV, cloud computing in the public hosting providers
> sense, doesn't make sense for us.  Since we generally only pay for
> Hardware, and our BW/Power/Rackspace are all 'free' at most of our
> hosting locations, and even amazon's cheapest machines cannot compare
> to this.
>
> I do believe there is oppurtunity within our own machines to better
> utlitilize resources on many machines, and in the long run it will
> make sense to run certain ASF services 'on the cloud', but I don't see
> it changing super quickly for the ASF Infrastructure itself.
>
> Thanks,
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

--
Thanks
- Mohammad Nour
- LinkedIn: http://www.linkedin.com/in/mnour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Jim Jagielski]

+1.

Like to join as well.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[kevan]

On Oct 27, 2009, at 2:59 AM, Paul Querna wrote:

> Reliance on Salaried Developers
>
> The majority, but not all, of the developers are paid by their
> employer to work on libcloud at this time.

I assume these are cloudkick employees? Will diversity be an issue for  
graduation? Since no affiliations are given, can't tell...

--kevan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Paul Querna-6]

On Thu, Oct 29, 2009 at 1:20 PM, Kevan Miller <kevan.miller@...> wrote:

>
> On Oct 27, 2009, at 2:59 AM, Paul Querna wrote:
>
>> Reliance on Salaried Developers
>>
>> The majority, but not all, of the developers are paid by their
>> employer to work on libcloud at this time.
>
> I assume these are cloudkick employees? Will diversity be an issue for
> graduation? Since no affiliations are given, can't tell...

Sure, it might be a blocker for graduation, but shouldn't be for incubation.

Thanks,

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...