Open source Content Management Systems (CMS) like WordPress, Drupal and Joomla! have now been around for a decade or so, doing their part to make the internet a more manageable place. At its core, a CMS structures the experience of developing, managing and consuming a website. Chances are good that a big chunk of the content you’ll read on the web today (including this post) is being delivered through an open source CMS. FedEx and The Washington Post are using Drupal. Coca-Cola France and Sony Music are using WordPress. Harvard and IHOP use Joomla!
Last week, the Federal Circuit overturned the District Court judgment in Oracle v. Google, finding that the Java API is copyrightable. This move overturns the expectations of businesses and developers and is likely to negatively impact how they leverage APIs going forward. We have been thinking a lot about the ruling since it came down, putting together our thoughts.
After less than six months in development, Project Solum has accomplished the first development milestone (Milestone 1). This important event allows deployment of code from Github via Heat to generate a running app deployed to Docker containers using a generalized (Heroku) build pack for the app stack.
In the last few years we have seen new distributions emerge, like MariaDB and Percona Server, as viable alternatives to MySQL. These new distributions create more choice for users with increased focus on performance and offer new configurations that empower users to push the limits of their database and optimize in new ways.
Getting an application designed, tested and running, then updating and improving it is no easy task — even in the best of times. There is a continuing quest for tooling that delivers automation of this work to allow more focus on what matters most: fast, efficient development. This automation is increasingly sought via a platform service layer that abstracts the compute, networking and storage details of the infrastructure service layer — offering simplification for application developers and the cloud operators who support them.
Austin-based writer and artist Austin Kleon kicked off SXSW Interactive with his panel called “Show Your Work,” based on his latest book by the same title. Kleon argued that showcasing the creative process holds as much benefit for the creator as the end result. By showing your work, you are not operating in isolation, but becoming part of a scene. This community is where ideas are exchanged and valuable networks are made.
When we started OpenStack, the goal was to form a community of like-minded companies and contributors to push for an open alternative to proprietary cloud software. We saw open source as a platform to foster swift innovation and to give customers more choice.
It feels like yesterday that Frank Frankovsky, vice president of Hardware Design at Facebook and chairman of the Open Compute Project (OCP), sent me a Facebook message – how fitting – about a budding open hardware project that he was working on. At Rackspace, we immediately jumped at the chance to be among the first companies to join the community, as we believed Open Compute was poised to flip the hardware model much like we did with cloud software when we founded OpenStack.
One of the things that we value at Rackspace is being “open,” which means that we prioritize sharing and collaborating over self-focused work. Being open creates value by aligning us with those whom we serve. It brings us all into closer and more productive partnership with each other, and enables us to deliver the Fanatical Support that is our trademark.