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 ECA93E422 for ; Fri, 8 Feb 2013 16:14:24 +0000 (UTC) Received: (qmail 90687 invoked by uid 500); 8 Feb 2013 16:14:24 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 90649 invoked by uid 500); 8 Feb 2013 16:14:24 -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 90640 invoked by uid 99); 8 Feb 2013 16:14:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2013 16:14:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.128.176] (HELO mail-ve0-f176.google.com) (209.85.128.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2013 16:14:17 +0000 Received: by mail-ve0-f176.google.com with SMTP id cz10so3423113veb.21 for ; Fri, 08 Feb 2013 08:13:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:content-transfer-encoding :x-gm-message-state; bh=+T7nUHDq/mHCOb7CS+16qwBeU9CyHR1OWLTxvwozEwY=; b=UjiPuhc97Rh4lWGghzoYLVRe83cxh8jUEphYP8pxGhutsdETKN9Jc1+X7ia4ae6ZCM NABV4aEhLCFrAZTpRlbLPNCHXyHExirq1bWmhpMdWk9EQjLCFz+rYu793rEW5zS5TUMN KVWPmSsL4/DOmoTGeAq+F98ehAG9WPY102UEV79uogyR9XpXHX2WFeVI3BxVKUSSX46d KcVc+lIOyd/ZxMUxscCPx9Rp1aiBCs+moYzGl0EfNRBZUNT9+Q/+tcjq7dwr0MjbAdUN v9r/9dwK5cbGuK7RBMv573pK8Aw5L0MtuLBx/A5RS3maQTTJNRxgaZW0IOXp86keEXXl 0bBw== X-Received: by 10.58.205.179 with SMTP id lh19mr7409411vec.7.1360340026757; Fri, 08 Feb 2013 08:13:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.184.72 with HTTP; Fri, 8 Feb 2013 08:13:26 -0800 (PST) In-Reply-To: References: From: David Nalley Date: Fri, 8 Feb 2013 11:13:26 -0500 Message-ID: Subject: Re: ACS - Better Marketing - YOUR HELP IS NEEDED To: cloudstack-dev@incubator.apache.org, cloudstack-users@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlvwDylHvef3oIwDhQftYWLabu8vB+bA3/gqM2LUqg1BbBLXVOOO/OH7h8AtkTDePJ2C7pI X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Feb 7, 2013 at 5: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. > > I'm not Citrix employee, I will speak freely - so pardon my honesty. > > 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. > > 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. > > 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. > > Here is how I propose we fix this: > > For each of the bullet points below - we assign leads that work with cont= ributors. > > > 1) Create an ACS social media marketing team - We NEED social media = attention > > a. Gather list of ideas > > b. Meet regularly on IRC to follow up on progress and discuss what c= an be done better > > c. Pick the best voted ideas > > d. Assign the duties and roles > > e. Conquer - one at a time > > f. Create Facebook, LinkedIn, Twitter and YouTube Channels or use = existing means and other social media > > g. Blog with SEO in mind > > > > 2) Show the world how you can get ACS to work in your environment on= youtube and other video sites > > a. Create a set of step by step tutorial (video preferred) > > i. Ba= sic ACS POC setup > > ii. Set= ting up ACS in corporate environment with strict compliance > > iii. Hos= ting environment > > iv. Devel= opment Environment - educate new developers on how to troubleshoot issues a= nd how to address them - actual basic examples would be really good on how = bug X was fixed > > > > b. Take it a step further and show how you can bolt on CS with other= offerings - again video preferred but text will do > > i. Sh= ow how to bolt on OpenSwift for block storage, OpenShift (linux PaaS) and I= ronFoundry (windows PaaS), Chef and SpaceWalk and others > > > > 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 > > a. We need support groups for different hypervisors, storage and ne= tworks that can help newcomers > > b. Each issue resolved must be documented preferable on wiki - any = documentation (including copy and paste from mailing list) is better than = none > > > > > 4) Host local user group meetups > > a. Show CS and help others > > > > 5) Reach out to other open source (and not) players and work with th= em to have easy integration and cross functionality > > a. RedHat with OpenShift PaaS > > b. IronFondry > > c. Cisco, Microsoft, VMWare, etc... > > d. Become part of major distributions > > e. Others will join as soon as they see the momentum > > > > * Next Steps to make this happen: > > 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! > > o Set the time for regular IRC meeting > > o Help lead this effort as well as participate > > > Together we can make ACS better for everyone and we can beat the buzzword= players - because we are truly better. > > 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. > > Thanks > ilya This is indeed great initiative, and I am happy to join in and help. Let us know when the first meeting will be and lets start tackling some of this stuff. --David