Comments
Don't Give Up On OpenStack
Newest First  |  Oldest First  |  Threaded View
Susan Fogarty
50%
50%
Susan Fogarty,
User Rank: Author
12/6/2013 | 11:59:28 AM
Re: Recognizing the stakeholders
The dynamics of open source software have always seemed at odds to me. Is there any opportunity to align with a very established organization like the IEEE or the IETF to get some objective oversight? I know the IEEE is working on the "OpenStand" initiative to drive more open global standards beyond internet protocols.
Andrew Froehlich
50%
50%
Andrew Froehlich,
User Rank: Apprentice
12/5/2013 | 4:44:16 PM
Re: Recognizing the stakeholders
I couldn't agree more @geoffarnold. The balancing act between keeping both product users and developers happy is a real challenge. Dev's interested in open source don't really like guidelines and restrictions.  But if they are serious about taking OpenStack to the next level, that's exactly what's needed. 
geoffarnold
50%
50%
geoffarnold,
User Rank: Apprentice
12/5/2013 | 12:53:24 PM
Recognizing the stakeholders
I agree that we shouldn't give up on OpenStack, but let's not underestimate the magnitude of the change that's required. As I blogged recently 

OpenStack APIs (and, in some less well defined sense, the code) are intended to become a de facto standard. In the public cloud space, while Rackspace, HP, IBM and others will compete on price, support, and added-value services, they are all expected to offer services with binary API compatibility. This means that their customers, presumably numbering in the tens or hundreds of thousands, are all users of the OpenStack APIs. They have a huge stake in the governance and quality of those APIs, and will have their opinions about how they should evolve.

How are their voices heard? What role do they play in making the decisions?

Today, the answers are "they're not" and "none". Because that's not how open source projects work. As Simon Phipps wrote"...open source communities are not there to serve end users. They are there to serve the needs of the people who show up to collaborate."


The hardest thing for an open source project to establish is a way of saying "no" to contributors, whether they be individual True Believers in Open Source, or vast commercial enterprises seeking an architectural advantage over their competitors. The impulse is always to do things which increase the number of participants, and it is assumed that saying "no" will have the opposite effect. In a consensus-driven community, this is a hard issue to resolve.

 



The Agile Archive
The Agile Archive
When it comes to managing data, donít look at backup and archiving systems as burdens and cost centers. A well-designed archive can enhance data protection and restores, ease search and e-discovery efforts, and save money by intelligently moving data from expensive primary storage systems.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Elite 100 - 2014
Our InformationWeek Elite 100 issue -- our 26th ranking of technology innovators -- shines a spotlight on businesses that are succeeding because of their digital strategies. We take a close at look at the top five companies in this year's ranking and the eight winners of our Business Innovation awards, and offer 20 great ideas that you can use in your company. We also provide a ranked list of our Elite 100 innovators.
Video
Slideshows
Twitter Feed
Audio Interviews
Archived Audio Interviews
GE is a leader in combining connected devices and advanced analytics in pursuit of practical goals like less downtime, lower operating costs, and higher throughput. At GIO Power & Water, CIO Jim Fowler is part of the team exploring how to apply these techniques to some of the world's essential infrastructure, from power plants to water treatment systems. Join us, and bring your questions, as we talk about what's ahead.