Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: unknown mxinclude:zoho.com~all (athena.apache.org: encountered
 unrecognized mechanism during SPF processing of domain of jlk@stratosec.co)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [DISCUSS] CloudStack Marketplace Update
From: John Kinsella <jlk@stratosec.co>
In-Reply-To: 
 <7A92FF96DF135843B4B608FB576BFC3E012DA2CF1BED@SJCPMAILBOX01.citrite.net>
Date: Wed, 19 Dec 2012 11:07:19 -0800
CC: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <E791D901-A8DC-4644-BD6F-2481C93D890A@stratosec.co>
References: 
 <CA+96GG5WtrxkyEsBCN4=_iztU8ZA9opLJPYsxgbDw1zrUFbOEQ@mail.gmail.com>
 <4F8072AF-F588-492D-BA38-093460F660AF@gmail.com>
 <7A92FF96DF135843B4B608FB576BFC3E012DA27F449A@SJCPMAILBOX01.citrite.net>
 <CAKprHVb5cXzcuq2_6MiM0YJfdvWLFWu=EeCh5Uu-9MXYUY_O-g@mail.gmail.com>
 <7A92FF96DF135843B4B608FB576BFC3E012DA27F44DC@SJCPMAILBOX01.citrite.net>
 <0889AA2F-F5DF-4633-88DB-9FD4A8ACB961@stratosec.co>
 <7A92FF96DF135843B4B608FB576BFC3E012DA27F44E3@SJCPMAILBOX01.citrite.net>
 <CA+96GG769HRA5bSPE775=GsM282Rt4bPkHTbnYDPxgNrA+PDbQ@mail.gmail.com>
 <CA+96GG68XgaxQ+KBwNHsveGtuCnMp-aqUyo4Za8QgQ9j0KZojQ@mail.gmail.com>
 <6DE00C9FDF08A34683DF71786C70EBF02F50E5CB@SBPOMB402.sbp.lan>
 <20121213215636.GC18515@localhost.localdomain>
 <15D29345-CF54-4A22-8C8A-F07F90FAF901@gmail.com>
 <7A92FF96DF135843B4B608FB576BFC3E012DA2CF1BED@SJCPMAILBOX01.citrite.net>
To: <cloudstack-users@incubator.apache.org>

On Dec 19, 2012, at 10:10 AM, Jie Feng <Jie.Feng@citrix.com> wrote:
> 4. Disable Marketplace by default or not including any listing =
repository by default.
> The community in general seems to be concerned about including a third =
party listing repository by default. My question is if third parties do =
run a listing repository, how do we make CloudStack admins and users =
aware of this? And in general, how do we help folks who build =
value-added offerings on top of CloudStack to reach the admins and users =
of the CloudStack community? In my opinion, for an open source project =
to be successful, an ecosystem is very important. My original goal is to =
design the Marketplace in such a way that the listings are very easily =
accessible by admins and users, and have place for the ecosystem to =
participate (think iPhone and iPhone apps).=20

This is an interesting concern - my response would be to ask "How do =
vendors in the Eclipse community get potential customers to know about =
their 3rd party repositories?" It seems to happen just fine. =46rom a =
business perspective, you don't advertise your repo, you advertise your =
awesome functionality that people will want, then when they ask how to =
get it, the repo is mentioned.

So the goal of this ACS marketplace integration should be to make it as =
easy as possible for a CloudStack user to either add a repo into their =
ACS install, or to visit a marketplace and then get the resulting =
acquisition (funds may be transferred or no) into their ACS install. If =
it's easy (within Apache limits), it'll get used.