Disclaimer - Opinions my own -- I do not represent NetApp. It looks like we are picking on one marketing piece rather than looking at the big picture.
Yes -- the piece could have served the community better with references to the dev team and such. The community membership can help make that tie in happen when we promote it. I can see the community leadership position about promoting commercial interests. Those of us not in that position can be much more free and less constrained. Make no mistake -- the big picture is offering the world a viable community alternative to "pay to play" OpenStack. Commercial credibility comes from the logos and support of the companies that deploy and bet their business on the SW. Is splitting the hairs around the Citrix commercialization of SW distribution & support really in conflict with the mission of the CloudStack community & the Apache Way? Kim White NetApp 408.822.3125 Direct 925.998.4252 Mobile [email protected] -----Original Message----- From: Mark Hinkle [mailto:[email protected]] Sent: Tuesday, February 03, 2015 5:41 AM To: [email protected] Subject: Re: Latest Blog Post > On Feb 3, 2015, at 12:28 AM, Rohit Yadav <[email protected]> wrote: > > >> On 03-Feb-2015, at 10:04 am, Mark Hinkle <[email protected]> wrote: >> >> I was on the road and asked Karen to do create some tweets especially since >> this blog was partially in response to lat months’s thread about Citrix not >> supporting CloudStack. I thought we promoted any success based on CloudStack >> whether it’s a proprietary fork, storage solution or other tool. I’d be >> lying if I didn’t have an opinion but would be curious to see how many >> people agree with Rohit. If there’s a majority opinion I’d support whatever >> the group wants. It seems the phrase “Damned if we do, Damned if we don’t” >> applies. > > The blog talks about CCP and does not talk anything about ACS - the project > or its community. The blog still has a “powered by Apache CloudStack” sticker > but should we promoting anything with such stickers? I would be happy if it > still could be edited to add a link to the project and add a line or two like > all past successes (proprietary forks or tools or solutions) have done. > > Regards, > Rohit Yadav > Software Architect, ShapeBlue > M. +91 88 262 30892 | [email protected] > Blog: bhaisaab.org | Twitter: @_bhaisaab > > Find out more about ShapeBlue and our range of CloudStack related services > > IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//> > CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/> > CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> > CloudStack Software > Engineering<http://shapeblue.com/cloudstack-software-engineering/> > CloudStack Infrastructure > Support<http://shapeblue.com/cloudstack-infrastructure-support/> > CloudStack Bootcamp Training > Courses<http://shapeblue.com/cloudstack-training/> > > This email and any attachments to it may be confidential and are intended > solely for the use of the individual to whom it is addressed. Any views or > opinions expressed are solely those of the author and do not necessarily > represent those of Shape Blue Ltd or related companies. If you are not the > intended recipient of this email, you must neither take any action based upon > its contents, nor copy or show it to anyone. Please contact the sender if you > believe you have received this email in error. Shape Blue Ltd is a company > incorporated in England & Wales. ShapeBlue Services India LLP is a company > incorporated in India and is operated under license from Shape Blue Ltd. > Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is > operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company > registered by The Republic of South Africa and is traded under license from > Shape Blue Ltd. ShapeBlue is a registered trademark. It’s a corporate blog and Steve would probably edit it to appease this group but I’d never in my wildest dreams ask any other supporter of the project to edit their blogs to our editorial guidelines. Given your strong opinions and my extreme frustration with his topic and thread I’d highly recommend that it not be tweeted. Mark
