Heya, Getting a bit late into the discussion here, but i agree with Chip here.
I'm already uncomfortable with the idea for a marketplace inside CloudStack, but providing just the features allow some external party (or parties) to set something up should be ok. But neither the ASF nor we as a community should maintain such a marketplace. We as a community are responsible for maintaining and distributing the CloudStack source code, initiatives like a market place seem better suited to a commercial entity or another group that is not directly related to maintaining the source code of CloudStack. Cheers, Hugo > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Thursday, December 13, 2012 9:25 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: [DISCUSS] CloudStack Marketplace Update > > On Wed, Dec 12, 2012 at 8:27 PM, Chip Childers > <chip.child...@sungard.com> wrote: > > On Wed, Dec 12, 2012 at 8:22 PM, Jie Feng <jie.f...@citrix.com> wrote: > >> Comments inline. > >> > >>> -----Original Message----- > >>> From: John Kinsella [mailto:j...@stratosec.co] > >>> Sent: Wednesday, December 12, 2012 5:12 PM > >>> To: cloudstack-dev@incubator.apache.org > >>> Subject: Re: [DISCUSS] CloudStack Marketplace Update > >>> > >>> Repeating my previous comments - if Citrix wants to host a > >>> repository of images for a CloudStack Marketplace, they can do > >>> whatever they wish. These should not be listed in the default ACS install. > >>> > >>> Please remember Apache CloudStack != Citrix. > >> > >> I am talking about an Apache listing repository. I am using Citrix as an > example. All of our committers who work with CloudStack partners can bring > in our validated partner listings. I am simply trying to leverage what we are > already doing outside of the community and bring the benefits in. > > > > -1 (binding) > > > > I am not confortable with the Apache CloudStack project making any > > assumptions about external organizations, and their various > > "certification" programs. Organizations have no standing with the > > ASF, and therefore the employer of our contributors should not affect > > their trust of some external organization for project purposes. > > > > At a bare minimum, if this marketplace idea is to move forward, we > > need to think about it in terms of code that can be used to provide > > marketplace services, but not as an "Apache" service. > > > > Do folks want to discuss how to resolve the blocker concerns here?
