Rackspace spins up OpenStack Foundation
Will hand over trademarks and copyrights to independent group
Exclusive Rackspace is letting go of key components of the OpenStack Linux-for-the-cloud initiative it is helping to lead, with the creation of an OpenStack Foundation, The Reg has learned.
The company has told a small number of OpenStackers, via a confidential email seen by The Reg, that it is in the process of creating the OpenStack Foundation and will hand over the OpenStack trademarks and copyrights to the group. The OpenStack Foundation will go live in 2012.
Trademarks and copyrights for the Apache-licensed OpenStack project are currently owned, administered and enforced by OpenStack LLC, a subsidiary of Rackspace.
The email by Jonathan Bryce, chief technology officer and founder of Rackspace's cloud subsidiary Mosso – and OpenStack project policy board chairman – did not give a reason why the company is apparently relinquishing control of these assets.
But speaking to The Reg, Bryce said Rackspace felt the time is right to create a permanent, vendor-neutral and independent home for OpenStack.
The existing OpenStack project policy board, the process of electing individuals to that board, and the project lead structure will remain in place and won't be changed with the new Foundation.
Rackspace will take feedback on what the community wants, but Bryce said Rackspace doesn't want change for the sake of change.
He said the Foundation is significant, though, because the trademarks are the only big piece of IP that exist around OpenStack because the code lives under an Apache licence.
Rackspace president for cloud and chief strategy officer Lew Moorman, who unveiled the OpenStack project at OSCON in 2010, will announce the OpenStack Foundation at the OpenStack design summit and conference underway in Boston, Massachusetts, on Thursday.
The hosting firm will use the conference to take feedback on the Foundation's structure starting with an hour-long governance session on Thursday afternoon.
Who controls the trademarks and copyrights of open-source projects is a sensitive subject. It speaks volumes about who is in charge, whether a project can actually be considered free and in the hands of individual members.
Oracle refused to relinquish control over the trademark and copyrights of the OpenOffice project last year – leading to a fork and the creation of the independent LibreOffice. The database giant also sought similar control over the Hudson build management system in a clumsy land grab that saw almost all Hudson contributors walk out and set up the rival Jenkins project.
Rackspace has taken considerable flack for exerting too much control over the management structure of the project running OpenStack; it will be willing to avoid stumbling down the same path as Oracle on a project it has staked so much on.
The OpenStack Foundation comes as Red Hat has spun up the Aeolus cloud project and positioned it as OpenStack "done right": Aeolus is a management tool being built to work with different clouds, rather than providing yet another cloud option as OpenStack is doing. Also: Red Hat's goal is to attract code contributions from across a broad community, rather than a few very active participants – as has happened at OpenStack.
Red Hat was invited by Rackspace to join OpenStack in the project's early days but the Linux outfit turned it down because the governance model didn't allow for contributions that would have suited its customers, and that the project was controlled too tightly by one vendor: Rackspace.
Bryce denied that the creation of the Foundation is a response to Red Hat, saying it had been part of the project's original objective.
Mark Collier, Rackspace vice president of marketing and business development, said that while Rackspace was seen to be doing the right thing among OpenStackers with regard to the project, control of the trademark was a concern.
"It is a concern that people have raised based on the behavior of other companies," he said. "Just the potential for abuse would make people nervous. We felt this was not something that was unsolvable – it could be solved through a Foundation."
While Rackspace is apparently attempting to loosen things up, it has emailed a select number of people about the Foundation's genesis, and there's therefore a risk that people will accuse the company of once again determining what's right for OpenStack.
Bryce emailed the 13 individuals on the OpenStack Project Policy Board. These include Rackspacers developing the OpenStack code for his company; OpenStack project leads of Swift, Nova compute and Glance; plus OpenStack leaders at Hewlett-Packard and Citrix Systems and two OpenStack start-ups.
In his email, Bryce had asked recipients to keep news of the Foundation quiet until Moorman's announcement on Thursday so as not to distract, he said, from discussions at the event over features in next version of OpenStack – codenamed Essex and expected in the second quarter of 2012.
Bryce had said in his email: "We have quite a few ideas about structure and operation, but mainly we want to announce the intention and then flesh out the plans and implementation together with the rest of the community."
Ongoing discussion is planned to take place after the Essex summit and conference. ®
This article has been update to clarify the recipients of Bryce's email were members of the OpenStack Project Policy Board.
Sponsored: 2016 Cyberthreat defense report