I'm with Joe on this, best to avoid an over specific mission statement. Should leave room to interpret and grow. Besides the simpler and more direct the statement the easier it is to consume and follow.
My 2 cents -KELCEY DAMAGE >-----Original Message----- >From: Joe Brockmeier [mailto:j...@zonker.net] >Sent: Monday, February 25, 2013 10:29 AM >To: cloudstack-dev@incubator.apache.org >Subject: Re: [DRAFT] Graduation resolution / IPMC vote email draft for >discussion > >On Fri, Feb 22, 2013, at 03:02 PM, Chip Childers wrote: >> > What happens if CloudStack starts to do more than manage large >networks of VMs ? >> > Pure theoretical speculation on my part. >> >> Very good point. We do bare-metal already. >> >> How about: >> >> "software to deploy and manage compute, storage and network services, >> as a highly available, highly scalable Infrastructure as a Service >> (IaaS) cloud computing platform" >> >> Thoughts? > >"software to provide Apache CloudStack, a highly available, scalable, >Infrastructure-as-a-Service (IaaS) cloud computing platform." > >or even > >"to provide Apache CloudStack, open source software that provides a highly >available, scalable, Infrastructure-as-a-Service (IaaS) cloud computing >platform." > >Looking at other charters, I don't think we need to get so specific as to discuss >compute, network, storage, etc. > >Best, > >jzb >-- >Joe Brockmeier >j...@zonker.net >Twitter: @jzb >http://www.dissociatedpress.net/
