Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of robyn.bergeron@gmail.com
 designates 74.125.83.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20121204193709.GA22499@cloud.com>
References: 
 <CANFAPZGLJjy+wu_U6EyC+AKkvLrsQ+QJuoerjTQ9v6=jFMrLRg@mail.gmail.com>
	<20121204193709.GA22499@cloud.com>
Date: Fri, 7 Dec 2012 02:02:00 -0700
Message-ID: 
 <CANFAPZGn+wYYZZXy6x8ybdFpRTM5_2bwxNUO_ewg9OqUL8FwDA@mail.gmail.com>
Subject: Re: Marketing and a "who uses it" list
From: Robyn Bergeron <robyn.bergeron@gmail.com>
To: "cloudstack-dev@incubator.apache.org"
 <cloudstack-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=047d7b622676f14e6b04d03f774e

--047d7b622676f14e6b04d03f774e
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Dec 4, 2012 at 12:37 PM, Prasanna Santhanam <
prasanna.santhanam@citrix.com> wrote:

> On Tue, Dec 04, 2012 at 01:11:51PM +0530, Robyn Bergeron wrote:
> > Greetings.
> >
> > A quick bit of background, esp. as I'm effectively a "long time reader,
> > first time poster" - I attended the collaboration conference over the
> past
> > weekend, became involved in a discussion about ways to market an open
> > source project, and subsequently volunteered myself to suggest/create a
> > page that folks could contribute to that is essentially a "list of
> > organizations using Apache Cloudstack."  I am assuming the dev list is
> the
> > optimal place for this discussion.
>
> Welcome Robyn!
>
> >
> > In my mind, there are a few benefits to providing this information:
> > * Potential users coming to the project page can see concrete examples of
> > real-world usage, which inspires confidence
>
> Yes - I do this for all projects to see the who's who (involved) and
> who's using the software and at what scale. That just adds to
> credibility and the glamour ;) no doubt!
>
> > * Potential developers coming to the project page can see that their
> > contributions would be well-used and loved. :)
>
> +1
>
>
> > * Press folks seeking information about project usage can see a list of
> > deployments, confirming their suspicions of awesomeness.
>
> And with user stories decide on their own deployments and usage.
> CloudStack is used by a wide array of folks.
>
> >
> > It then occurred to me that it would be useful more generally to have a
> > basic Marketing wiki page. So I was bold and made a quick one, and you
> can
> > see it, and go crazy and edit it as well:
> >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marketing
> >
>
> >     ** What to do if someone's organization is listed and someone gets
> > unhappy about that listing.  Thoughts?
> I would think it best to accept that someone uses cloudstack if they
> have listed the usage in a blog/their company page. Or if they've
> brought its use to our wiki/lists themselves
>
> >  Assuming I haven't totally done said toe-stepping, I figure a useful
> next
> > step would be to mail the users list and see if anyone on that list is
> > willing to add their name to such a list. (Side bonus: Some of them may
> be
> > adding stuff to the wiki for a first-time mini-contribution!)
>
> Yes please take this to the users lists as well.
>

Okay, it would appear that there is enough consensus to move ahead to the
users list - or at least, nobody saying this is a terrible idea :) That
said - it would be great to have a first example that someone else has
populated.

I took the liberty of breaking out the "list" page into a separate child
page under Marketing - mostly to remove any barriers for people wanting to
add their name (no longer have to scroll down the marketing page).

https://cwiki.apache.org/confluence/x/nh7VAQ

If anyone on *THIS* list would like to help kick the users/organizations
list off right - that would be awesome. But I'll hit up the users list as
well now.

Cheers,

-Robyn


>
>
> And thanks for being bold and stepping up to do this.
>
>
> --
> Prasanna.,
>

--047d7b622676f14e6b04d03f774e--