Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED3D7E1F1 for ; Mon, 11 Feb 2013 23:03:35 +0000 (UTC) Received: (qmail 36355 invoked by uid 500); 11 Feb 2013 23:03:34 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 36301 invoked by uid 500); 11 Feb 2013 23:03:34 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 36282 invoked by uid 99); 11 Feb 2013 23:03:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 23:03:34 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of imusayev@webmd.net designates 213.199.154.141 as permitted sender) Received: from [213.199.154.141] (HELO db3outboundpool.messaging.microsoft.com) (213.199.154.141) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 23:03:30 +0000 Received: from mail2-db3-R.bigfish.com (10.3.81.237) by DB3EHSOBE007.bigfish.com (10.3.84.27) with Microsoft SMTP Server id 14.1.225.23; Mon, 11 Feb 2013 23:03:08 +0000 Received: from mail2-db3 (localhost [127.0.0.1]) by mail2-db3-R.bigfish.com (Postfix) with ESMTP id 8D92A44023D; Mon, 11 Feb 2013 23:03:08 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.138.251.40;KIP:(null);UIP:(null);IPV:NLI;H:exht02l-crp-03.webmdhealth.net;RD:none;EFVD:NLI X-SpamScore: 22 X-BigFish: VPS22(z3f29ii4582m407bk551biz98dI9371I542I1432Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahz8dhz8275ch177df4h17326ah8275dh1954cbhc704dh8275bhz31h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h1155h) Received-SPF: softfail (mail2-db3: transitioning domain of webmd.net does not designate 207.138.251.40 as permitted sender) client-ip=207.138.251.40; envelope-from=imusayev@webmd.net; helo=exht02l-crp-03.webmdhealth.net ;mdhealth.net ; Received: from mail2-db3 (localhost.localdomain [127.0.0.1]) by mail2-db3 (MessageSwitch) id 136062374298862_7237; Mon, 11 Feb 2013 23:02:22 +0000 (UTC) Received: from DB3EHSMHS012.bigfish.com (unknown [10.3.81.253]) by mail2-db3.bigfish.com (Postfix) with ESMTP id 1D4F52C0079; Mon, 11 Feb 2013 23:02:09 +0000 (UTC) Received: from exht02l-crp-03.webmdhealth.net (207.138.251.40) by DB3EHSMHS012.bigfish.com (10.3.87.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 11 Feb 2013 23:02:06 +0000 Received: from EXMBX01L-CRP-03.webmdhealth.net ([fe80::5dee:f0f2:86fe:c40f]) by exht02l-crp-03.webmdhealth.net ([::1]) with mapi id 14.02.0318.004; Mon, 11 Feb 2013 18:02:04 -0500 From: "Musayev, Ilya" To: Sebastien Goasguen CC: "cloudstack-dev@incubator.apache.org" , "cloudstack-users@incubator.apache.org" Subject: RE: ACS - Better Marketing - YOUR HELP IS NEEDED Thread-Topic: ACS - Better Marketing - YOUR HELP IS NEEDED Thread-Index: Ac4FemP6hCiHNQcFQzSbWU7EALVHqwA6D5UAAJIrEYA= Date: Mon, 11 Feb 2013 23:02:03 +0000 Message-ID: References: <220FAE37-6238-4DA9-8155-A4820E060CEF@gmail.com> In-Reply-To: <220FAE37-6238-4DA9-8155-A4820E060CEF@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.46.42.145] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: webmd.net X-Virus-Checked: Checked by ClamAV on apache.org Sebastien, Agreed with all your comments, joining the cloudstack-marketing list now. BTW, I could mention that we are cloudstack user - and I did updated the pa= ge of "Who is using CloudStack", I just cant put the company logo - due to = legal reasons. In my world, anything that has to go through legal is like throwing a reque= st into a deep hole - and pray that at somepoint the request comes back and= when it does. Regards ilya=20 -----Original Message----- From: Sebastien Goasguen [mailto:runseb@gmail.com]=20 Sent: Friday, February 08, 2013 3:13 PM To: Musayev, Ilya Cc: cloudstack-dev@incubator.apache.org; cloudstack-users@incubator.apache.= org Subject: Re: ACS - Better Marketing - YOUR HELP IS NEEDED On Feb 7, 2013, at 11:47 PM, "Musayev, Ilya" wrote: > To be completely honest, CloudStack is an awesome product, with one major= flow - it's a "best kept secret" not too many know about. The last thing w= e want to see is for CS to become like BSD (awesome and stable) but barely = used. >=20 > I'm not Citrix employee, I will speak freely - so pardon my honesty. >=20 > We lose the market to a peer pressure phenomenon known as OpenStack, I'm = not saying OS is bad by any means, but realistically, many companies go for= OS - because thats what everyone talks about, they don't use the approach = of what is right for my environment, instead they go for the buzzword. Not = many can actually get OS to work - in true open source way - and end up pay= ing for various companies to make it work for them and maintain as well. We= need to get the word out there for CS - we can do better. >=20 > For the most part, (my strong opinion based on where I worked in past) I = can say that in most use cases for small, mid and large size companies, CS = is a better fit. >=20 > Bad marketing, works against everyone's interest. Anything from future jo= b opportunity - to actually working with a product that is simply great, st= able and feature rich. >=20 > Here is how I propose we fix this: >=20 > For each of the bullet points below - we assign leads that work with cont= ributors. >=20 >=20 > 1) Create an ACS social media marketing team - We NEED social media = attention >=20 > a. Gather list of ideas >=20 > b. Meet regularly on IRC to follow up on progress and discuss what c= an be done better >=20 > c. Pick the best voted ideas >=20 > d. Assign the duties and roles >=20 > e. Conquer - one at a time >=20 > f. Create Facebook, LinkedIn, Twitter and YouTube Channels or use = existing means and other social media >=20 This is great, I just want to point out that we have talked about a few of = these items already: They already exist (from prior Apache move) and we talked about it: http://markmail.org/thread/p3awdls6khvvtyzk All videos from CCC have been posted at: http://www.youtube.com/diycloudcomputing > g. Blog with SEO in mind >=20 >=20 >=20 > 2) Show the world how you can get ACS to work in your environment on= youtube and other video sites >=20 > a. Create a set of step by step tutorial (video preferred) >=20 > i. Bas= ic ACS POC setup >=20 > ii. Sett= ing up ACS in corporate environment with strict compliance >=20 > iii. Host= ing environment >=20 > iv. Develo= pment Environment - educate new developers on how to troubleshoot issues an= d how to address them - actual basic examples would be really good on how b= ug X was fixed >=20 >=20 I have asked for screencast/demo at: http://markmail.org/thread/j4dv4wt2xkhqv73v >=20 > b. Take it a step further and show how you can bolt on CS with other= offerings - again video preferred but text will do >=20 > i. Sho= w how to bolt on OpenSwift for block storage, OpenShift (linux PaaS) and Ir= onFoundry (windows PaaS), Chef and SpaceWalk and others >=20 >=20 >=20 > 3) Create support groups based on area of expertise, for example I c= an help with VmWare and CS setups, but I'm not good with XEN or KVM at the = moment >=20 > a. We need support groups for different hypervisors, storage and ne= tworks that can help newcomers >=20 > b. Each issue resolved must be documented preferable on wiki - any = documentation (including copy and paste from mailing list) is better than = none >=20 >=20 >=20 >=20 > 4) Host local user group meet ups Personnally, I attend and speak at JUG in France/Geneva region. I was just = at the Grenoble JUG last week and I am heading to Edinburgh JUG in March 27= . >=20 > a. Show CS and help others >=20 >=20 This is what we try to do with buildacloud.org (former cloudstack.org): http://buildacloud.org/blog/202-bacd-ghent-summary-and-slides.html My question to all the CloudStack users reading this is how can we get all = of you to speak out about your deployments. Write a blog describing your use case, how you use CloudStack and why you l= ove it ? Not to pick on you Ilya, but If I google for "cloudstack webmd" it only ret= urns links to the mailing list. So what prevents you from writing about how= you use CloudStack ? What can we do as a community to get you to write abo= ut CloudStack ? >=20 > 5) Reach out to other open source (and not) players and work with th= em to have easy integration and cross functionality >=20 > a. RedHat with OpenShift PaaS As an example, see my podcast with redhat during FOSDEM where I reach out t= o delta cloud: http://cloudevangelist.org >=20 > b. IronFondry >=20 > c. Cisco, Microsoft, VMWare, etc... >=20 > d. Become part of major distributions There was also a thread on this: http://markmail.org/thread/3nm2g7elvoxek7ga >=20 > e. Others will join as soon as they see the momentum >=20 >=20 Momentum is building, at least in France it's picking up nicely: http://ies.ikoula.com/cloud-prive >=20 > * Next Steps to make this happen: >=20 > o Gather list of people willing to contribute their time with skills an= d desired areas of involvement, even if you are a new comer or don't have e= nough experience with CS, we can use your help! >=20 > o Set the time for regular IRC meeting >=20 > o Help lead this effort as well as participate >=20 >=20 > Together we can make ACS better for everyone and we can beat the buzzword= players - because we are truly better. >=20 > Your input is welcome, if you want to reach out to me off the list, pleas= e feel free, I'm on irc.freenode.net nick "serverchief", or email me direct= ly. >=20 > Thanks > ilya The bottom line to me is very simple: We need everyone on this list to write a blog about how they use cloudstack= or develop on cloudstack: http://sebgoa.blogspot.com Then we need to tweet the hell out of it :) Easy :)