What’s New? Updated to work with the latest release of cog

Last week the OpenStack community held our summit to discuss the work we will be doing during the “Liberty” release cycle over the next six months. On Friday, several of us met to discuss how we should specify versions for the server projects. Unlike the other sessions where there are etherpads for notes, we used a whiteboard and took pictures. This post includes the picture, along with a transcription of the text.

Last week the OpenStack community held our summit to discuss the work we will be doing during the “Liberty” release cycle over the next six months. On Friday, several of us met to discuss how we manage dependencies. Unlike the other sessions where there are etherpads for notes, we used a whiteboard and took pictures. This post includes those pictures, along with transcriptions of the text. Goals We started by discussing the goals for requirements management, so we could evaluate the proposal against those needs.

What’s New? Lots of fixes for handling paths with spaces in them, contributed by Jessamyn Smith. Fix an issue with the default behavior of workon and changing directories to the project, if it is set.

What’s New? Add options to control whether to cd to the virtualenv when creating a temporary env. Add some tests.

What’s New? Touch temporary file after a name is created Support “workon .” make cd after workon optional Merged in hjwp/virtualenvwrapper (pull request #25) Stop mangling the python argument to virtualenv ignore -f lines in pip freeze output Merged in bittner/virtualenvwrapper (pull request #22) hacked attempt to get round MSYS_HOME environ dependency on windows/git-bash/msys Change “distribute” to “setuptools” in docs Merged in jessamynsmith/virtualenvwrapper (pull request #23) Override tox’s desire to install pre-releases Reworded the documentation around user scripts vs plugin creation, to make it more clear which one you need.

Over the last year, the openstack-dev mailing list has averaged 2500 messages every month. Staying on top of that much email can be challenging, especially with some of the consumer-grade email clients available today. I’ve recently upgrade my email setup to use sup, a terminal-based mail client that is helping me process the mailing list, and even keep up with gerrit at the same time. The Story Gets Worse Before It Gets Better Last summer I moved all of my email processing from Google’s GMail service to an account under my own domain hosted by FastMail.

The OpenStack community, like other open source communities, relies on IRC for a lot of our brief and interactive communication. The community is large, though, and spans the globe, so we are not all online simultaneously. Many of us also travel, meaning we are offline at times even when we are otherwise “working.” The result is lags in communication, or missed messages entirely. ZNC is an IRC “bouncer”, a tool for maintaining a presence on an Internet Relay Chat network even when you yourself are not connected to the Internet.

As mentioned previously, I have been using ansible for managing my development configuration for a few months now, and I’m finally getting around to releasing some of the roles I’ve created in a form (possibly) useful to other folks. This one configures some of the packages needed to run unit tests for OpenStack projects. Features There’s nothing quite as annoying as having tox fail to build a test environment because some system package is missing.

I have been using ansible for managing my development configuration for a few months now, and I’m finally getting around to releasing two of the roles I’ve created in a form (possibly) useful to other folks. Why Ansible? Ansible is an tool for automating system tasks like deploying packages and configuring servers. In my case, I use it to set up cloud servers and vagrant VMs with the packages and tools I need to be productive at work.