Re: [VOTE] Accept jclouds into the Apache Incubator
On 22 April 2013 15:39, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... +1, binding - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Accept jclouds into the Apache Incubator
Hello folks, This vote has PASSED with 15 binding +1s and 9 non-binding +1s. Binding +1 VOTES: === David Nally Henry Saputra Bertrand Delacretaz Davanum Srinivas Suresh Marru Nandana Mihindukulasooriya Tomaz Muraus Olivier Lamy Mark Struberg Mohammad Nour El-Din Roman Shaposhnik Brian McCallister Jean-Baptiste Onofré Tom White Alan Cabrera Non-binding +1 VOTES: === Edward J. Yoon Chip Childers John D. Ament Kevin Kludge Ashish Paliwala Andrea Turli Andrei Savu Jordan Zimmerman Carlos Sanchez Thanks to all who voted and participated in the discussions. I'll work with folks to get the podling started. Becca On Apr 23, 2013, at 9:02 PM, Alan Cabrera wrote: > > On Apr 22, 2013, at 3:39 PM, Rebecca Wood wrote: > >> Hello everyone, >> >> I am calling a VOTE for acceptance of jclouds into the Apache Incubator. >> >> The vote will close on Monday, April 29, 2013. >> >> [ ] +1 Accept jclouds into the Apache Incubator. >> [ ] +0 Don't care. >> [ ] -1 Don't accept jclouds into the Incubator because... >> >> The full proposal is pasted below, and the corresponding wiki is >> http://wiki.apache.org/incubator/jcloudsProposal. >> >> Only VOTEs from Incubator PMC members are binding, but all are welcome to >> express their thoughts. > > +1 binding > > Regards, > Alan > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
On Apr 22, 2013, at 3:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. +1 binding Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Tom On Mon, Apr 22, 2013 at 11:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a highly acti
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) Regards JB On 04/23/2013 10:40 AM, Andrei Savu wrote: +1 (non-binding) -- Andrei Savu On Tue, Apr 23, 2013 at 9:40 AM, Tomaz Muraus wrote: +1 (binding) On Apr 22, 2013 3:39 PM, "Rebecca Wood" wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing c
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 -Brian On Mon, Apr 22, 2013 at 4:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a highly ac
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Accept jclouds into the Apache Incubator. On Tue, Apr 23, 2013 at 11:40 AM, Roman Shaposhnik wrote: > On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood wrote: > > Hello everyone, > > > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > > > The vote will close on Monday, April 29, 2013. > > > > [ ] +1 Accept jclouds into the Apache Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't accept jclouds into the Incubator because... > > +1 (binding) > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Davanum Srinivas :: http://davanum.wordpress.com
Re: [VOTE] Accept jclouds into the Apache Incubator
On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) On Tue, Apr 23, 2013 at 1:03 AM, Carlos Sanchez wrote: > +1 > > > > On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood wrote: > > > Hello everyone, > > > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > > > The vote will close on Monday, April 29, 2013. > > > > [ ] +1 Accept jclouds into the Apache Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't accept jclouds into the Incubator because... > > > > The full proposal is pasted below, and the corresponding wiki is > > http://wiki.apache.org/incubator/jcloudsProposal. > > > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > > express their thoughts. > > > > Thanks, > > > > Becca Wood > > > > -- > > > > = jclouds Proposal for Apache Incubator = > > > > == Abstract == > > > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > > library that enables developers to access a variety of supported cloud > > providers using one API. > > > > == Proposal == > > > > [[http://www.jclouds.org/|jclouds]] provides two portable API > > abstractions for cloud computing and cloud storage in the form of Java or > > Clojure libraries. By abstracting away vendor-specific details, jclouds > > supplies a solution for users to avoid lock-in to a specific cloud > vendor. > > It also provisions hooks to make it easy to take advantage of specific > > features from those vendors. > > > > == Background == > > > > jclouds began in March of 2009 while Adrian Cole was working on the > Amazon > > S3 plugin for Infinispan. He discovered that existing S3 libraries would > > not pass the concurrent test suite needed for write behind persistence. > > When it became clear that a new library was needed, jclouds formed as an > > independent project founded by Cole under the mentorship of Manik > Surtani. > > > > The fledgling jclouds team soon encountered two portability issues: > > runtime portability with Google App Engine and compatibility with the > > similar cloud files service from Rackspace. > > > > The legacy of Google App Engine is still present within jclouds and is > > expressed by the 'driver' design which doesn't require threads. > Supporting > > Rackspace started a legacy of cloud portability which would soon extend > to > > provisioning. As jclouds supports newer and cutting edge cloud > > technologies, it is in a constant state of evolution. > > > > jclouds was founded in Shoreditch, London. The ensuing 4 months > > backpacking between European Java User Groups accounts for the initial > > population of European developers and users within the community. The > > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and > there > > were a number of other advisers as well. > > > > == Rationale == > > > > There are many providers that offer IaaS clouds, but few APIs that can > > bridge the gap between cloud providers. jclouds supplies an abstraction > > layer for both compute and storage resources that makes it easy to work > > with many different cloud APIs using a simple and singular API. jclouds > > provides this abstraction layer for the Java and Clojure communities. It > is > > a unique niche within the cloud community. > > > > jclouds provides the write once, run anywhere concept when utilizing > > infrastructure cloud resources. > > > > == Initial Goals == > > > > * Build a more centralized community pulling together jclouds > developers, > > jclouds integrators, and service providers who use jclouds. > > * Although jclouds has a fairly collaborative community, the committers > > wish to further bridge the gap between developers and community by > > encouraging more community involvement in development processes. > > * Break down from a monolithic release process into one that is more > > decentrilized. > > * Bring the jclouds core code base consisting of ComputeService and > > Blobstore into Apache. > > * jclouds will not move all existing provider code into Apache. The goal > > is to move the provider code for those clouds that have complete > > portability and are tried, tested, and true. This includes code for > > OpenStack, Amazon EC2, and Google Cloud. > > > > == Current Status == > > > > === Meritocracy === > > > > jclouds has an active community of contributors who are encouraged to > > become full-fledged jclouds committers. A jclouds committer understands > the > > importance of seeking community feedback, actively listening to > > suggestions, and fostering relationships with community members who make > > contributions. The entirety of jclouds is built upon the relationships > that > > have been built with community members. This camaraderie will continue to > > be promoted as jclouds is introduced into the Incubator and beyond. > > > > jclouds encourages involvement from its community members, and the issues > > are open and available to any developers who wish to contribut
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a highly active a
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non binding) On Apr 22, 2013, at 3:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library > that enables developers to access a variety of supported cloud providers > using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions > for cloud computing and cloud storage in the form of Java or Clojure > libraries. By abstracting away vendor-specific details, jclouds supplies a > solution for users to avoid lock-in to a specific cloud vendor. It also > provisions hooks to make it easy to take advantage of specific features from > those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 > plugin for Infinispan. He discovered that existing S3 libraries would not > pass the concurrent test suite needed for write behind persistence. When it > became clear that a new library was needed, jclouds formed as an independent > project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: runtime > portability with Google App Engine and compatibility with the similar cloud > files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud technologies, > it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking > between European Java User Groups accounts for the initial population of > European developers and users within the community. The initial contributors > to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew > Phillips. Manik Surtani served as a mentor, and there were a number of other > advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can bridge > the gap between cloud providers. jclouds supplies an abstraction layer for > both compute and storage resources that makes it easy to work with many > different cloud APIs using a simple and singular API. jclouds provides this > abstraction layer for the Java and Clojure communities. It is a unique niche > within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers wish > to further bridge the gap between developers and community by encouraging > more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and Blobstore > into Apache. > * jclouds will not move all existing provider code into Apache. The goal is > to move the provider code for those clouds that have complete portability and > are tried, tested, and true. This includes code for OpenStack, Amazon EC2, > and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to become > full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to suggestions, > and fostering relationships with community members who make contributions. > The entirety of jclouds is built upon the relationships that have been built > with community members. This camaraderie will continue to be promoted as > jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues are > open and available to any developers who wish to contribute to the project. > The jclouds team currently seeks help and asks for suggestions utilizing the > jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. > Any and all submissions for changes are reviewed and
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) LieGrue, strub - Original Message - > From: Rebecca Wood > To: general@incubator.apache.org > Cc: > Sent: Tuesday, 23 April 2013, 0:39 > Subject: [VOTE] Accept jclouds into the Apache Incubator > > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library > that enables developers to access a variety of supported cloud providers > using > one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions > for > cloud computing and cloud storage in the form of Java or Clojure libraries. > By > abstracting away vendor-specific details, jclouds supplies a solution for > users > to avoid lock-in to a specific cloud vendor. It also provisions hooks to make > it > easy to take advantage of specific features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 > plugin for Infinispan. He discovered that existing S3 libraries would not > pass > the concurrent test suite needed for write behind persistence. When it became > clear that a new library was needed, jclouds formed as an independent project > founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: runtime > portability with Google App Engine and compatibility with the similar cloud > files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed > by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud technologies, > it > is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking > between European Java User Groups accounts for the initial population of > European developers and users within the community. The initial contributors > to > jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew > Phillips. Manik Surtani served as a mentor, and there were a number of other > advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can bridge > the gap between cloud providers. jclouds supplies an abstraction layer for > both > compute and storage resources that makes it easy to work with many different > cloud APIs using a simple and singular API. jclouds provides this abstraction > layer for the Java and Clojure communities. It is a unique niche within the > cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers wish > to > further bridge the gap between developers and community by encouraging more > community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and Blobstore > into Apache. > * jclouds will not move all existing provider code into Apache. The goal is > to > move the provider code for those clouds that have complete portability and > are > tried, tested, and true. This includes code for OpenStack, Amazon EC2, and > Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to become > full-fledged jclouds committers. A jclouds committer understands the > importance > of seeking community feedback, actively listening to suggestions, and > fostering > relationships with community members who make contributions
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) Olivier On Apr 23, 2013 8:39 AM, "Rebecca Wood" wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a highly
Re: [VOTE] Accept jclouds into the Apache Incubator
On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood wrote: > ...I am calling a VOTE for acceptance of jclouds into the Apache Incubator +1 -Bertrand P.S. 10 mentors...I'll know where to look when other podlings need help ;-) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non-binding) -- Andrei Savu On Tue, Apr 23, 2013 at 9:40 AM, Tomaz Muraus wrote: > +1 (binding) > On Apr 22, 2013 3:39 PM, "Rebecca Wood" wrote: > > > Hello everyone, > > > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > > > The vote will close on Monday, April 29, 2013. > > > > [ ] +1 Accept jclouds into the Apache Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't accept jclouds into the Incubator because... > > > > The full proposal is pasted below, and the corresponding wiki is > > http://wiki.apache.org/incubator/jcloudsProposal. > > > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > > express their thoughts. > > > > Thanks, > > > > Becca Wood > > > > -- > > > > = jclouds Proposal for Apache Incubator = > > > > == Abstract == > > > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > > library that enables developers to access a variety of supported cloud > > providers using one API. > > > > == Proposal == > > > > [[http://www.jclouds.org/|jclouds]] provides two portable API > > abstractions for cloud computing and cloud storage in the form of Java or > > Clojure libraries. By abstracting away vendor-specific details, jclouds > > supplies a solution for users to avoid lock-in to a specific cloud > vendor. > > It also provisions hooks to make it easy to take advantage of specific > > features from those vendors. > > > > == Background == > > > > jclouds began in March of 2009 while Adrian Cole was working on the > Amazon > > S3 plugin for Infinispan. He discovered that existing S3 libraries would > > not pass the concurrent test suite needed for write behind persistence. > > When it became clear that a new library was needed, jclouds formed as an > > independent project founded by Cole under the mentorship of Manik > Surtani. > > > > The fledgling jclouds team soon encountered two portability issues: > > runtime portability with Google App Engine and compatibility with the > > similar cloud files service from Rackspace. > > > > The legacy of Google App Engine is still present within jclouds and is > > expressed by the 'driver' design which doesn't require threads. > Supporting > > Rackspace started a legacy of cloud portability which would soon extend > to > > provisioning. As jclouds supports newer and cutting edge cloud > > technologies, it is in a constant state of evolution. > > > > jclouds was founded in Shoreditch, London. The ensuing 4 months > > backpacking between European Java User Groups accounts for the initial > > population of European developers and users within the community. The > > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and > there > > were a number of other advisers as well. > > > > == Rationale == > > > > There are many providers that offer IaaS clouds, but few APIs that can > > bridge the gap between cloud providers. jclouds supplies an abstraction > > layer for both compute and storage resources that makes it easy to work > > with many different cloud APIs using a simple and singular API. jclouds > > provides this abstraction layer for the Java and Clojure communities. It > is > > a unique niche within the cloud community. > > > > jclouds provides the write once, run anywhere concept when utilizing > > infrastructure cloud resources. > > > > == Initial Goals == > > > > * Build a more centralized community pulling together jclouds > developers, > > jclouds integrators, and service providers who use jclouds. > > * Although jclouds has a fairly collaborative community, the committers > > wish to further bridge the gap between developers and community by > > encouraging more community involvement in development processes. > > * Break down from a monolithic release process into one that is more > > decentrilized. > > * Bring the jclouds core code base consisting of ComputeService and > > Blobstore into Apache. > > * jclouds will not move all existing provider code into Apache. The goal > > is to move the provider code for those clouds that have complete > > portability and are tried, tested, and true. This includes code for > > OpenStack, Amazon EC2, and Google Cloud. > > > > == Current Status == > > > > === Meritocracy === > > > > jclouds has an active community of contributors who are encouraged to > > become full-fledged jclouds committers. A jclouds committer understands > the > > importance of seeking community feedback, actively listening to > > suggestions, and fostering relationships with community members who make > > contributions. The entirety of jclouds is built upon the relationships > that > > have been built with community members. This camaraderie will continue to > > be promoted as jclouds is introduced into the Incubator and beyond. > > > > jclouds encourages involvement from its community members, and the issues > > are open and available to any developers who wis
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) On Apr 22, 2013 3:39 PM, "Rebecca Wood" wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a highly active a
Re: [VOTE] Accept jclouds into the Apache Incubator
On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > +1 (binding) Best Regards, Nandana
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (not binding) Il giorno 23/apr/2013 07:41, "Ashish" ha scritto: > +1 (non-binding) > > > On Tue, Apr 23, 2013 at 4:09 AM, Rebecca Wood wrote: > > > Hello everyone, > > > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > > > The vote will close on Monday, April 29, 2013. > > > > [ ] +1 Accept jclouds into the Apache Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't accept jclouds into the Incubator because... > > > > The full proposal is pasted below, and the corresponding wiki is > > http://wiki.apache.org/incubator/jcloudsProposal. > > > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > > express their thoughts. > > > > Thanks, > > > > Becca Wood > > > > -- > > > > = jclouds Proposal for Apache Incubator = > > > > == Abstract == > > > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > > library that enables developers to access a variety of supported cloud > > providers using one API. > > > > == Proposal == > > > > [[http://www.jclouds.org/|jclouds]] provides two portable API > > abstractions for cloud computing and cloud storage in the form of Java or > > Clojure libraries. By abstracting away vendor-specific details, jclouds > > supplies a solution for users to avoid lock-in to a specific cloud > vendor. > > It also provisions hooks to make it easy to take advantage of specific > > features from those vendors. > > > > == Background == > > > > jclouds began in March of 2009 while Adrian Cole was working on the > Amazon > > S3 plugin for Infinispan. He discovered that existing S3 libraries would > > not pass the concurrent test suite needed for write behind persistence. > > When it became clear that a new library was needed, jclouds formed as an > > independent project founded by Cole under the mentorship of Manik > Surtani. > > > > The fledgling jclouds team soon encountered two portability issues: > > runtime portability with Google App Engine and compatibility with the > > similar cloud files service from Rackspace. > > > > The legacy of Google App Engine is still present within jclouds and is > > expressed by the 'driver' design which doesn't require threads. > Supporting > > Rackspace started a legacy of cloud portability which would soon extend > to > > provisioning. As jclouds supports newer and cutting edge cloud > > technologies, it is in a constant state of evolution. > > > > jclouds was founded in Shoreditch, London. The ensuing 4 months > > backpacking between European Java User Groups accounts for the initial > > population of European developers and users within the community. The > > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and > there > > were a number of other advisers as well. > > > > == Rationale == > > > > There are many providers that offer IaaS clouds, but few APIs that can > > bridge the gap between cloud providers. jclouds supplies an abstraction > > layer for both compute and storage resources that makes it easy to work > > with many different cloud APIs using a simple and singular API. jclouds > > provides this abstraction layer for the Java and Clojure communities. It > is > > a unique niche within the cloud community. > > > > jclouds provides the write once, run anywhere concept when utilizing > > infrastructure cloud resources. > > > > == Initial Goals == > > > > * Build a more centralized community pulling together jclouds > developers, > > jclouds integrators, and service providers who use jclouds. > > * Although jclouds has a fairly collaborative community, the committers > > wish to further bridge the gap between developers and community by > > encouraging more community involvement in development processes. > > * Break down from a monolithic release process into one that is more > > decentrilized. > > * Bring the jclouds core code base consisting of ComputeService and > > Blobstore into Apache. > > * jclouds will not move all existing provider code into Apache. The goal > > is to move the provider code for those clouds that have complete > > portability and are tried, tested, and true. This includes code for > > OpenStack, Amazon EC2, and Google Cloud. > > > > == Current Status == > > > > === Meritocracy === > > > > jclouds has an active community of contributors who are encouraged to > > become full-fledged jclouds committers. A jclouds committer understands > the > > importance of seeking community feedback, actively listening to > > suggestions, and fostering relationships with community members who make > > contributions. The entirety of jclouds is built upon the relationships > that > > have been built with community members. This camaraderie will continue to > > be promoted as jclouds is introduced into the Incubator and beyond. > > > > jclouds encourages involvement from its community members, and the issues > > are open and available to any developers who wish to c
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non-binding) On Tue, Apr 23, 2013 at 4:09 AM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a hig
Re: [VOTE] Accept jclouds into the Apache Incubator
+ 1 (binding) Suresh On Apr 22, 2013, at 6:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library > that enables developers to access a variety of supported cloud providers > using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions > for cloud computing and cloud storage in the form of Java or Clojure > libraries. By abstracting away vendor-specific details, jclouds supplies a > solution for users to avoid lock-in to a specific cloud vendor. It also > provisions hooks to make it easy to take advantage of specific features from > those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 > plugin for Infinispan. He discovered that existing S3 libraries would not > pass the concurrent test suite needed for write behind persistence. When it > became clear that a new library was needed, jclouds formed as an independent > project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: runtime > portability with Google App Engine and compatibility with the similar cloud > files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud technologies, > it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking > between European Java User Groups accounts for the initial population of > European developers and users within the community. The initial contributors > to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew > Phillips. Manik Surtani served as a mentor, and there were a number of other > advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can bridge > the gap between cloud providers. jclouds supplies an abstraction layer for > both compute and storage resources that makes it easy to work with many > different cloud APIs using a simple and singular API. jclouds provides this > abstraction layer for the Java and Clojure communities. It is a unique niche > within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers wish > to further bridge the gap between developers and community by encouraging > more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and Blobstore > into Apache. > * jclouds will not move all existing provider code into Apache. The goal is > to move the provider code for those clouds that have complete portability and > are tried, tested, and true. This includes code for OpenStack, Amazon EC2, > and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to become > full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to suggestions, > and fostering relationships with community members who make contributions. > The entirety of jclouds is built upon the relationships that have been built > with community members. This camaraderie will continue to be promoted as > jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues are > open and available to any developers who wish to contribute to the project. > The jclouds team currently seeks help and asks for suggestions utilizing the > jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. > Any and all submissions for changes are reviewe
RE: [VOTE] Accept jclouds into the Apache Incubator
+1 (non-binding) Very happy to see this. -kevin > -Original Message- > From: Rebecca Wood [mailto:silky...@gmail.com] > Sent: Monday, April 22, 2013 3:39 PM > To: general@incubator.apache.org > Subject: [VOTE] Accept jclouds into the Apache Incubator > > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library > that enables developers to access a variety of supported cloud providers using > one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for > cloud computing and cloud storage in the form of Java or Clojure libraries. By > abstracting away vendor-specific details, jclouds supplies a solution for > users to > avoid lock-in to a specific cloud vendor. It also provisions hooks to make it > easy > to take advantage of specific features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would not > pass > the concurrent test suite needed for write behind persistence. When it became > clear that a new library was needed, jclouds formed as an independent project > founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: runtime > portability with Google App Engine and compatibility with the similar cloud > files > service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed > by the 'driver' design which doesn't require threads. Supporting Rackspace > started a legacy of cloud portability which would soon extend to > provisioning. As > jclouds supports newer and cutting edge cloud technologies, it is in a > constant > state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking > between European Java User Groups accounts for the initial population of > European developers and users within the community. The initial contributors > to > jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew > Phillips. Manik Surtani served as a mentor, and there were a number of other > advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can bridge > the gap between cloud providers. jclouds supplies an abstraction layer for > both > compute and storage resources that makes it easy to work with many different > cloud APIs using a simple and singular API. jclouds provides this abstraction > layer > for the Java and Clojure communities. It is a unique niche within the cloud > community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers wish > to > further bridge the gap between developers and community by encouraging more > community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and Blobstore > into Apache. > * jclouds will not move all existing provider code into Apache. The goal is > to > move the provider code for those clouds that have complete portability and are > tried, tested, and true. This includes code for OpenStack, Amazon EC2, and > Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to become > full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to suggestions, > and fostering relationships with community members who make contributions. > The entirety of jclouds is built upon the
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non-binding) On Mon, Apr 22, 2013 at 6:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jclouds has a hig
Re: [VOTE] Accept jclouds into the Apache Incubator
On Mon, Apr 22, 2013 at 03:39:20PM -0700, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... +1 (non-binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Good luck guys - Henry On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic > library that enables developers to access a variety of supported cloud > providers using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API > abstractions for cloud computing and cloud storage in the form of Java or > Clojure libraries. By abstracting away vendor-specific details, jclouds > supplies a solution for users to avoid lock-in to a specific cloud vendor. > It also provisions hooks to make it easy to take advantage of specific > features from those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon > S3 plugin for Infinispan. He discovered that existing S3 libraries would > not pass the concurrent test suite needed for write behind persistence. > When it became clear that a new library was needed, jclouds formed as an > independent project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: > runtime portability with Google App Engine and compatibility with the > similar cloud files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud > technologies, it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months > backpacking between European Java User Groups accounts for the initial > population of European developers and users within the community. The > initial contributors to jclouds included Adrian Cole, James Murty, Andrew > Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there > were a number of other advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can > bridge the gap between cloud providers. jclouds supplies an abstraction > layer for both compute and storage resources that makes it easy to work > with many different cloud APIs using a simple and singular API. jclouds > provides this abstraction layer for the Java and Clojure communities. It is > a unique niche within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers > wish to further bridge the gap between developers and community by > encouraging more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal > is to move the provider code for those clouds that have complete > portability and are tried, tested, and true. This includes code for > OpenStack, Amazon EC2, and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to > become full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to > suggestions, and fostering relationships with community members who make > contributions. The entirety of jclouds is built upon the relationships that > have been built with community members. This camaraderie will continue to > be promoted as jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues > are open and available to any developers who wish to contribute to the > project. The jclouds team currently seeks help and asks for suggestions > utilizing the jclouds and jclouds-dev Google groups and IRC on > irc.freenode.net#jclouds. Any and all submissions for changes are > reviewed and taken into consideration. > > === Community === > > jcloud
Re: [VOTE] Accept jclouds into the Apache Incubator
On Mon, Apr 22, 2013 at 6:39 PM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > Looks good, happy to see this moving forward. +1 (binding) --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 On Tue, Apr 23, 2013 at 7:39 AM, Rebecca Wood wrote: > Hello everyone, > > I am calling a VOTE for acceptance of jclouds into the Apache Incubator. > > The vote will close on Monday, April 29, 2013. > > [ ] +1 Accept jclouds into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept jclouds into the Incubator because... > > The full proposal is pasted below, and the corresponding wiki is > http://wiki.apache.org/incubator/jcloudsProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Becca Wood > > -- > > = jclouds Proposal for Apache Incubator = > > == Abstract == > > [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library > that enables developers to access a variety of supported cloud providers > using one API. > > == Proposal == > > [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions > for cloud computing and cloud storage in the form of Java or Clojure > libraries. By abstracting away vendor-specific details, jclouds supplies a > solution for users to avoid lock-in to a specific cloud vendor. It also > provisions hooks to make it easy to take advantage of specific features from > those vendors. > > == Background == > > jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 > plugin for Infinispan. He discovered that existing S3 libraries would not > pass the concurrent test suite needed for write behind persistence. When it > became clear that a new library was needed, jclouds formed as an independent > project founded by Cole under the mentorship of Manik Surtani. > > The fledgling jclouds team soon encountered two portability issues: runtime > portability with Google App Engine and compatibility with the similar cloud > files service from Rackspace. > > The legacy of Google App Engine is still present within jclouds and is > expressed by the 'driver' design which doesn't require threads. Supporting > Rackspace started a legacy of cloud portability which would soon extend to > provisioning. As jclouds supports newer and cutting edge cloud technologies, > it is in a constant state of evolution. > > jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking > between European Java User Groups accounts for the initial population of > European developers and users within the community. The initial contributors > to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew > Phillips. Manik Surtani served as a mentor, and there were a number of other > advisers as well. > > == Rationale == > > There are many providers that offer IaaS clouds, but few APIs that can bridge > the gap between cloud providers. jclouds supplies an abstraction layer for > both compute and storage resources that makes it easy to work with many > different cloud APIs using a simple and singular API. jclouds provides this > abstraction layer for the Java and Clojure communities. It is a unique niche > within the cloud community. > > jclouds provides the write once, run anywhere concept when utilizing > infrastructure cloud resources. > > == Initial Goals == > > * Build a more centralized community pulling together jclouds developers, > jclouds integrators, and service providers who use jclouds. > * Although jclouds has a fairly collaborative community, the committers wish > to further bridge the gap between developers and community by encouraging > more community involvement in development processes. > * Break down from a monolithic release process into one that is more > decentrilized. > * Bring the jclouds core code base consisting of ComputeService and > Blobstore into Apache. > * jclouds will not move all existing provider code into Apache. The goal is > to move the provider code for those clouds that have complete portability and > are tried, tested, and true. This includes code for OpenStack, Amazon EC2, > and Google Cloud. > > == Current Status == > > === Meritocracy === > > jclouds has an active community of contributors who are encouraged to become > full-fledged jclouds committers. A jclouds committer understands the > importance of seeking community feedback, actively listening to suggestions, > and fostering relationships with community members who make contributions. > The entirety of jclouds is built upon the relationships that have been built > with community members. This camaraderie will continue to be promoted as > jclouds is introduced into the Incubator and beyond. > > jclouds encourages involvement from its community members, and the issues are > open and available to any developers who wish to contribute to the project. > The jclouds team currently seeks help and asks for suggestions utilizing the > jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. > Any and all submissions for changes are reviewed and taken into consideration. > > === Commu
[VOTE] Accept jclouds into the Apache Incubator
Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is currently fostered at https://groups.google.com/forum/#!forum/jclouds-dev and https://groups.google.com/forum/#!forum/jclouds. The jclouds te
