incubator-cloudstack-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: REVISED (was Re: Talking Points for Graduation)
Date Thu, 21 Mar 2013 01:08:31 GMT
On Wed, Mar 20, 2013 at 05:20:37PM -0500, Joe Brockmeier wrote:
> Hi all, 
> 
> Revised talking points below: 
> 
> - Why graduation matters:
> 
> Graduation is about the community's readiness to operate as an open
> source project, it's not about the state of the code - which was already
> mature when CloudStack entered the incubator. What it means is that the
> project is self-governing and has sufficient participation from a
> diverse community that it has demonstrated to the Apache board that it's
> ready to act as a TLP and gets the Apache Way. 
> 
> From here, Apache CloudStack can operate more autonomously and that will
> make it easier for the project to do things like releases and promote
> itself. 
> 
> - What's the "Apache Way," and why should people care?
> 
> This can go pretty deep, see TheApacheWay.com for a really deep primer
> on The Apache Way. 
> 
> In one sentence, to quote Shane Curcuru, "The Apache Way is primarily
> about Community, Merit, and Openness, backed up by Pragmatism and
> Charity." 
> 
> - What's the target audience for Apache CloudStack, or how do I know if
> it works for my organization?
> 
> Apache CloudStack is an open source IaaS, so if your organization fits
> one of these descriptions, you probably would benefit:
> 
> * Service provider that wants to provide public IaaS cloud.
> 
> * Enterprise or another organization with sufficient computing resources
> that would benefit from aggregating resources, providing programmatic
> access, accounting, etc. 
> 
> - What it doesn't mean:
> 
> It's deeply important to emphasize that this has nothing to do with code
> maturity. One of the common misconceptions about incubating projects -
> and CloudStack - is that it is a "new" project and/or that the code is
> immature. We need to emphasize that CloudStack is mature software and
> has been since it entered the incubator. Graduation is about community
> readiness, not code readiness.
> 
> - What Apache CloudStack is:
> 
> Apache CloudStack is open source Infrastructure-as-a-Service software,
> and the community that produces the software. 
> 
> CloudStack is a turnkey product that supplies integrated components for
> many of the functions that organizations expect from an IaaS platform:
> the UI, API, accounting, networking, management, etc. - and works with a
> wide range of hypervisors, storage, and networking appliances. 
> 
> - Why Should an Organization Try CloudStack?
> 
> Maturity, stability, scalability, and community. 
> 
> * Maturity: Apache CloudStack is in use in many production deployments
> for private, public, and hybrid clouds.
> 
> * Stability: It's been proven as a stable platform with a number of
> long-term deployments that have seen little or no downtime. 
> 
> * Scalability: CloudStack has been used in environments with more than
> 30,000 physical nodes and is also used in geo-distributed environments
> with data centers all over the globe. 
> 
> * Community: As part of the Apache Software Foundation, CloudStack's
> community is diverse, friendly, and one that puts all contributors on
> equal footing. The Apache governance model is well-understood and open. 
> 
> - What's next for the project?
> 
> Currently, the community is working on two releases.  4.0.2 is a
> bug-fix release for the 4.0 feature release.  4.1.0 is our next major 
> feature release.  Both releases are very close to being completed.
> 
> Users of Apache CloudStack can expect a new feature release
> approximately every four months. The community has created a time-based
> release model which allows for features to be build independently from
> the releases themselves, and integrated at an appropriate time to be
> part of the available feature release cycle.  Bug-fix releases will
> continue to take place in between each major feature release, as needed.
> Moving beyond our upcoming 4.1.0 feature release, the community is
> already hard at work on many features expected to be included in 4.2.0.
> 
> As with all projects in the ASF, project technical decisions are made by
> the community through consensus gathering and open discussion.  Apache
> CloudStack's features and architecture are constantly growing and
> evolving, based on the efforts of the community.
> 
>                                  ###
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> http://dissociatedpress.net/
> Twitter: @jzb
>

Perfect.  Let's make sure that any PMC members we hook up with press
have this (just in case they still aren't on this list).

Which reminds me (perhaps off topic for this thread), but have press
feelers been sent and / or list of contacts finalized?

Mime
View raw message