Everett Toews

A common complaint about many open source projects is documentation. Insufficient, incorrect, non-existent, hard to find, and difficult to update are things we typically all hear. There are a lot of different ways to tackle these problems. There’s no silver bullet but one of my favourite tactics is lowering the barriers for absolutely anyone to walk up and contribute documentation.

Like many other developers, I’ve decided to abandon WordPress and use GitHub’s Jekyll as a Service for my blogging platform. Most developers focus on the how when they write their “I’ve switched to Jekyll” post. I’m thankful to all of those developers because their work has made my transition easier. However, I’m going to focus on the why for this post.

Here’s how to deploy DevStack for OpenStack Icehouse on the Rackspace Cloud. You can use DevStack for testing/development of OpenStack or just learning a bit more about OpenStack and how all of the pieces fit together.

Simply put, SXSW 2014 was awesome. This year I had a workshop titled Cloud Portability with Multi-Cloud Toolkits accepted. With that came a Gold badge and full access to SXSW Interactive. It’s a pass to insight into the tech industry and I tried to make full use of it.

I was setting up a laptop to contribute some code to OpenStack according to the Gerrit Workflow Account Setup. When I got to the point of doing the git review -s I hit the error

TL;DR Developers need zero ambiguity from API documentation.