You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@cloudstack.apache.org by Joe Brockmeier <jz...@zonker.net> on 2013/03/05 00:09:20 UTC
Elevator Pitch / Top N Features
Hey all,
One of the things I'd like to work on in the next few weeks (as we get
ready for 4.1) is to make the text on our landing page (CloudStack.org)
a little more enticing/descriptive for folks.
Specifically I'd like to tighten up the "What Is?" section and highlight
between eight and 10 features (max) on the front page.
So - what features should we highlight? What are the *most* compelling
things about Apache CloudStack. Essentially, what's our elevator pitch
for CloudStack?
For example:
- Multi-hypervisor support (Xen, VMware, KVM)
- Apache-licensed
- Elegant UI that is a reference implementation of the native API
Thoughts? Suggestions?
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Re: Elevator Pitch / Top N Features
Posted by Noah Slater <ns...@apache.org>.
This is a great idea! And I wish we'd done this sooner on another project
I'm involved with.
It's easy to get distracted with shiny things. But what is CloudStack's
*story*? I don't think UI or the license count.
I'd think about it in terms of, if you had to strip back CloudStack to the
two or three architectural features that define it. That you'd put at the
core of your design doc if you were to start over... What are they?
On 4 March 2013 23:09, Joe Brockmeier <jz...@zonker.net> wrote:
> Hey all,
>
> One of the things I'd like to work on in the next few weeks (as we get
> ready for 4.1) is to make the text on our landing page (CloudStack.org)
> a little more enticing/descriptive for folks.
>
> Specifically I'd like to tighten up the "What Is?" section and highlight
> between eight and 10 features (max) on the front page.
>
> So - what features should we highlight? What are the *most* compelling
> things about Apache CloudStack. Essentially, what's our elevator pitch
> for CloudStack?
>
> For example:
>
> - Multi-hypervisor support (Xen, VMware, KVM)
> - Apache-licensed
> - Elegant UI that is a reference implementation of the native API
>
> Thoughts? Suggestions?
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
--
NS
Re: Elevator Pitch / Top N Features
Posted by Kelly Hair <ke...@citrix.com>.
Here's a starter list:
1. Purpose built for cloud.
2. Open Source large & growing community
3. APIs both open & also fully compatible with AWS.
4. Multi-Hypervisor support as well as bare metal provisioning.
5. Workload agnostic can support both enterprise workloads as well as
new cloud era architectures
6. Scalability. With region support this will grow even further.
7. Rich ecosystem.
8. Single pane of glass management.
On 3/5/13 12:57 AM, "Musayev, Ilya" <im...@webmd.net> wrote:
>Android tends to autocorrect - useleslly.
>
>Replace network releases with newer releases.
>
>"Musayev, Ilya" <im...@webmd.net> wrote:
>Joe
>
>Please start the draft page somewhere and I will pitch-in. We can use the
>same content on Wikipedia page as well.
>
>Also it would be nice to have "what cloudstack is now" and whats going to
>happen soon with network releases.
>
>Thanks
>Ilya
>
>kelcey Damage <ke...@backbonetechnology.com> wrote:
>Lol, you don't want to know my opinion of the UI from an Ops perspective
>( I
>do think it's very pretty and shiny, and I know Sonny has been working on
>alternative admin interfaces :) ).
>
>As for the elevator pitch one big thing that comes to mind is that we have
>the easiest API I have ever used. And that's a big deal.
>
>Thanks
>
>-----Original Message-----
>From: Joe Brockmeier [mailto:jzb@zonker.net]
>Sent: Monday, March 04, 2013 3:09 PM
>To: cloudstack-marketing@incubator.apache.org
>Subject: Elevator Pitch / Top N Features
>
>Hey all,
>
>One of the things I'd like to work on in the next few weeks (as we get
>ready
>for 4.1) is to make the text on our landing page (CloudStack.org) a little
>more enticing/descriptive for folks.
>
>Specifically I'd like to tighten up the "What Is?" section and highlight
>between eight and 10 features (max) on the front page.
>
>So - what features should we highlight? What are the *most* compelling
>things about Apache CloudStack. Essentially, what's our elevator pitch for
>CloudStack?
>
>For example:
>
>- Multi-hypervisor support (Xen, VMware, KVM)
>- Apache-licensed
>- Elegant UI that is a reference implementation of the native API
>
>Thoughts? Suggestions?
>
>Best,
>
>jzb
>--
>Joe Brockmeier
>jzb@zonker.net
>Twitter: @jzb
>http://www.dissociatedpress.net/
>
>
RE: Elevator Pitch / Top N Features
Posted by "Musayev, Ilya" <im...@webmd.net>.
Android tends to autocorrect - useleslly.
Replace network releases with newer releases.
"Musayev, Ilya" <im...@webmd.net> wrote:
Joe
Please start the draft page somewhere and I will pitch-in. We can use the same content on Wikipedia page as well.
Also it would be nice to have "what cloudstack is now" and whats going to happen soon with network releases.
Thanks
Ilya
kelcey Damage <ke...@backbonetechnology.com> wrote:
Lol, you don't want to know my opinion of the UI from an Ops perspective ( I
do think it's very pretty and shiny, and I know Sonny has been working on
alternative admin interfaces :) ).
As for the elevator pitch one big thing that comes to mind is that we have
the easiest API I have ever used. And that's a big deal.
Thanks
-----Original Message-----
From: Joe Brockmeier [mailto:jzb@zonker.net]
Sent: Monday, March 04, 2013 3:09 PM
To: cloudstack-marketing@incubator.apache.org
Subject: Elevator Pitch / Top N Features
Hey all,
One of the things I'd like to work on in the next few weeks (as we get ready
for 4.1) is to make the text on our landing page (CloudStack.org) a little
more enticing/descriptive for folks.
Specifically I'd like to tighten up the "What Is?" section and highlight
between eight and 10 features (max) on the front page.
So - what features should we highlight? What are the *most* compelling
things about Apache CloudStack. Essentially, what's our elevator pitch for
CloudStack?
For example:
- Multi-hypervisor support (Xen, VMware, KVM)
- Apache-licensed
- Elegant UI that is a reference implementation of the native API
Thoughts? Suggestions?
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Re: Elevator Pitch / Top N Features
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Mar 05, 2013 at 04:19:38PM +0000, Noah Slater wrote:
> As a community, it is in our interests to promote CloudStack and paint it
> in a positive light. This is at odds with the interests of
> an encyclopaedia, which is to report important facts about notable subjects
> from a neutral point of view. For these reasons, it is usually frowned upon
> to contribute to bios about yourself, your company, your works, etc.
That, plus what I said about wikipedia wanting to be a tertiary source. Any
updates should have a reference to a secondary source.
Re: Elevator Pitch / Top N Features
Posted by Robyn Bergeron <rb...@redhat.com>.
----- Original Message -----
> From: "Joe Brockmeier" <jz...@zonker.net>
> To: cloudstack-marketing@incubator.apache.org
> Sent: Tuesday, March 5, 2013 10:33:50 AM
> Subject: Re: Elevator Pitch / Top N Features
>
> On Tue, Mar 5, 2013, at 11:12 AM, Musayev, Ilya wrote:
> > I see your point, on the other hand, if you mention what is true,
> > you
> > don't overstate or beat your competitor, I don't believe we should
> > have
> > an issue.
> >
> > We are only mentioning the facts. In addition, many of us are not
> > affiliated with Citrix, though we are affiliated with the project
> > this is
> > still community lead effort.
>
> Not sure what a Citrix affiliation would have to do with Apache
> CloudStack. ;-)
>
> Being community led doesn't make a difference, IMHO, from the vantage
> of
> a Wikipedia "editor" who is looking at contributions coming in with
> an
> eye for bias/gaming the page.
>
> > I don't believe we should just let Wikipedia page stay outdated and
> > wait
> > for someone else to do it - as it may never happen - or happen with
> > considerable amount of delay (I.e. we are on version 4.1 and
> > article
> > mentions 3.x). Lots of things have changed since then and the
> > person who
> > updates the wiki may not have enough expertise to write about
> > something
> > he does not know about.
>
> Totally agree with this. If the wikipedia article says "current
> release
> is 3.x" then I think we're empowered to change that.
>
> For instance, looking at the page I noticed the stable release info
> was
> outdated - so I edited that. Purely factual, I can't imagine anyone
> can
> complain about that edit.
>
> On the other hand, coordinating on the list to discuss how to
> *promote*
> ACS via Wikipedia may well be viewed unfavorably.
>
> > If we stay ethically correct, state only facts, don't down play on
> > competitors and this comes from the community, my humble opinion,
> > we
> > should be ok.
> >
> > Thoughts?
>
> See above - but "comes from the community" won't necessarily be
> viewed
> as a "defense" if it looks like we're editing the page impartially.
>
> I think we should take an active interest in making sure the page is
> accurate and current, and any community member can do that. I start
> to
> worry when it comes to talking about using promotional text from our
> Web
> site on Wikipedia. That would probably be viewed unfavorably.
Perhaps it would be useful to have a release-day marketing task list, where a few kind volunteers can take care of various updates that need to be done - including perhaps updating the current basics of release information on wikipedia?
I think there's a subtle difference between "promotional text" and "just the basics" - when it comes to things like feature descriptions, I think there's certainly room for various interpretations that all have their own benefits, thought obviously it's a matter of who's willing to do the work, let alone do it in multiple ways :) The "just the facts" vs. "SHINY AND COMPELLING things you MUST HAVE!" marketing version is one way to look at it - wikipedia would obviously benefit more from "just the facts."
In the past, in Fedora (sorry, the only example I have) we've done Talking Points, which were intended for the purposes of letting the good people who help promote Fedora have a concise, human-readable (ie: not amazingly-detailed engineering-heavy) version of highlighted release features. Note that there are extended details, as well as a bulletpoint-type "bottom line" description, the latter being something that might be more easily extended to drop into wikipedia (IMO).
https://fedoraproject.org/wiki/Fedora_14_talking_points
-robyn
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
Re: Elevator Pitch / Top N Features
Posted by Joe Brockmeier <jz...@zonker.net>.
On Tue, Mar 5, 2013, at 11:12 AM, Musayev, Ilya wrote:
> I see your point, on the other hand, if you mention what is true, you
> don't overstate or beat your competitor, I don't believe we should have
> an issue.
>
> We are only mentioning the facts. In addition, many of us are not
> affiliated with Citrix, though we are affiliated with the project this is
> still community lead effort.
Not sure what a Citrix affiliation would have to do with Apache
CloudStack. ;-)
Being community led doesn't make a difference, IMHO, from the vantage of
a Wikipedia "editor" who is looking at contributions coming in with an
eye for bias/gaming the page.
> I don't believe we should just let Wikipedia page stay outdated and wait
> for someone else to do it - as it may never happen - or happen with
> considerable amount of delay (I.e. we are on version 4.1 and article
> mentions 3.x). Lots of things have changed since then and the person who
> updates the wiki may not have enough expertise to write about something
> he does not know about.
Totally agree with this. If the wikipedia article says "current release
is 3.x" then I think we're empowered to change that.
For instance, looking at the page I noticed the stable release info was
outdated - so I edited that. Purely factual, I can't imagine anyone can
complain about that edit.
On the other hand, coordinating on the list to discuss how to *promote*
ACS via Wikipedia may well be viewed unfavorably.
> If we stay ethically correct, state only facts, don't down play on
> competitors and this comes from the community, my humble opinion, we
> should be ok.
>
> Thoughts?
See above - but "comes from the community" won't necessarily be viewed
as a "defense" if it looks like we're editing the page impartially.
I think we should take an active interest in making sure the page is
accurate and current, and any community member can do that. I start to
worry when it comes to talking about using promotional text from our Web
site on Wikipedia. That would probably be viewed unfavorably.
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
RE: Elevator Pitch / Top N Features
Posted by "Musayev, Ilya" <im...@webmd.net>.
I see your point, on the other hand, if you mention what is true, you don't overstate or beat your competitor, I don't believe we should have an issue.
We are only mentioning the facts. In addition, many of us are not affiliated with Citrix, though we are affiliated with the project this is still community lead effort.
I don't believe we should just let Wikipedia page stay outdated and wait for someone else to do it - as it may never happen - or happen with considerable amount of delay (I.e. we are on version 4.1 and article mentions 3.x). Lots of things have changed since then and the person who updates the wiki may not have enough expertise to write about something he does not know about.
If we stay ethically correct, state only facts, don't down play on competitors and this comes from the community, my humble opinion, we should be ok.
Thoughts?
> -----Original Message-----
> From: Noah Slater [mailto:nslater@apache.org]
> Sent: Tuesday, March 05, 2013 11:20 AM
> To: cloudstack-marketing@incubator.apache.org
> Subject: Re: Elevator Pitch / Top N Features
>
> As a community, it is in our interests to promote CloudStack and paint it in a
> positive light. This is at odds with the interests of an encyclopaedia, which is
> to report important facts about notable subjects from a neutral point of
> view. For these reasons, it is usually frowned upon to contribute to bios
> about yourself, your company, your works, etc.
>
>
> On 5 March 2013 16:12, Musayev, Ilya <im...@webmd.net> wrote:
>
> > Noah,
> >
> > Thanks for the feedback,
> >
> > I'm a bit at loss, what conflict of interests do we have if it's a
> > community effort?
> >
> > Please clarify,
> >
> > Thanks
> > ilya
> >
> > > -----Original Message-----
> > > From: Noah Slater [mailto:nslater@apache.org]
> > > Sent: Tuesday, March 05, 2013 10:28 AM
> > > To: Noah Slater
> > > Cc: cloudstack-marketing@incubator.apache.org
> > > Subject: Re: Elevator Pitch / Top N Features
> > >
> > > Sorry, I really need to start clarifying this stuff. In the past,
> > > *on
> > previous
> > > projects*.
> > >
> > >
> > > On 5 March 2013 15:27, Noah Slater <ns...@apache.org> wrote:
> > >
> > > > In the past, I have asked members of the user@ and dev@ list to
> > > > pay attention to Wikipedia, and to update or correct as needed.
> > > > But we've kept it restricted to private individuals. We would
> > > > never co-ordinate on the public lists. Because obviously, as a
> > > > group, we have a conflict of interests, and it's best to just stay clear.
> > > >
> > > >
> > > > On 5 March 2013 14:49, Joe Brockmeier <jz...@zonker.net> wrote:
> > > >
> > > >> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
> > > >> > Please start the draft page somewhere and I will pitch-in. We
> > > >> > can use
> > > >> the
> > > >> > same content on Wikipedia page as well.
> > > >>
> > > >> I've started a page here: but remember the wiki motto is "edit
> > boldly."
> > > >> No need to ask someone else to create page on the wiki when you
> > > >> can do it yourself.
> > > >>
> > > >>
> > > >>
> > >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resou
> > > r
> > > >> ces+and+Proposals
> > > >>
> > > >> Also: I would be *very* careful about pushing content to Wikipedia.
> > > >> We should absolutely keep an eye on the Wikipedia page for
> > > >> CloudStack and keep it updated/accurate, but I think they frown
> > > >> on content that is overly promotional. What's acceptable for the
> > > >> Apache CloudStack Web site is not necessarily acceptable for the
> Wikipedia page.
> > > >>
> > > >> > Also it would be nice to have "what cloudstack is now" and
> > > >> > whats going
> > > >> to
> > > >> > happen soon with newer releases.
> > > >>
> > > >> (Fixed the Android auto-correct for you. Computers - aren't they
> > > >> wonderful?)
> > > >>
> > > >> A "What's new in CloudStack" section would make sense, sure.
> > > >>
> > > >> Best,
> > > >>
> > > >> jzb
> > > >> --
> > > >> Joe Brockmeier
> > > >> jzb@zonker.net
> > > >> Twitter: @jzb
> > > >> http://www.dissociatedpress.net/
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > NS
> > > >
> > >
> > >
> > >
> > > --
> > > NS
> >
> >
>
>
> --
> NS
Re: Elevator Pitch / Top N Features
Posted by Noah Slater <ns...@apache.org>.
As a community, it is in our interests to promote CloudStack and paint it
in a positive light. This is at odds with the interests of
an encyclopaedia, which is to report important facts about notable subjects
from a neutral point of view. For these reasons, it is usually frowned upon
to contribute to bios about yourself, your company, your works, etc.
On 5 March 2013 16:12, Musayev, Ilya <im...@webmd.net> wrote:
> Noah,
>
> Thanks for the feedback,
>
> I'm a bit at loss, what conflict of interests do we have if it's a
> community effort?
>
> Please clarify,
>
> Thanks
> ilya
>
> > -----Original Message-----
> > From: Noah Slater [mailto:nslater@apache.org]
> > Sent: Tuesday, March 05, 2013 10:28 AM
> > To: Noah Slater
> > Cc: cloudstack-marketing@incubator.apache.org
> > Subject: Re: Elevator Pitch / Top N Features
> >
> > Sorry, I really need to start clarifying this stuff. In the past, *on
> previous
> > projects*.
> >
> >
> > On 5 March 2013 15:27, Noah Slater <ns...@apache.org> wrote:
> >
> > > In the past, I have asked members of the user@ and dev@ list to pay
> > > attention to Wikipedia, and to update or correct as needed. But we've
> > > kept it restricted to private individuals. We would never co-ordinate
> > > on the public lists. Because obviously, as a group, we have a conflict
> > > of interests, and it's best to just stay clear.
> > >
> > >
> > > On 5 March 2013 14:49, Joe Brockmeier <jz...@zonker.net> wrote:
> > >
> > >> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
> > >> > Please start the draft page somewhere and I will pitch-in. We can
> > >> > use
> > >> the
> > >> > same content on Wikipedia page as well.
> > >>
> > >> I've started a page here: but remember the wiki motto is "edit
> boldly."
> > >> No need to ask someone else to create page on the wiki when you can
> > >> do it yourself.
> > >>
> > >>
> > >>
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resour
> > >> ces+and+Proposals
> > >>
> > >> Also: I would be *very* careful about pushing content to Wikipedia.
> > >> We should absolutely keep an eye on the Wikipedia page for CloudStack
> > >> and keep it updated/accurate, but I think they frown on content that
> > >> is overly promotional. What's acceptable for the Apache CloudStack
> > >> Web site is not necessarily acceptable for the Wikipedia page.
> > >>
> > >> > Also it would be nice to have "what cloudstack is now" and whats
> > >> > going
> > >> to
> > >> > happen soon with newer releases.
> > >>
> > >> (Fixed the Android auto-correct for you. Computers - aren't they
> > >> wonderful?)
> > >>
> > >> A "What's new in CloudStack" section would make sense, sure.
> > >>
> > >> Best,
> > >>
> > >> jzb
> > >> --
> > >> Joe Brockmeier
> > >> jzb@zonker.net
> > >> Twitter: @jzb
> > >> http://www.dissociatedpress.net/
> > >>
> > >
> > >
> > >
> > > --
> > > NS
> > >
> >
> >
> >
> > --
> > NS
>
>
--
NS
RE: Elevator Pitch / Top N Features
Posted by "Musayev, Ilya" <im...@webmd.net>.
Noah,
Thanks for the feedback,
I'm a bit at loss, what conflict of interests do we have if it's a community effort?
Please clarify,
Thanks
ilya
> -----Original Message-----
> From: Noah Slater [mailto:nslater@apache.org]
> Sent: Tuesday, March 05, 2013 10:28 AM
> To: Noah Slater
> Cc: cloudstack-marketing@incubator.apache.org
> Subject: Re: Elevator Pitch / Top N Features
>
> Sorry, I really need to start clarifying this stuff. In the past, *on previous
> projects*.
>
>
> On 5 March 2013 15:27, Noah Slater <ns...@apache.org> wrote:
>
> > In the past, I have asked members of the user@ and dev@ list to pay
> > attention to Wikipedia, and to update or correct as needed. But we've
> > kept it restricted to private individuals. We would never co-ordinate
> > on the public lists. Because obviously, as a group, we have a conflict
> > of interests, and it's best to just stay clear.
> >
> >
> > On 5 March 2013 14:49, Joe Brockmeier <jz...@zonker.net> wrote:
> >
> >> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
> >> > Please start the draft page somewhere and I will pitch-in. We can
> >> > use
> >> the
> >> > same content on Wikipedia page as well.
> >>
> >> I've started a page here: but remember the wiki motto is "edit boldly."
> >> No need to ask someone else to create page on the wiki when you can
> >> do it yourself.
> >>
> >>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resour
> >> ces+and+Proposals
> >>
> >> Also: I would be *very* careful about pushing content to Wikipedia.
> >> We should absolutely keep an eye on the Wikipedia page for CloudStack
> >> and keep it updated/accurate, but I think they frown on content that
> >> is overly promotional. What's acceptable for the Apache CloudStack
> >> Web site is not necessarily acceptable for the Wikipedia page.
> >>
> >> > Also it would be nice to have "what cloudstack is now" and whats
> >> > going
> >> to
> >> > happen soon with newer releases.
> >>
> >> (Fixed the Android auto-correct for you. Computers - aren't they
> >> wonderful?)
> >>
> >> A "What's new in CloudStack" section would make sense, sure.
> >>
> >> Best,
> >>
> >> jzb
> >> --
> >> Joe Brockmeier
> >> jzb@zonker.net
> >> Twitter: @jzb
> >> http://www.dissociatedpress.net/
> >>
> >
> >
> >
> > --
> > NS
> >
>
>
>
> --
> NS
Re: Elevator Pitch / Top N Features
Posted by Noah Slater <ns...@apache.org>.
Sorry, I really need to start clarifying this stuff. In the past, *on
previous projects*.
On 5 March 2013 15:27, Noah Slater <ns...@apache.org> wrote:
> In the past, I have asked members of the user@ and dev@ list to pay
> attention to Wikipedia, and to update or correct as needed. But we've kept
> it restricted to private individuals. We would never co-ordinate on the
> public lists. Because obviously, as a group, we have a conflict of
> interests, and it's best to just stay clear.
>
>
> On 5 March 2013 14:49, Joe Brockmeier <jz...@zonker.net> wrote:
>
>> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
>> > Please start the draft page somewhere and I will pitch-in. We can use
>> the
>> > same content on Wikipedia page as well.
>>
>> I've started a page here: but remember the wiki motto is "edit boldly."
>> No need to ask someone else to create page on the wiki when you can do
>> it yourself.
>>
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources+and+Proposals
>>
>> Also: I would be *very* careful about pushing content to Wikipedia. We
>> should absolutely keep an eye on the Wikipedia page for CloudStack and
>> keep it updated/accurate, but I think they frown on content that is
>> overly promotional. What's acceptable for the Apache CloudStack Web site
>> is not necessarily acceptable for the Wikipedia page.
>>
>> > Also it would be nice to have "what cloudstack is now" and whats going
>> to
>> > happen soon with newer releases.
>>
>> (Fixed the Android auto-correct for you. Computers - aren't they
>> wonderful?)
>>
>> A "What's new in CloudStack" section would make sense, sure.
>>
>> Best,
>>
>> jzb
>> --
>> Joe Brockmeier
>> jzb@zonker.net
>> Twitter: @jzb
>> http://www.dissociatedpress.net/
>>
>
>
>
> --
> NS
>
--
NS
Re: Elevator Pitch / Top N Features
Posted by Noah Slater <ns...@apache.org>.
In the past, I have asked members of the user@ and dev@ list to pay
attention to Wikipedia, and to update or correct as needed. But we've kept
it restricted to private individuals. We would never co-ordinate on the
public lists. Because obviously, as a group, we have a conflict of
interests, and it's best to just stay clear.
On 5 March 2013 14:49, Joe Brockmeier <jz...@zonker.net> wrote:
> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
> > Please start the draft page somewhere and I will pitch-in. We can use the
> > same content on Wikipedia page as well.
>
> I've started a page here: but remember the wiki motto is "edit boldly."
> No need to ask someone else to create page on the wiki when you can do
> it yourself.
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources+and+Proposals
>
> Also: I would be *very* careful about pushing content to Wikipedia. We
> should absolutely keep an eye on the Wikipedia page for CloudStack and
> keep it updated/accurate, but I think they frown on content that is
> overly promotional. What's acceptable for the Apache CloudStack Web site
> is not necessarily acceptable for the Wikipedia page.
>
> > Also it would be nice to have "what cloudstack is now" and whats going to
> > happen soon with newer releases.
>
> (Fixed the Android auto-correct for you. Computers - aren't they
> wonderful?)
>
> A "What's new in CloudStack" section would make sense, sure.
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
--
NS
Re: Elevator Pitch / Top N Features
Posted by Mathias Mullins <ma...@citrix.com>.
So my comments in-line.
Matt
On 3/5/13 5:53 PM, "Prodosh Banerjee" <p....@anolim.com> wrote:
>Here are my two cents - the main benefits and differentiators for
>Cloudstack compared to the competition:
>
>1. Proven technology: production ready
There are several folks not agreeing with this right now in the user
community. I personally agree with this but you don't want to community
disagreeing with your top markers.
>2. Easy to setup and use
Added this to #8 on the Wiki
>3. SDN - Software Defined Networking supported out of the box (this is
>one of the best differentiators)
Put this in as #2.
>4. High Availability for management nodes as well as HA support for VMs
Combining this with #5
>5. Proven scalability: manage huge clouds of thousands of servers today
>6. Support for the most common hypervisors out of the box: Xen, KVM,
>VMware etc.
Already in There
>7. Amazon Web Services compatible APIs
>8. Self service Web UI
>9. Usage metering
7/8/9 - Already in there
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources+an
d+Proposals
>
>
>Prodosh Banerjee
>Managing Partner, Anolim GmbH
>
>Tel: +41 76 465 9806
>Email: p.banerjee@anolim.com
>Web: http://anolim.com
>Skype: p.banerjee
>
>Alte Landstrasse 64
>8800 Thalwil
>
>On 05.03.2013, at 20:03, Mathias Mullins <ma...@citrix.com>
>wrote:
>
>> So I'm dropping back about 10 e-mails here back to Joe original thread
>> here to avoid the Wikipedia discussion. I've taken some of the pieces
>>that
>> Kelly added and expanded on them some in the Wiki. The #10 to be honest
>>is
>> weak, so if someone can help with one better that would help.
>>
>> Matt Mullins
>> CloudPlatform Implementation Engineer
>> Worldwide Cloud Services Citrix System, Inc.
>> +1 (407) 920-1107 Office/Cell Phone
>> matt.mullins@citrix.com
>>
>>
>>
>>
>>
>>
>> On 3/5/13 9:49 AM, "Joe Brockmeier" <jz...@zonker.net> wrote:
>>
>>> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
>>>> Please start the draft page somewhere and I will pitch-in. We can use
>>>> the
>>>> same content on Wikipedia page as well.
>>>
>>> I've started a page here: but remember the wiki motto is "edit boldly."
>>> No need to ask someone else to create page on the wiki when you can do
>>> it yourself.
>>>
>>>
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources
>>>+a
>>> nd+Proposals
>>>
>>> Also: I would be *very* careful about pushing content to Wikipedia. We
>>> should absolutely keep an eye on the Wikipedia page for CloudStack and
>>> keep it updated/accurate, but I think they frown on content that is
>>> overly promotional. What's acceptable for the Apache CloudStack Web
>>>site
>>> is not necessarily acceptable for the Wikipedia page.
>>>
>>>> Also it would be nice to have "what cloudstack is now" and whats going
>>>> to
>>>> happen soon with newer releases.
>>>
>>> (Fixed the Android auto-correct for you. Computers - aren't they
>>> wonderful?)
>>>
>>> A "What's new in CloudStack" section would make sense, sure.
>>>
>>> Best,
>>>
>>> jzb
>>> --
>>> Joe Brockmeier
>>> jzb@zonker.net
>>> Twitter: @jzb
>>> http://www.dissociatedpress.net/
>>
>
Re: Elevator Pitch / Top N Features
Posted by Kelly Hair <ke...@citrix.com>.
+1 SDNs - was working off an older 3.x list ;)
On 3/5/13 5:53 PM, "Prodosh Banerjee" <p....@anolim.com> wrote:
>Here are my two cents - the main benefits and differentiators for
>Cloudstack compared to the competition:
>
>1. Proven technology: production ready
>2. Easy to setup and use
>3. SDN - Software Defined Networking supported out of the box (this is
>one of the best differentiators)
>4. High Availability for management nodes as well as HA support for VMs
>5. Proven scalability: manage huge clouds of thousands of servers today
>6. Support for the most common hypervisors out of the box: Xen, KVM,
>VMware etc.
>7. Amazon Web Services compatible APIs
>8. Self service Web UI
>9. Usage metering
>
>
>Prodosh Banerjee
>Managing Partner, Anolim GmbH
>
>Tel: +41 76 465 9806
>Email: p.banerjee@anolim.com
>Web: http://anolim.com
>Skype: p.banerjee
>
>Alte Landstrasse 64
>8800 Thalwil
>
>On 05.03.2013, at 20:03, Mathias Mullins <ma...@citrix.com>
>wrote:
>
>> So I'm dropping back about 10 e-mails here back to Joe original thread
>> here to avoid the Wikipedia discussion. I've taken some of the pieces
>>that
>> Kelly added and expanded on them some in the Wiki. The #10 to be honest
>>is
>> weak, so if someone can help with one better that would help.
>>
>> Matt Mullins
>> CloudPlatform Implementation Engineer
>> Worldwide Cloud Services Citrix System, Inc.
>> +1 (407) 920-1107 Office/Cell Phone
>> matt.mullins@citrix.com
>>
>>
>>
>>
>>
>>
>> On 3/5/13 9:49 AM, "Joe Brockmeier" <jz...@zonker.net> wrote:
>>
>>> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
>>>> Please start the draft page somewhere and I will pitch-in. We can use
>>>> the
>>>> same content on Wikipedia page as well.
>>>
>>> I've started a page here: but remember the wiki motto is "edit boldly."
>>> No need to ask someone else to create page on the wiki when you can do
>>> it yourself.
>>>
>>>
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources
>>>+a
>>> nd+Proposals
>>>
>>> Also: I would be *very* careful about pushing content to Wikipedia. We
>>> should absolutely keep an eye on the Wikipedia page for CloudStack and
>>> keep it updated/accurate, but I think they frown on content that is
>>> overly promotional. What's acceptable for the Apache CloudStack Web
>>>site
>>> is not necessarily acceptable for the Wikipedia page.
>>>
>>>> Also it would be nice to have "what cloudstack is now" and whats going
>>>> to
>>>> happen soon with newer releases.
>>>
>>> (Fixed the Android auto-correct for you. Computers - aren't they
>>> wonderful?)
>>>
>>> A "What's new in CloudStack" section would make sense, sure.
>>>
>>> Best,
>>>
>>> jzb
>>> --
>>> Joe Brockmeier
>>> jzb@zonker.net
>>> Twitter: @jzb
>>> http://www.dissociatedpress.net/
>>
>
Re: Elevator Pitch / Top N Features
Posted by Prodosh Banerjee <p....@anolim.com>.
Here are my two cents - the main benefits and differentiators for Cloudstack compared to the competition:
1. Proven technology: production ready
2. Easy to setup and use
3. SDN - Software Defined Networking supported out of the box (this is one of the best differentiators)
4. High Availability for management nodes as well as HA support for VMs
5. Proven scalability: manage huge clouds of thousands of servers today
6. Support for the most common hypervisors out of the box: Xen, KVM, VMware etc.
7. Amazon Web Services compatible APIs
8. Self service Web UI
9. Usage metering
Prodosh Banerjee
Managing Partner, Anolim GmbH
Tel: +41 76 465 9806
Email: p.banerjee@anolim.com
Web: http://anolim.com
Skype: p.banerjee
Alte Landstrasse 64
8800 Thalwil
On 05.03.2013, at 20:03, Mathias Mullins <ma...@citrix.com> wrote:
> So I'm dropping back about 10 e-mails here back to Joe original thread
> here to avoid the Wikipedia discussion. I've taken some of the pieces that
> Kelly added and expanded on them some in the Wiki. The #10 to be honest is
> weak, so if someone can help with one better that would help.
>
> Matt Mullins
> CloudPlatform Implementation Engineer
> Worldwide Cloud Services Citrix System, Inc.
> +1 (407) 920-1107 Office/Cell Phone
> matt.mullins@citrix.com
>
>
>
>
>
>
> On 3/5/13 9:49 AM, "Joe Brockmeier" <jz...@zonker.net> wrote:
>
>> On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
>>> Please start the draft page somewhere and I will pitch-in. We can use
>>> the
>>> same content on Wikipedia page as well.
>>
>> I've started a page here: but remember the wiki motto is "edit boldly."
>> No need to ask someone else to create page on the wiki when you can do
>> it yourself.
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources+a
>> nd+Proposals
>>
>> Also: I would be *very* careful about pushing content to Wikipedia. We
>> should absolutely keep an eye on the Wikipedia page for CloudStack and
>> keep it updated/accurate, but I think they frown on content that is
>> overly promotional. What's acceptable for the Apache CloudStack Web site
>> is not necessarily acceptable for the Wikipedia page.
>>
>>> Also it would be nice to have "what cloudstack is now" and whats going
>>> to
>>> happen soon with newer releases.
>>
>> (Fixed the Android auto-correct for you. Computers - aren't they
>> wonderful?)
>>
>> A "What's new in CloudStack" section would make sense, sure.
>>
>> Best,
>>
>> jzb
>> --
>> Joe Brockmeier
>> jzb@zonker.net
>> Twitter: @jzb
>> http://www.dissociatedpress.net/
>
Re: Elevator Pitch / Top N Features
Posted by Mathias Mullins <ma...@citrix.com>.
So I'm dropping back about 10 e-mails here back to Joe original thread
here to avoid the Wikipedia discussion. I've taken some of the pieces that
Kelly added and expanded on them some in the Wiki. The #10 to be honest is
weak, so if someone can help with one better that would help.
Matt Mullins
CloudPlatform Implementation Engineer
Worldwide Cloud Services Citrix System, Inc.
+1 (407) 920-1107 Office/Cell Phone
matt.mullins@citrix.com
On 3/5/13 9:49 AM, "Joe Brockmeier" <jz...@zonker.net> wrote:
>On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
>> Please start the draft page somewhere and I will pitch-in. We can use
>>the
>> same content on Wikipedia page as well.
>
>I've started a page here: but remember the wiki motto is "edit boldly."
>No need to ask someone else to create page on the wiki when you can do
>it yourself.
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources+a
>nd+Proposals
>
>Also: I would be *very* careful about pushing content to Wikipedia. We
>should absolutely keep an eye on the Wikipedia page for CloudStack and
>keep it updated/accurate, but I think they frown on content that is
>overly promotional. What's acceptable for the Apache CloudStack Web site
>is not necessarily acceptable for the Wikipedia page.
>
>> Also it would be nice to have "what cloudstack is now" and whats going
>>to
>> happen soon with newer releases.
>
>(Fixed the Android auto-correct for you. Computers - aren't they
>wonderful?)
>
>A "What's new in CloudStack" section would make sense, sure.
>
>Best,
>
>jzb
>--
>Joe Brockmeier
>jzb@zonker.net
>Twitter: @jzb
>http://www.dissociatedpress.net/
Re: Elevator Pitch / Top N Features
Posted by Joe Brockmeier <jz...@zonker.net>.
On Mon, Mar 4, 2013, at 08:58 PM, Musayev, Ilya wrote:
> Please start the draft page somewhere and I will pitch-in. We can use the
> same content on Wikipedia page as well.
I've started a page here: but remember the wiki motto is "edit boldly."
No need to ask someone else to create page on the wiki when you can do
it yourself.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Website+Resources+and+Proposals
Also: I would be *very* careful about pushing content to Wikipedia. We
should absolutely keep an eye on the Wikipedia page for CloudStack and
keep it updated/accurate, but I think they frown on content that is
overly promotional. What's acceptable for the Apache CloudStack Web site
is not necessarily acceptable for the Wikipedia page.
> Also it would be nice to have "what cloudstack is now" and whats going to
> happen soon with newer releases.
(Fixed the Android auto-correct for you. Computers - aren't they
wonderful?)
A "What's new in CloudStack" section would make sense, sure.
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
RE: Elevator Pitch / Top N Features
Posted by "Musayev, Ilya" <im...@webmd.net>.
Joe
Please start the draft page somewhere and I will pitch-in. We can use the same content on Wikipedia page as well.
Also it would be nice to have "what cloudstack is now" and whats going to happen soon with network releases.
Thanks
Ilya
kelcey Damage <ke...@backbonetechnology.com> wrote:
Lol, you don't want to know my opinion of the UI from an Ops perspective ( I
do think it's very pretty and shiny, and I know Sonny has been working on
alternative admin interfaces :) ).
As for the elevator pitch one big thing that comes to mind is that we have
the easiest API I have ever used. And that's a big deal.
Thanks
-----Original Message-----
From: Joe Brockmeier [mailto:jzb@zonker.net]
Sent: Monday, March 04, 2013 3:09 PM
To: cloudstack-marketing@incubator.apache.org
Subject: Elevator Pitch / Top N Features
Hey all,
One of the things I'd like to work on in the next few weeks (as we get ready
for 4.1) is to make the text on our landing page (CloudStack.org) a little
more enticing/descriptive for folks.
Specifically I'd like to tighten up the "What Is?" section and highlight
between eight and 10 features (max) on the front page.
So - what features should we highlight? What are the *most* compelling
things about Apache CloudStack. Essentially, what's our elevator pitch for
CloudStack?
For example:
- Multi-hypervisor support (Xen, VMware, KVM)
- Apache-licensed
- Elegant UI that is a reference implementation of the native API
Thoughts? Suggestions?
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
RE: Elevator Pitch / Top N Features
Posted by kelcey Damage <ke...@backbonetechnology.com>.
Lol, you don't want to know my opinion of the UI from an Ops perspective ( I
do think it's very pretty and shiny, and I know Sonny has been working on
alternative admin interfaces :) ).
As for the elevator pitch one big thing that comes to mind is that we have
the easiest API I have ever used. And that's a big deal.
Thanks
-----Original Message-----
From: Joe Brockmeier [mailto:jzb@zonker.net]
Sent: Monday, March 04, 2013 3:09 PM
To: cloudstack-marketing@incubator.apache.org
Subject: Elevator Pitch / Top N Features
Hey all,
One of the things I'd like to work on in the next few weeks (as we get ready
for 4.1) is to make the text on our landing page (CloudStack.org) a little
more enticing/descriptive for folks.
Specifically I'd like to tighten up the "What Is?" section and highlight
between eight and 10 features (max) on the front page.
So - what features should we highlight? What are the *most* compelling
things about Apache CloudStack. Essentially, what's our elevator pitch for
CloudStack?
For example:
- Multi-hypervisor support (Xen, VMware, KVM)
- Apache-licensed
- Elegant UI that is a reference implementation of the native API
Thoughts? Suggestions?
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/