Re: [VOTE] CloudStack for Apache Incubator
+1 (binding) On Tue, Apr 10, 2012 at 8:55 AM, Emmanuel Lécharny wrote: > +1: accept CloudStack into Incubator > (binding) > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > > > > --**--**- > To unsubscribe, e-mail: > general-unsubscribe@incubator.**apache.org > For additional commands, e-mail: > general-help@incubator.apache.**org > > -- Thanks - Mohammad Nour "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein
Re: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project
+1 LieGrue, strub - Original Message - > From: Hadrian Zbarcea > To: general@incubator.apache.org > Cc: > Sent: Monday, April 9, 2012 6:11 PM > Subject: Re: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project > > +1 > Hadrian > > On 04/02/2012 05:10 AM, Andy Seaborne wrote: >> This is a call for vote to graduate the Apache Jena podling from Apache >> Incubator to be a top level project. >> >> Jena entered incubation in November 2010. The project has added two new >> committers and PPMC members, made several releases and has a diverse >> committer base. The user and development communities are active. The >> PPMC has indicated [1,2,3] that it believes the project is ready to >> graduate as a top-level project with the resolution draft below. >> >> We ask that the IPMC approve this graduation request though this VOTE. >> >> [1] Vote: http://s.apache.org/jena-graduation-vote >> [2] Result: http://s.apache.org/jena-graduation >> [3] Request for comments: >> > http://mail-archives.apache.org/mod_mbox/incubator-general/201203.mbox/%3C5C4A33CB-B122-43A8-B082-CBD63B526DE7%40cray.com%3E >> >> >> On behalf of the Apache Jena PPMC, >> >> Andy >> >> - >> >> [ ] +1 Recommend to the ASF Board that Apache Jena Proposal >> is ready to graduate to being a top level project. >> [ ] 0 >> [ ] -1 Do not graduate Apache Jena because ... >> >> The vote will be tallied no earlier than: >> >> Thursday April 5th, at 23:59 UTC. >> >> - >> >> X. Establish the Apache Jena Project >> >> WHEREAS, the Board of Directors deems it to be in the best >> interests of the Foundation and consistent with the >> Foundation's purpose to establish a Project Management >> Committee charged with the creation and maintenance of >> open-source software related to accessing, storing, querying, >> publishing and reasoning with semantic web data while >> adhering to relevant W3C and community standards. >> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >> Committee (PMC), to be known as the "Apache Jena Project", >> be and hereby is established pursuant to Bylaws of the >> Foundation; and be it further >> >> RESOLVED, that the Apache Jena Project be and hereby is >> responsible for the creation and maintenance of software >> related to accessing, storing, querying, >> publishing and reasoning with semantic web data while >> adhering to relevant W3C and community standards; >> and be it further >> >> RESOLVED, that the office of "Vice President, Apache Jena" be >> and hereby is created, the person holding such office to >> serve at the direction of the Board of Directors as the chair >> of the Apache Jena Project, and to have primary responsibility >> for management of the projects within the scope of >> responsibility of the Apache Jena Project; and be it further >> >> RESOLVED, that the persons listed immediately below be and >> hereby are appointed to serve as the initial members of the >> Apache Jena Project: >> >> * Andy Seaborne (andy) >> * Benson Marguilies (bimargulies) >> * Chris Dollin (chrisdollin) >> * Damian Steer (damian) >> * Dave Reynolds (der) >> * Ian Dickinson (ijd) >> * Paolo Castagna (castagna) >> * Rob Vesse (rvesse) >> * Stephen Allen (sallen) >> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andy Seaborne >> be appointed to the office of Vice President, Apache Jena, to >> serve in accordance with and subject to the direction of the >> Board of Directors and the Bylaws of the Foundation until >> death, resignation, retirement, removal or disqualification, >> or until a successor is appointed; and be it further >> >> RESOLVED, that the initial Apache Jena PMC be and hereby is >> tasked with the creation of a set of bylaws intended to >> encourage open development and increased participation in the >> Apache Jena Project; and be it further >> >> RESOLVED, that the Apache Jena Project be and hereby >> is tasked with the migration and rationalization of the Apache >> Incubator Jena podling; and be it further >> >> RESOLVED, that all responsibilities pertaining to the Apache >> Incubator Jena podling encumbered upon the Apache Incubator >> Project are hereafter discharged. >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > -- > Hadrian Zbarcea > Principal Software Architect > Talend, Inc > http://coders.talend.com/ > http://camelbot.blogspot.com/ > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding) -- Best Regards, -- Alex
Retiring Zeta Components
Hello all, just a short heads up: before a few days i have raised the question to retire Zeta Components because of lack of activity for quite a while. So far no committer has responded. I will follow up here again in a couple of days. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [all] Size of releases
On Mon, Apr 9, 2012 at 2:05 AM, Daniel Shahaf wrote:
> Christian Grobmeier wrote on Thu, Mar 29, 2012 at 00:22:19 +0200:
>> On Thu, Mar 29, 2012 at 12:06 AM, Daniel Shahaf
>> wrote:
>> > Jukka Zitting wrote on Wed, Mar 28, 2012 at 22:34:30 +0200:
>> >> Hi,
>> >>
>> >> On Wed, Mar 28, 2012 at 6:19 PM, Christian Grobmeier
>> >> wrote:
>> >> > I will try to update this document now with the recommendation from
>> >> > infra:
>> >> > http://incubator.apache.org/guides/releasemanagement.html#release-distribution
>> >>
>> >> While you're at it, can you please also (or rather instead) update the
>> >> ASF-wide documentation at http://www.apache.org/dev/#releases?
>> >>
>> >> This isn't particularly tied to the Incubator, so the primary place
>> >> for the relevant guidance shouldn't IMHO be incubator.apache.org. Most
>> >> notably the IPMC shouldn't be responsible for updating this
>> >> information in case the related infra policies change.
>> >>
>> >
>> > Yes it's on infra's radar to document the "some releases are large
>> > enough to need coordination with us" point. We've been busy so haven't
>> > got to it yet
>>
>> Please let us know if you have found some time, then we can point from
>> our release-docs to your document.
>
> http://www.apache.org/dev/release#heads-up
Thank you, I have linked this document in the "release management" guide.
Cheers
Christian
> % $svn di
> Index: release.mdtext
> ===
> --- release.mdtext (revision 1311120)
> +++ release.mdtext (revision 1311121)
> @@ -222,6 +222,18 @@
> their dist/ dir. To transition just open a Jira ticket and specify: (1) what
> mailing list commit mails should go to.
>
> +## Do I need to talk to Infrastructure before distributing a release?
> {#heads-up}
> +
> +Most projects can just distribute a release as described in the previous two
> +questions. However, releases that are likely to strain the mirroring and
> +download resources **must** be coordinated with infrastructure.
> +
> +Releases of more than 1GB of artifacts require a heads-up to Infrastructure
> in
> +advance.
> +
> +Specific exemptions from other dist policies (such as what may or must or
> must
> +not be distributed via the mirrors) also need to be coordinated with
> Infrastructure.
> +
> ## How Should Releases Be Announced? ## {#release-announcements}
>
> Please ensure that you wait at least 24 hours after uploading a new release
--
http://www.grobmeier.de
https://www.timeandbill.de
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding)
Ate
On 04/10/2012 03:32 AM, Kevin Kluge wrote:
Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
The proposal is available at [1] and I have also included it below. Please
vote with:
+1: accept CloudStack into Incubator
+0: don't care
-1: do not accept CloudStack into Incubator (please explain the objection)
The vote is open for at least 72 hours from now (until at least 19:00 US-PST on
April 12, 2012).
Thanks for the consideration.
-kevin
[1] http://wiki.apache.org/incubator/CloudStackProposal
Abstract
CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
platform.
Proposal
CloudStack provides control plane software that can be used to create an IaaS
cloud. It includes an HTTP-based API for user and administrator functions and a
web UI for user and administrator access. Administrators can provision physical
infrastructure (e.g., servers, network elements, storage) into an instance of
CloudStack, while end users can use the CloudStack self-service API and UI for
the provisioning and management of virtual machines, virtual disks, and virtual
networks.
Citrix Systems, Inc. submits this proposal to donate the CloudStack source code,
documentation, websites, and trademarks to the Apache Software Foundation
("ASF").
Background
Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual
machines to end users. CloudStack additionally provides baremetal OS installation to end users via
a self-service interface. The management of physical resources to provide the larger goal of cloud
service delivery is known as "orchestration". IaaS clouds are usually described as
"elastic" -- an elastic service is one that allows its user to rapidly scale up or down
their need for resources.
A number of open source projects and companies have been created to implement IaaS
clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General
Public License version 3 ("GPL v3") in 2010. Citrix acquired Cloud.com,
including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache
License v2 in April, 2012.
Rationale
IaaS clouds provide the ability to implement datacenter operations in a
programmable fashion. This functionality is tremendously powerful and benefits
the community by providing:
- More efficient use of datacenter personnel
- More efficient use of datacenter hardware
- Better responsiveness to user requests
- Better uptime/availability through automation
While there are several open source IaaS efforts today, none are governed by an
independent foundation such as ASF. Vendor influence and/or proprietary
implementations may limit the community's ability to choose the hardware and
software for use in the datacenter. The community at large will benefit from
the ability to enhance the orchestration layer as needed for particular
hardware or software support, and to implement algorithms and features that may
reduce cost or increase user satisfaction for specific use cases. In this
respect the independent nature of the ASF is key to the long term health and
success of the project.
Initial Goals
The CloudStack project has two initial goals after the proposal is accepted and
the incubation has begun.
The Cloudstack Project's first goal is to ensure that the CloudStack source
includes only third party code that is licensed under the Apache License or
open source licenses that are approved by the ASF for use in ASF projects. The
CloudStack Project has begun the process of removing third party code that is
not licensed under an ASF approved license. This is an ongoing process that
will continue into the incubation period. Third party code contributed to
CloudStack under the CloudStack contribution agreement was assigned to
Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack
project has begun the process of amending the previous CloudStack contribution
agreements to obtain consent from existing contributors to change the
CloudStack project's license. In the event that an existing contributor does
not consent to this change, the project is prepared to remove that
contributor's code. Additionally, there are binary dependencies on
redistributed libraries that
are not provided with an ASF-approved license. Finally, the CloudStack has source files incorporated from third parties that were not provided with an ASF-approved license. We have begun the process of re-writing this software. This is an ongoing process that will extend into the incubation period. These issues are discussed in more detail later in the proposal.
Although CloudStack is open source, many design documents and discussions that
should have been publicly available and accessible were not publicized. The
Project's second goal will be to fix this lack of transparency by encouraging
the initial committers to publicize technical documentation
RE: Spam on the Incubator wiki
> -Original Message- > From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] > Sent: Saturday, 7 April 2012 12:11 AM > To: general > Subject: Spam on the Incubator wiki > > Hi, > > Looks like the Incubator wiki is getting hit by spammers. A simple solution to > the problem is to require whitelisting of all wiki users [1], though it does add > a bit of an entry barrier. I'll request infra to make the required configuration > change unless anyone comes up with an alternative solution. > > [1] http://wiki.apache.org/general/OurWikiFarm#per_wiki_access_control_- > _tighten_your_wiki_just_a_little.2C_benefit_just_a_lot > > BR, I'm seeing more and more spam appear, just give me the nod and it'll be done. Gav... > > Jukka Zitting > > - > 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] CloudStack for Apache Incubator
[X] +1: accept CloudStack into Incubator (non-binding)
[] +0: don't care
[] -1: do not accept CloudStack into Incubator (please explain the objection)
Cheers
Daniel
On Tue, Apr 10, 2012 at 3:32 AM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed
Re: [VOTE] CloudStack for Apache Incubator
On Mon, Apr 9, 2012 at 9:32 PM, Kevin Kluge wrote: > Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. > The proposal is available at [1] and I have also included it below. Please > vote with: > +1: accept CloudStack into Incubator > +0: don't care > -1: do not accept CloudStack into Incubator (please explain the objection) > > The vote is open for at least 72 hours from now (until at least 19:00 US-PST > on April 12, 2012). +1 Thanks, --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] CloudStack for Apache Incubator
+1 (binding)
>-Original Message-
>From: Kevin Kluge [mailto:kevin.kl...@citrix.com]
>Sent: Monday, April 09, 2012 9:32 PM
>To: general@incubator.apache.org
>Subject: [VOTE] CloudStack for Apache Incubator
>
>Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
>The
>proposal is available at [1] and I have also included it below. Please vote
>with:
>+1: accept CloudStack into Incubator
>+0: don't care
>-1: do not accept CloudStack into Incubator (please explain the objection)
>
>The vote is open for at least 72 hours from now (until at least 19:00 US-PST on
>April 12, 2012).
>
>Thanks for the consideration.
>
>-kevin
>
>[1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
>Abstract
>
>CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
>platform.
>
>Proposal
>
>CloudStack provides control plane software that can be used to create an IaaS
>cloud. It includes an HTTP-based API for user and administrator functions and
>a web UI for user and administrator access. Administrators can provision
>physical infrastructure (e.g., servers, network elements, storage) into an
>instance of CloudStack, while end users can use the CloudStack self-service
>API and UI for the provisioning and management of virtual machines, virtual
>disks, and virtual networks.
>
>Citrix Systems, Inc. submits this proposal to donate the CloudStack source
>code, documentation, websites, and trademarks to the Apache Software
>Foundation ("ASF").
>
>Background
>
>Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
>provide virtual machines to end users. CloudStack additionally provides
>baremetal OS installation to end users via a self-service interface. The
>management of physical resources to provide the larger goal of cloud service
>delivery is known as "orchestration". IaaS clouds are usually described as
>"elastic" -- an elastic service is one that allows its user to rapidly scale
>up or
>down their need for resources.
>
>A number of open source projects and companies have been created to
>implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
>the source under GNU General Public License version 3 ("GPL v3") in 2010.
>Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed
>the
>CloudStack source under Apache License v2 in April, 2012.
>
>Rationale
>
>IaaS clouds provide the ability to implement datacenter operations in a
>programmable fashion. This functionality is tremendously powerful and
>benefits the community by providing:
>
>- More efficient use of datacenter personnel
>- More efficient use of datacenter hardware
>- Better responsiveness to user requests
>- Better uptime/availability through automation
>
>While there are several open source IaaS efforts today, none are governed by
>an independent foundation such as ASF. Vendor influence and/or proprietary
>implementations may limit the community's ability to choose the hardware
>and software for use in the datacenter. The community at large will benefit
>from the ability to enhance the orchestration layer as needed for particular
>hardware or software support, and to implement algorithms and features that
>may reduce cost or increase user satisfaction for specific use cases. In this
>respect the independent nature of the ASF is key to the long term health and
>success of the project.
>
>Initial Goals
>
>The CloudStack project has two initial goals after the proposal is accepted and
>the incubation has begun.
>
>The Cloudstack Project's first goal is to ensure that the CloudStack source
>includes only third party code that is licensed under the Apache License or
>open source licenses that are approved by the ASF for use in ASF projects.
>The CloudStack Project has begun the process of removing third party code
>that is not licensed under an ASF approved license. This is an ongoing process
>that will continue into the incubation period. Third party code contributed to
>CloudStack under the CloudStack contribution agreement was assigned to
>Cloud.com in exchange for distributing CloudStack under GPLv3. The
>CloudStack project has begun the process of amending the previous
>CloudStack contribution agreements to obtain consent from existing
>contributors to change the CloudStack project's license. In the event that an
>existing contributor does not consent to this change, the project is prepared
>to remove that contributor's code. Additionally, there are binary
>dependencies on redistributed libraries that are not provided with an ASF-
>approved license. Finally, the CloudStack has source files incorporated from
>third parties that were not provided with an ASF-approved license. We have
>begun the process of re-writing this software. This is an ongoing process that
>will extend into the incubation period. These issues are discussed in more
>detail later in the proposal.
>
>Although CloudStack is open source, many design documents and discussions
>that sho
Re: [VOTE] Release Apache Mesos 0.9.0-incubating (RC4)
On 8 April 2012 23:48, Benjamin Hindman wrote: > Hi Sebb, > > Thanks so much for taking a look! Responses inline. > > On Sun, Apr 8, 2012 at 2:22 PM, sebb wrote: > >> On 7 April 2012 02:59, Benjamin Hindman wrote: >> > Please vote on releasing the following candidate as Apache Mesos >> > (incubating) version 0.9.0. This will be the first incubator release for >> > Mesos in Apache, but the fifth release candidate. >> > >> > Vote thread on mesos-...@incubator.apache.org: >> > >> > >> http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201203.mbox/%3CCAFeOQnW7jk-VcTFpUP-_VonL99JCnggKeNPW%2BGx-Ozdy1U8sjg%40mail.gmail.com%3E >> > >> > The candidate for Mesos 0.9.0-incubating release is available at: >> > >> > >> http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz >> > >> > The tag to be voted on: >> > >> > >> https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4 >> >> The NOTICE file is incomplete; the product name and copyright year(s) >> are missing. >> > > Thanks, I'll add that. > > >> The LICENSE file includes references to several 3rd party items. >> It looks like glog and utilities.cc and others may require mention in >> NOTICE. >> > > Is there a document somewhere which describes when something needs to go > into NOTICE in addition to LICENSE? I had read previously read the section > titled "What Are Required Third-Party Notices?" from > http://apache.org/legal/resolved.html#required-third-party-notices but I > still was unclear whether or not anything needed to be done. AFAIK, it depends on what the license says. > >> There's no DISCLAIMER file in SVN root. >> > > Right, I'll add that. > > >> There are several 3rd party libraries in SVN under >> >> >> https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4/third_party/ > > > This was deliberate, so as to make it easier to use for both developers > (who check out the repository) and users (who download a distribution). Is > there a policy against this? I saw this as analogous to distributing JARs. > AIUI, there must be a source-only release. This should have N&L files that relate to the source only. A binary release may also be provided, in which case its N&L files need to correspond with what is in the binary release. For building from source, the dependencies need to be provided somehow. Various options are possible: - written instructions how to get the dependencies and where to put them - separate script to download the dependencies - build process automatically downloads the dependencies. Depending on the licenses of 3rd party jars you may need to provide a combination of methods. There are some types of dependencies that can only be included if the user makes a deliberate choice of downloading them, see the cited doc. If all the dependencies are binary-distributable, it's probably also OK to provide an archive containing just the dependencies. This must have the relevant N&L files. > > Is the correct next step to cancel this vote, IMO, yes. > create a RC5, and start a new vote thread for that? Once the issues have been resolved, yes. > Or modify RC4? No, RCs should be immutable. Otherwise how can one tell what one is voting on? > Thank you very much! > > Ben. > > > >> > The MD5 checksum of the tarball can be found at: >> > >> > >> http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.md5 >> > >> > The signature of the tarball can be found at: >> > >> > >> http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.asc >> > >> > Mesos' KEYS file, containing the PGP keys used to sign the release: >> > http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS >> > >> > Please vote on releasing this package as Apache Mesos 0.9.0-incubating! >> > >> > The vote is open until Tuesday, April 10th at 8 pm (a bit more than 72 >> > hours since it's over the weekend) and passes if a majority of at least 3 >> > +1 IPMC votes are cast. >> > >> > [ ] +1 Release this package as Apache Mesos 0.9.0-incubating >> > [ ] -1 Do not release this package because ... >> > >> > To learn more about Apache Mesos, please see >> > http://incubator.apache.org/mesos. >> >> - >> 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] CloudStack for Apache Incubator
+1
Doug
On Apr 9, 2012 6:32 PM, "Kevin Kluge" wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the
> Incubator. The proposal is available at [1] and I have also included it
> below. Please vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00
> US-PST on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an
> IaaS cloud. It includes an HTTP-based API for user and administrator
> functions and a web UI for user and administrator access. Administrators
> can provision physical infrastructure (e.g., servers, network elements,
> storage) into an instance of CloudStack, while end users can use the
> CloudStack self-service API and UI for the provisioning and management of
> virtual machines, virtual disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these
> clouds provide virtual machines to end users. CloudStack additionally
> provides baremetal OS installation to end users via a self-service
> interface. The management of physical resources to provide the larger goal
> of cloud service delivery is known as "orchestration". IaaS clouds are
> usually described as "elastic" -- an elastic service is one that allows its
> user to rapidly scale up or down their need for resources.
>
> A number of open source projects and companies have been created to
> implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
> the source under GNU General Public License version 3 ("GPL v3") in 2010.
> Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix
> re-licensed the CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed
> by an independent foundation such as ASF. Vendor influence and/or
> proprietary implementations may limit the community's ability to choose the
> hardware and software for use in the datacenter. The community at large
> will benefit from the ability to enhance the orchestration layer as needed
> for particular hardware or software support, and to implement algorithms
> and features that may reduce cost or increase user satisfaction for
> specific use cases. In this respect the independent nature of the ASF is
> key to the long term health and success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is
> accepted and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack
> source includes only third party code that is licensed under the Apache
> License or open source licenses that are approved by the ASF for use in ASF
> projects. The CloudStack Project has begun the process of removing third
> party code that is not licensed under an ASF approved license. This is an
> ongoing process that will continue into the incubation period. Third party
> code contributed to CloudStack under the CloudStack contribution agreement
> was assigned to Cloud.com in exchange for distributing CloudStack under
> GPLv3. The CloudStack project has begun the process of amending the
> previous CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that
> an existing contributor does not consent to this change, the project is
> prepared to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents and discussions
> that should have been publicly available and accessible were not
> publicized. The Project's sec
Re: [VOTE] CloudStack for Apache Incubator
+1 binding
Dan
On Monday, April 09, 2012 06:32:24 PM Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the
> Incubator. The proposal is available at [1] and I have also included it
> below. Please vote with: +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00
> US-PST on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an
> IaaS cloud. It includes an HTTP-based API for user and administrator
> functions and a web UI for user and administrator access. Administrators
> can provision physical infrastructure (e.g., servers, network elements,
> storage) into an instance of CloudStack, while end users can use the
> CloudStack self-service API and UI for the provisioning and management of
> virtual machines, virtual disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these
> clouds provide virtual machines to end users. CloudStack additionally
> provides baremetal OS installation to end users via a self-service
> interface. The management of physical resources to provide the larger
> goal of cloud service delivery is known as "orchestration". IaaS clouds
> are usually described as "elastic" -- an elastic service is one that
> allows its user to rapidly scale up or down their need for resources.
>
> A number of open source projects and companies have been created to
> implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
> the source under GNU General Public License version 3 ("GPL v3") in 2010.
> Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix
> re-licensed the CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed
> by an independent foundation such as ASF. Vendor influence and/or
> proprietary implementations may limit the community's ability to choose
> the hardware and software for use in the datacenter. The community at
> large will benefit from the ability to enhance the orchestration layer as
> needed for particular hardware or software support, and to implement
> algorithms and features that may reduce cost or increase user
> satisfaction for specific use cases. In this respect the independent
> nature of the ASF is key to the long term health and success of the
> project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is
> accepted and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack
> source includes only third party code that is licensed under the Apache
> License or open source licenses that are approved by the ASF for use in
> ASF projects. The CloudStack Project has begun the process of removing
> third party code that is not licensed under an ASF approved license. This
> is an ongoing process that will continue into the incubation period.
> Third party code contributed to CloudStack under the CloudStack
> contribution agreement was assigned to Cloud.com in exchange for
> distributing CloudStack under GPLv3. The CloudStack project has begun the
> process of amending the previous CloudStack contribution agreements to
> obtain consent from existing contributors to change the CloudStack
> project's license. In the event that an existing contributor does not
> consent to this change, the project is prepared to remove that
> contributor's code. Additionally, there are binary dependencies on
> redistributed libraries that are not provided with an ASF-approved
> license. Finally, the CloudStack has source files incorporated from third
> parties that were not provided with an ASF-approved license. We have
> begun the process of re-writing this software. This is an ongoing process
> that will extend into the incubation period. These issues are discussed
> in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents and discussions
> that should have been publicly available and acces
Re: [VOTE] CloudStack for Apache Incubator
On 04/09/2012 09:32 PM, Kevin Kluge wrote: > Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. > The proposal is available at [1] and I have also included it below. Please > vote with: > +1: accept CloudStack into Incubator > +0: don't care > -1: do not accept CloudStack into Incubator (please explain the objection) > > The vote is open for at least 72 hours from now (until at least 19:00 US-PST > on April 12, 2012). > > Thanks for the consideration. > > -kevin > > [1] http://wiki.apache.org/incubator/CloudStackProposal > > > +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
+1 binding
-- dims
On Apr 10, 2012, at 9:52 AM, Daniel Kulp wrote:
>
> +1 binding
>
> Dan
>
>
>
> On Monday, April 09, 2012 06:32:24 PM Kevin Kluge wrote:
>> Hi All. I'd like to call for a VOTE for CloudStack to enter the
>> Incubator. The proposal is available at [1] and I have also included it
>> below. Please vote with: +1: accept CloudStack into Incubator
>> +0: don't care
>> -1: do not accept CloudStack into Incubator (please explain the objection)
>>
>> The vote is open for at least 72 hours from now (until at least 19:00
>> US-PST on April 12, 2012).
>>
>> Thanks for the consideration.
>>
>> -kevin
>>
>> [1] http://wiki.apache.org/incubator/CloudStackProposal
>>
>>
>>
>>
>> Abstract
>>
>> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
>> platform.
>>
>> Proposal
>>
>> CloudStack provides control plane software that can be used to create an
>> IaaS cloud. It includes an HTTP-based API for user and administrator
>> functions and a web UI for user and administrator access. Administrators
>> can provision physical infrastructure (e.g., servers, network elements,
>> storage) into an instance of CloudStack, while end users can use the
>> CloudStack self-service API and UI for the provisioning and management of
>> virtual machines, virtual disks, and virtual networks.
>>
>> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
>> code, documentation, websites, and trademarks to the Apache Software
>> Foundation ("ASF").
>>
>> Background
>>
>> Amazon and other cloud pioneers invented IaaS clouds. Typically these
>> clouds provide virtual machines to end users. CloudStack additionally
>> provides baremetal OS installation to end users via a self-service
>> interface. The management of physical resources to provide the larger
>> goal of cloud service delivery is known as "orchestration". IaaS clouds
>> are usually described as "elastic" -- an elastic service is one that
>> allows its user to rapidly scale up or down their need for resources.
>>
>> A number of open source projects and companies have been created to
>> implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
>> the source under GNU General Public License version 3 ("GPL v3") in 2010.
>> Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix
>> re-licensed the CloudStack source under Apache License v2 in April, 2012.
>>
>> Rationale
>>
>> IaaS clouds provide the ability to implement datacenter operations in a
>> programmable fashion. This functionality is tremendously powerful and
>> benefits the community by providing:
>>
>> - More efficient use of datacenter personnel
>> - More efficient use of datacenter hardware
>> - Better responsiveness to user requests
>> - Better uptime/availability through automation
>>
>> While there are several open source IaaS efforts today, none are governed
>> by an independent foundation such as ASF. Vendor influence and/or
>> proprietary implementations may limit the community's ability to choose
>> the hardware and software for use in the datacenter. The community at
>> large will benefit from the ability to enhance the orchestration layer as
>> needed for particular hardware or software support, and to implement
>> algorithms and features that may reduce cost or increase user
>> satisfaction for specific use cases. In this respect the independent
>> nature of the ASF is key to the long term health and success of the
>> project.
>>
>> Initial Goals
>>
>> The CloudStack project has two initial goals after the proposal is
>> accepted and the incubation has begun.
>>
>> The Cloudstack Project's first goal is to ensure that the CloudStack
>> source includes only third party code that is licensed under the Apache
>> License or open source licenses that are approved by the ASF for use in
>> ASF projects. The CloudStack Project has begun the process of removing
>> third party code that is not licensed under an ASF approved license. This
>> is an ongoing process that will continue into the incubation period.
>> Third party code contributed to CloudStack under the CloudStack
>> contribution agreement was assigned to Cloud.com in exchange for
>> distributing CloudStack under GPLv3. The CloudStack project has begun the
>> process of amending the previous CloudStack contribution agreements to
>> obtain consent from existing contributors to change the CloudStack
>> project's license. In the event that an existing contributor does not
>> consent to this change, the project is prepared to remove that
>> contributor's code. Additionally, there are binary dependencies on
>> redistributed libraries that are not provided with an ASF-approved
>> license. Finally, the CloudStack has source files incorporated from third
>> parties that were not provided with an ASF-approved license. We have
>> begun the process of re-writing this software. This is an ongoing process
>> that will extend into the incubation period. These issue
Re: [VOTE] CloudStack for Apache Incubator
+1 (non binding)
On Tue, Apr 10, 2012 at 10:51 AM, Davanum Srinivas wrote:
> +1 binding
>
> -- dims
>
>
> On Apr 10, 2012, at 9:52 AM, Daniel Kulp wrote:
>
>>
>> +1 binding
>>
>> Dan
>>
>>
>>
>> On Monday, April 09, 2012 06:32:24 PM Kevin Kluge wrote:
>>> Hi All. I'd like to call for a VOTE for CloudStack to enter the
>>> Incubator. The proposal is available at [1] and I have also included it
>>> below. Please vote with: +1: accept CloudStack into Incubator
>>> +0: don't care
>>> -1: do not accept CloudStack into Incubator (please explain the objection)
>>>
>>> The vote is open for at least 72 hours from now (until at least 19:00
>>> US-PST on April 12, 2012).
>>>
>>> Thanks for the consideration.
>>>
>>> -kevin
>>>
>>> [1] http://wiki.apache.org/incubator/CloudStackProposal
>>>
>>>
>>>
>>>
>>> Abstract
>>>
>>> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
>>> platform.
>>>
>>> Proposal
>>>
>>> CloudStack provides control plane software that can be used to create an
>>> IaaS cloud. It includes an HTTP-based API for user and administrator
>>> functions and a web UI for user and administrator access. Administrators
>>> can provision physical infrastructure (e.g., servers, network elements,
>>> storage) into an instance of CloudStack, while end users can use the
>>> CloudStack self-service API and UI for the provisioning and management of
>>> virtual machines, virtual disks, and virtual networks.
>>>
>>> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
>>> code, documentation, websites, and trademarks to the Apache Software
>>> Foundation ("ASF").
>>>
>>> Background
>>>
>>> Amazon and other cloud pioneers invented IaaS clouds. Typically these
>>> clouds provide virtual machines to end users. CloudStack additionally
>>> provides baremetal OS installation to end users via a self-service
>>> interface. The management of physical resources to provide the larger
>>> goal of cloud service delivery is known as "orchestration". IaaS clouds
>>> are usually described as "elastic" -- an elastic service is one that
>>> allows its user to rapidly scale up or down their need for resources.
>>>
>>> A number of open source projects and companies have been created to
>>> implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
>>> the source under GNU General Public License version 3 ("GPL v3") in 2010.
>>> Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix
>>> re-licensed the CloudStack source under Apache License v2 in April, 2012.
>>>
>>> Rationale
>>>
>>> IaaS clouds provide the ability to implement datacenter operations in a
>>> programmable fashion. This functionality is tremendously powerful and
>>> benefits the community by providing:
>>>
>>> - More efficient use of datacenter personnel
>>> - More efficient use of datacenter hardware
>>> - Better responsiveness to user requests
>>> - Better uptime/availability through automation
>>>
>>> While there are several open source IaaS efforts today, none are governed
>>> by an independent foundation such as ASF. Vendor influence and/or
>>> proprietary implementations may limit the community's ability to choose
>>> the hardware and software for use in the datacenter. The community at
>>> large will benefit from the ability to enhance the orchestration layer as
>>> needed for particular hardware or software support, and to implement
>>> algorithms and features that may reduce cost or increase user
>>> satisfaction for specific use cases. In this respect the independent
>>> nature of the ASF is key to the long term health and success of the
>>> project.
>>>
>>> Initial Goals
>>>
>>> The CloudStack project has two initial goals after the proposal is
>>> accepted and the incubation has begun.
>>>
>>> The Cloudstack Project's first goal is to ensure that the CloudStack
>>> source includes only third party code that is licensed under the Apache
>>> License or open source licenses that are approved by the ASF for use in
>>> ASF projects. The CloudStack Project has begun the process of removing
>>> third party code that is not licensed under an ASF approved license. This
>>> is an ongoing process that will continue into the incubation period.
>>> Third party code contributed to CloudStack under the CloudStack
>>> contribution agreement was assigned to Cloud.com in exchange for
>>> distributing CloudStack under GPLv3. The CloudStack project has begun the
>>> process of amending the previous CloudStack contribution agreements to
>>> obtain consent from existing contributors to change the CloudStack
>>> project's license. In the event that an existing contributor does not
>>> consent to this change, the project is prepared to remove that
>>> contributor's code. Additionally, there are binary dependencies on
>>> redistributed libraries that are not provided with an ASF-approved
>>> license. Finally, the CloudStack has source files incorporated from third
>>> parties that were not provided with an A
Re: [VOTE] CloudStack for Apache Incubator
+ 1 (non-binding). Looking forward for this project to succeed.
Suresh
On Apr 9, 2012, at 9:32 PM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open sourc
Re: [VOTE] CloudStack for Apache Incubator
+1,
Deepal
> +1 (non binding)
>
> On Tue, Apr 10, 2012 at 10:51 AM, Davanum Srinivas wrote:
>> +1 binding
>>
>> -- dims
>>
>>
>> On Apr 10, 2012, at 9:52 AM, Daniel Kulp wrote:
>>
>>> +1 binding
>>>
>>> Dan
>>>
>>>
>>>
>>> On Monday, April 09, 2012 06:32:24 PM Kevin Kluge wrote:
Hi All. I'd like to call for a VOTE for CloudStack to enter the
Incubator. The proposal is available at [1] and I have also included it
below. Please vote with: +1: accept CloudStack into Incubator
+0: don't care
-1: do not accept CloudStack into Incubator (please explain the objection)
The vote is open for at least 72 hours from now (until at least 19:00
US-PST on April 12, 2012).
Thanks for the consideration.
-kevin
[1] http://wiki.apache.org/incubator/CloudStackProposal
Abstract
CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
platform.
Proposal
CloudStack provides control plane software that can be used to create an
IaaS cloud. It includes an HTTP-based API for user and administrator
functions and a web UI for user and administrator access. Administrators
can provision physical infrastructure (e.g., servers, network elements,
storage) into an instance of CloudStack, while end users can use the
CloudStack self-service API and UI for the provisioning and management of
virtual machines, virtual disks, and virtual networks.
Citrix Systems, Inc. submits this proposal to donate the CloudStack source
code, documentation, websites, and trademarks to the Apache Software
Foundation ("ASF").
Background
Amazon and other cloud pioneers invented IaaS clouds. Typically these
clouds provide virtual machines to end users. CloudStack additionally
provides baremetal OS installation to end users via a self-service
interface. The management of physical resources to provide the larger
goal of cloud service delivery is known as "orchestration". IaaS clouds
are usually described as "elastic" -- an elastic service is one that
allows its user to rapidly scale up or down their need for resources.
A number of open source projects and companies have been created to
implement IaaS clouds. Cloud.com started CloudStack in 2008 and released
the source under GNU General Public License version 3 ("GPL v3") in 2010.
Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix
re-licensed the CloudStack source under Apache License v2 in April, 2012.
Rationale
IaaS clouds provide the ability to implement datacenter operations in a
programmable fashion. This functionality is tremendously powerful and
benefits the community by providing:
- More efficient use of datacenter personnel
- More efficient use of datacenter hardware
- Better responsiveness to user requests
- Better uptime/availability through automation
While there are several open source IaaS efforts today, none are governed
by an independent foundation such as ASF. Vendor influence and/or
proprietary implementations may limit the community's ability to choose
the hardware and software for use in the datacenter. The community at
large will benefit from the ability to enhance the orchestration layer as
needed for particular hardware or software support, and to implement
algorithms and features that may reduce cost or increase user
satisfaction for specific use cases. In this respect the independent
nature of the ASF is key to the long term health and success of the
project.
Initial Goals
The CloudStack project has two initial goals after the proposal is
accepted and the incubation has begun.
The Cloudstack Project's first goal is to ensure that the CloudStack
source includes only third party code that is licensed under the Apache
License or open source licenses that are approved by the ASF for use in
ASF projects. The CloudStack Project has begun the process of removing
third party code that is not licensed under an ASF approved license. This
is an ongoing process that will continue into the incubation period.
Third party code contributed to CloudStack under the CloudStack
contribution agreement was assigned to Cloud.com in exchange for
distributing CloudStack under GPLv3. The CloudStack project has begun the
process of amending the previous CloudStack contribution agreements to
obtain consent from existing contributors to change the CloudStack
project's license. In the event that an existing contributor does not
consent to this change, the project is prepared to remove that
contributor's code. Additionally, there are binary dependencies on
redistributed libraries that are not provided with an ASF-approved
RE: [VOTE] CloudStack for Apache Incubator
+1 (non-binding)
Sander
OSS Watch - supporting open source in education and research
http://www.oss-watch.ac.uk
> -Original Message-
> From: Kevin Kluge [mailto:kevin.kl...@citrix.com]
> Sent: 10 April 2012 02:32
> To: general@incubator.apache.org
> Subject: [VOTE] CloudStack for Apache Incubator
>
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix acquired
> Cloud.com, including CloudStack, in 2011. Citrix re-licensed the CloudStack
> source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and benefits
> the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects. The
> CloudStack Project has begun the process of removing third party code that is
> not licensed under an ASF approved license. This is an ongoing process that
> will continue into the incubation period. Third party code contributed to
> CloudStack under the CloudStack contribution agreement was assigned to
> Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack
> project has begun the process of amending the previous CloudStack contribution
> agreements to obtain consent from existing contributors to change the
> CloudStack project's license. In the event that an existing contributor does
> not consent to this change, the project is prepared to remove that
> contributor's code. Additionally, there are binary dependencies on
> redistributed libraries that are not provided with an ASF-approved license.
> Finally, the CloudStack has source files incorporated from third parties that
> were not provided with an ASF-approved license. We have begun the process of
> re-writing this software. This is an ongoing process that will ex
Re: [VOTE] CloudStack for Apache Incubator
+1 binding Regards, Alan On Apr 9, 2012, at 6:32 PM, Kevin Kluge wrote: > Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. > The proposal is available at [1] and I have also included it below. Please > vote with: > +1: accept CloudStack into Incubator > +0: don't care > -1: do not accept CloudStack into Incubator (please explain the objection) > > The vote is open for at least 72 hours from now (until at least 19:00 US-PST > on April 12, 2012). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.9.0-incubating (RC4)
Hi Sebb, The third party libraries we included were actually all source code, just compressed in tar.gz files to save space. There were no JARs or binaries. Is distributing their source code okay, or is it still better to get people to download them elsewhere? Matei On Apr 10, 2012, at 6:03 AM, sebb wrote: > On 8 April 2012 23:48, Benjamin Hindman wrote: >> Hi Sebb, >> >> Thanks so much for taking a look! Responses inline. >> >> On Sun, Apr 8, 2012 at 2:22 PM, sebb wrote: >> >>> On 7 April 2012 02:59, Benjamin Hindman wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.9.0. This will be the first incubator release for Mesos in Apache, but the fifth release candidate. Vote thread on mesos-...@incubator.apache.org: >>> http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201203.mbox/%3CCAFeOQnW7jk-VcTFpUP-_VonL99JCnggKeNPW%2BGx-Ozdy1U8sjg%40mail.gmail.com%3E The candidate for Mesos 0.9.0-incubating release is available at: >>> http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz The tag to be voted on: >>> https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4 >>> >>> The NOTICE file is incomplete; the product name and copyright year(s) >>> are missing. >>> >> >> Thanks, I'll add that. >> >> >>> The LICENSE file includes references to several 3rd party items. >>> It looks like glog and utilities.cc and others may require mention in >>> NOTICE. >>> >> >> Is there a document somewhere which describes when something needs to go >> into NOTICE in addition to LICENSE? I had read previously read the section >> titled "What Are Required Third-Party Notices?" from >> http://apache.org/legal/resolved.html#required-third-party-notices but I >> still was unclear whether or not anything needed to be done. > > AFAIK, it depends on what the license says. > >> >>> There's no DISCLAIMER file in SVN root. >>> >> >> Right, I'll add that. >> >> >>> There are several 3rd party libraries in SVN under >>> >>> >>> https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4/third_party/ >> >> >> This was deliberate, so as to make it easier to use for both developers >> (who check out the repository) and users (who download a distribution). Is >> there a policy against this? I saw this as analogous to distributing JARs. >> > > AIUI, there must be a source-only release. > This should have N&L files that relate to the source only. > > A binary release may also be provided, in which case its N&L files > need to correspond with what is in the binary release. > > For building from source, the dependencies need to be provided somehow. > Various options are possible: > - written instructions how to get the dependencies and where to put them > - separate script to download the dependencies > - build process automatically downloads the dependencies. > > Depending on the licenses of 3rd party jars you may need to provide a > combination of methods. > There are some types of dependencies that can only be included if the > user makes a deliberate choice of downloading them, see the cited doc. > > If all the dependencies are binary-distributable, it's probably also > OK to provide an archive containing just the dependencies. > This must have the relevant N&L files. > >> >> Is the correct next step to cancel this vote, > > IMO, yes. > >> create a RC5, and start a new vote thread for that? > > Once the issues have been resolved, yes. > >> Or modify RC4? > > No, RCs should be immutable. Otherwise how can one tell what one is voting on? > >> Thank you very much! >> >> Ben. >> >> >> The MD5 checksum of the tarball can be found at: >>> http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.md5 The signature of the tarball can be found at: >>> http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.9.0-incubating! The vote is open until Tuesday, April 10th at 8 pm (a bit more than 72 hours since it's over the weekend) and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.9.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos. >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> > >
Re: [VOTE] CloudStack for Apache Incubator
+1 binding
Ralph
On Apr 9, 2012, at 6:32 PM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents and discussions
> that should
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding)
On Apr 9, 2012, at 6:32 PM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents and discussions
> that should have
Re: Spam on the Incubator wiki
Hi Gavin, On Tue, Apr 10, 2012 at 11:36 AM, Gavin McDonald wrote: > I'm seeing more and more spam appear, just give me the nod and it'll be > done. You're the man! With no objections raised, please make the change. Thanks! BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
+1 from me (binding).
Thanks!
Cheers,
Chris
On Apr 9, 2012, at 6:32 PM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents an
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding)
Hadrian
On 04/09/2012 09:32 PM, Kevin Kluge wrote:
Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
The proposal is available at [1] and I have also included it below. Please
vote with:
+1: accept CloudStack into Incubator
+0: don't care
-1: do not accept CloudStack into Incubator (please explain the objection)
The vote is open for at least 72 hours from now (until at least 19:00 US-PST on
April 12, 2012).
Thanks for the consideration.
-kevin
[1] http://wiki.apache.org/incubator/CloudStackProposal
Abstract
CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
platform.
Proposal
CloudStack provides control plane software that can be used to create an IaaS
cloud. It includes an HTTP-based API for user and administrator functions and a
web UI for user and administrator access. Administrators can provision physical
infrastructure (e.g., servers, network elements, storage) into an instance of
CloudStack, while end users can use the CloudStack self-service API and UI for
the provisioning and management of virtual machines, virtual disks, and virtual
networks.
Citrix Systems, Inc. submits this proposal to donate the CloudStack source code,
documentation, websites, and trademarks to the Apache Software Foundation
("ASF").
Background
Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual
machines to end users. CloudStack additionally provides baremetal OS installation to end users via
a self-service interface. The management of physical resources to provide the larger goal of cloud
service delivery is known as "orchestration". IaaS clouds are usually described as
"elastic" -- an elastic service is one that allows its user to rapidly scale up or down
their need for resources.
A number of open source projects and companies have been created to implement IaaS
clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General
Public License version 3 ("GPL v3") in 2010. Citrix acquired Cloud.com,
including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache
License v2 in April, 2012.
Rationale
IaaS clouds provide the ability to implement datacenter operations in a
programmable fashion. This functionality is tremendously powerful and benefits
the community by providing:
- More efficient use of datacenter personnel
- More efficient use of datacenter hardware
- Better responsiveness to user requests
- Better uptime/availability through automation
While there are several open source IaaS efforts today, none are governed by an
independent foundation such as ASF. Vendor influence and/or proprietary
implementations may limit the community's ability to choose the hardware and
software for use in the datacenter. The community at large will benefit from
the ability to enhance the orchestration layer as needed for particular
hardware or software support, and to implement algorithms and features that may
reduce cost or increase user satisfaction for specific use cases. In this
respect the independent nature of the ASF is key to the long term health and
success of the project.
Initial Goals
The CloudStack project has two initial goals after the proposal is accepted and
the incubation has begun.
The Cloudstack Project's first goal is to ensure that the CloudStack source
includes only third party code that is licensed under the Apache License or
open source licenses that are approved by the ASF for use in ASF projects. The
CloudStack Project has begun the process of removing third party code that is
not licensed under an ASF approved license. This is an ongoing process that
will continue into the incubation period. Third party code contributed to
CloudStack under the CloudStack contribution agreement was assigned to
Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack
project has begun the process of amending the previous CloudStack contribution
agreements to obtain consent from existing contributors to change the
CloudStack project's license. In the event that an existing contributor does
not consent to this change, the project is prepared to remove that
contributor's code. Additionally, there are binary dependencies on
redistributed libraries that
are not provided with an ASF-approved license. Finally, the CloudStack has source files incorporated from third parties that were not provided with an ASF-approved license. We have begun the process of re-writing this software. This is an ongoing process that will extend into the incubation period. These issues are discussed in more detail later in the proposal.
Although CloudStack is open source, many design documents and discussions that
should have been publicly available and accessible were not publicized. The
Project's second goal will be to fix this lack of transparency by encouraging
the initial committers to publicize technical documentati
Any23 status (Was: [Incubator Wiki] Trivial Update of "April2012" by LewisJohnMcgibbney)
Hi, Thanks for the report, Any23! On Mon, Apr 2, 2012 at 2:24 PM, Apache Wiki wrote: > + Anything To Triples (any23) is a library, a web service and a command line > tool that extracts > + structured data in RDF format from a variety of Web documents. [...] This should be sufficient as the project description in the context of a board report. The list of supported formats, while interesting, is less relevant in this context. Please also include a note of when Any23 entered incubation. I took the liberty of adding that information to your report. > + - The community has seen steady levels of traffic with the dev list > receiving 281 hits in March; an > + increase from the previous month. > [...] > + - We are very close to VOTE'ing on the 0.7.0-incubating release (1st during > incubation), and Simone > + Tripodi has stepped up as release manager. We are currently discussing when > to push for the RC. Sounds like good progress! In future reports it would be good if you included the list of most important issues to solve before graduation. Your January report listed the following: > 1. Port Any23 code to ASF infrastructure and update license headers > 2. Develop a strong community with organizational diversity and with > strong connections to other relevant ASF communities. > 3. At least one Any23 incubating release Based on your current report it sounds like 1 is already solved and 3 will be done shortly. What's your status on 2? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding) Good luck! Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Any23 status (Was: [Incubator Wiki] Trivial Update of "April2012" by LewisJohnMcgibbney)
Hi Jukka, On Apr 10, 2012, at 2:46 PM, Jukka Zitting wrote: > > In future reports it would be good if you included the list of most > important issues to solve before graduation. Your January report > listed the following: > >> 1. Port Any23 code to ASF infrastructure and update license headers >> 2. Develop a strong community with organizational diversity and with >> strong connections to other relevant ASF communities. >> 3. At least one Any23 incubating release > > Based on your current report it sounds like 1 is already solved and 3 > will be done shortly. What's your status on 2? I think my opinion on #2 is that we are still working to do that. The great news is that Andy Seaborne from Jena is onboard as a committer and PPMC member, helping to bridge the semantic web efforts, and we are starting to have some cross pollination (e.g., with the recent GeoSPARQL thread and with efforts from Paolo). So, lots of activity, mainly driven by the original guys, but slowly growing and showing really good progress iMHO. And, to add, Lewis wasn't one of the original team that started Any23, pre-Apache, so the fact that Lewis has stepped up and is really helping to charge forward is a great sign of diversity too. My 2c. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding)
From: Kevin Kluge
Sent: 4/9/2012 18:32
To: general@incubator.apache.org
Subject: [VOTE] CloudStack for Apache Incubator
Hi All. I'd like to call for a VOTE for CloudStack to enter the
Incubator. The proposal is available at [1] and I have also included
it below. Please vote with:
+1: accept CloudStack into Incubator
+0: don't care
-1: do not accept CloudStack into Incubator (please explain the objection)
The vote is open for at least 72 hours from now (until at least 19:00
US-PST on April 12, 2012).
Thanks for the consideration.
-kevin
[1] http://wiki.apache.org/incubator/CloudStackProposal
Abstract
CloudStack is an IaaS ("Infrastracture as a Service") cloud
orchestration platform.
Proposal
CloudStack provides control plane software that can be used to create
an IaaS cloud. It includes an HTTP-based API for user and
administrator functions and a web UI for user and administrator
access. Administrators can provision physical infrastructure (e.g.,
servers, network elements, storage) into an instance of CloudStack,
while end users can use the CloudStack self-service API and UI for the
provisioning and management of virtual machines, virtual disks, and
virtual networks.
Citrix Systems, Inc. submits this proposal to donate the CloudStack
source code, documentation, websites, and trademarks to the Apache
Software Foundation ("ASF").
Background
Amazon and other cloud pioneers invented IaaS clouds. Typically these
clouds provide virtual machines to end users. CloudStack additionally
provides baremetal OS installation to end users via a self-service
interface. The management of physical resources to provide the larger
goal of cloud service delivery is known as "orchestration". IaaS
clouds are usually described as "elastic" -- an elastic service is one
that allows its user to rapidly scale up or down their need for
resources.
A number of open source projects and companies have been created to
implement IaaS clouds. Cloud.com started CloudStack in 2008 and
released the source under GNU General Public License version 3 ("GPL
v3") in 2010. Citrix acquired Cloud.com, including CloudStack, in
2011. Citrix re-licensed the CloudStack source under Apache License v2
in April, 2012.
Rationale
IaaS clouds provide the ability to implement datacenter operations in
a programmable fashion. This functionality is tremendously powerful
and benefits the community by providing:
- More efficient use of datacenter personnel
- More efficient use of datacenter hardware
- Better responsiveness to user requests
- Better uptime/availability through automation
While there are several open source IaaS efforts today, none are
governed by an independent foundation such as ASF. Vendor influence
and/or proprietary implementations may limit the community's ability
to choose the hardware and software for use in the datacenter. The
community at large will benefit from the ability to enhance the
orchestration layer as needed for particular hardware or software
support, and to implement algorithms and features that may reduce cost
or increase user satisfaction for specific use cases. In this respect
the independent nature of the ASF is key to the long term health and
success of the project.
Initial Goals
The CloudStack project has two initial goals after the proposal is
accepted and the incubation has begun.
The Cloudstack Project's first goal is to ensure that the CloudStack
source includes only third party code that is licensed under the
Apache License or open source licenses that are approved by the ASF
for use in ASF projects. The CloudStack Project has begun the process
of removing third party code that is not licensed under an ASF
approved license. This is an ongoing process that will continue into
the incubation period. Third party code contributed to CloudStack
under the CloudStack contribution agreement was assigned to Cloud.com
in exchange for distributing CloudStack under GPLv3. The CloudStack
project has begun the process of amending the previous CloudStack
contribution agreements to obtain consent from existing contributors
to change the CloudStack project's license. In the event that an
existing contributor does not consent to this change, the project is
prepared to remove that contributor's code. Additionally, there are
binary dependencies on redistributed libraries that are not provided
with an ASF-approved license. Finally, the CloudStack has source files
incorporated from third parties that were not provided with an
ASF-approved license. We have begun the process of re-writing this
software. This is an ongoing process that will extend into the
incubation period. These issues are discussed in more detail later in
the proposal.
Although CloudStack is open source, many design documents and
discussions that should have been publicly available and accessible
were not publicized. The Project's second goal will be to fix this
lack of transparency by encouraging the initial committers to
publicize tech
Re: [VOTE] CloudStack for Apache Incubator
+1!
On Wed, Apr 11, 2012 at 7:34 AM, Gianugo Rabellino wrote:
> +1 (binding)
>
>
> From: Kevin Kluge
> Sent: 4/9/2012 18:32
> To: general@incubator.apache.org
> Subject: [VOTE] CloudStack for Apache Incubator
> Hi All. I'd like to call for a VOTE for CloudStack to enter the
> Incubator. The proposal is available at [1] and I have also included
> it below. Please vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00
> US-PST on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud
> orchestration platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create
> an IaaS cloud. It includes an HTTP-based API for user and
> administrator functions and a web UI for user and administrator
> access. Administrators can provision physical infrastructure (e.g.,
> servers, network elements, storage) into an instance of CloudStack,
> while end users can use the CloudStack self-service API and UI for the
> provisioning and management of virtual machines, virtual disks, and
> virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack
> source code, documentation, websites, and trademarks to the Apache
> Software Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these
> clouds provide virtual machines to end users. CloudStack additionally
> provides baremetal OS installation to end users via a self-service
> interface. The management of physical resources to provide the larger
> goal of cloud service delivery is known as "orchestration". IaaS
> clouds are usually described as "elastic" -- an elastic service is one
> that allows its user to rapidly scale up or down their need for
> resources.
>
> A number of open source projects and companies have been created to
> implement IaaS clouds. Cloud.com started CloudStack in 2008 and
> released the source under GNU General Public License version 3 ("GPL
> v3") in 2010. Citrix acquired Cloud.com, including CloudStack, in
> 2011. Citrix re-licensed the CloudStack source under Apache License v2
> in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in
> a programmable fashion. This functionality is tremendously powerful
> and benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are
> governed by an independent foundation such as ASF. Vendor influence
> and/or proprietary implementations may limit the community's ability
> to choose the hardware and software for use in the datacenter. The
> community at large will benefit from the ability to enhance the
> orchestration layer as needed for particular hardware or software
> support, and to implement algorithms and features that may reduce cost
> or increase user satisfaction for specific use cases. In this respect
> the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is
> accepted and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack
> source includes only third party code that is licensed under the
> Apache License or open source licenses that are approved by the ASF
> for use in ASF projects. The CloudStack Project has begun the process
> of removing third party code that is not licensed under an ASF
> approved license. This is an ongoing process that will continue into
> the incubation period. Third party code contributed to CloudStack
> under the CloudStack contribution agreement was assigned to Cloud.com
> in exchange for distributing CloudStack under GPLv3. The CloudStack
> project has begun the process of amending the previous CloudStack
> contribution agreements to obtain consent from existing contributors
> to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is
> prepared to remove that contributor's code. Additionally, there are
> binary dependencies on redistributed libraries that are not provided
> with an ASF-approved license. Finally, the CloudStack has source files
> incorporated from third parties that were not provided with an
> ASF-approved license. We have begun the process of re-writing this
> software. This is an ongoing process that will extend into the
> incubation period. These issues are discussed in more detail later in
> the proposal.
>
> Althou
Re: [VOTE] CloudStack for Apache Incubator
+1 (binding)
Tom
On Mon, Apr 9, 2012 at 6:32 PM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents and discussions
> that should have been publicly
Re: [VOTE] CloudStack for Apache Incubator
+1! (binding)
Arun
On Apr 10, 2012, at 7:02 AM, Kevin Kluge wrote:
> Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator.
> The proposal is available at [1] and I have also included it below. Please
> vote with:
> +1: accept CloudStack into Incubator
> +0: don't care
> -1: do not accept CloudStack into Incubator (please explain the objection)
>
> The vote is open for at least 72 hours from now (until at least 19:00 US-PST
> on April 12, 2012).
>
> Thanks for the consideration.
>
> -kevin
>
> [1] http://wiki.apache.org/incubator/CloudStackProposal
>
>
>
>
> Abstract
>
> CloudStack is an IaaS ("Infrastracture as a Service") cloud orchestration
> platform.
>
> Proposal
>
> CloudStack provides control plane software that can be used to create an IaaS
> cloud. It includes an HTTP-based API for user and administrator functions and
> a web UI for user and administrator access. Administrators can provision
> physical infrastructure (e.g., servers, network elements, storage) into an
> instance of CloudStack, while end users can use the CloudStack self-service
> API and UI for the provisioning and management of virtual machines, virtual
> disks, and virtual networks.
>
> Citrix Systems, Inc. submits this proposal to donate the CloudStack source
> code, documentation, websites, and trademarks to the Apache Software
> Foundation ("ASF").
>
> Background
>
> Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds
> provide virtual machines to end users. CloudStack additionally provides
> baremetal OS installation to end users via a self-service interface. The
> management of physical resources to provide the larger goal of cloud service
> delivery is known as "orchestration". IaaS clouds are usually described as
> "elastic" -- an elastic service is one that allows its user to rapidly scale
> up or down their need for resources.
>
> A number of open source projects and companies have been created to implement
> IaaS clouds. Cloud.com started CloudStack in 2008 and released the source
> under GNU General Public License version 3 ("GPL v3") in 2010. Citrix
> acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the
> CloudStack source under Apache License v2 in April, 2012.
>
> Rationale
>
> IaaS clouds provide the ability to implement datacenter operations in a
> programmable fashion. This functionality is tremendously powerful and
> benefits the community by providing:
>
> - More efficient use of datacenter personnel
> - More efficient use of datacenter hardware
> - Better responsiveness to user requests
> - Better uptime/availability through automation
>
> While there are several open source IaaS efforts today, none are governed by
> an independent foundation such as ASF. Vendor influence and/or proprietary
> implementations may limit the community's ability to choose the hardware and
> software for use in the datacenter. The community at large will benefit from
> the ability to enhance the orchestration layer as needed for particular
> hardware or software support, and to implement algorithms and features that
> may reduce cost or increase user satisfaction for specific use cases. In this
> respect the independent nature of the ASF is key to the long term health and
> success of the project.
>
> Initial Goals
>
> The CloudStack project has two initial goals after the proposal is accepted
> and the incubation has begun.
>
> The Cloudstack Project's first goal is to ensure that the CloudStack source
> includes only third party code that is licensed under the Apache License or
> open source licenses that are approved by the ASF for use in ASF projects.
> The CloudStack Project has begun the process of removing third party code
> that is not licensed under an ASF approved license. This is an ongoing
> process that will continue into the incubation period. Third party code
> contributed to CloudStack under the CloudStack contribution agreement was
> assigned to Cloud.com in exchange for distributing CloudStack under GPLv3.
> The CloudStack project has begun the process of amending the previous
> CloudStack contribution agreements to obtain consent from existing
> contributors to change the CloudStack project's license. In the event that an
> existing contributor does not consent to this change, the project is prepared
> to remove that contributor's code. Additionally, there are binary
> dependencies on redistributed libraries that are not provided with an
> ASF-approved license. Finally, the CloudStack has source files incorporated
> from third parties that were not provided with an ASF-approved license. We
> have begun the process of re-writing this software. This is an ongoing
> process that will extend into the incubation period. These issues are
> discussed in more detail later in the proposal.
>
> Although CloudStack is open source, many design documents and discussions
> that sho
