Musings on the Austin Summit

This is going to be a bit of a different summit recap than my previous ones. Since Steve Hardy has already posted an excellent summary of the major TripleO topics from this summit, I'm not going to duplicate all of that here.

Instead, this will be a more personally focused post, wherein I reflect on my experience at this summit and how it compared to previous ones. If that kind of navel-gazing sounds incredibly uninteresting, then you might want to pull the rip cord now. :-)

Vancouver Summit - The Moose is Loose

Third time's a charm, right?

Well, yes and no. Overall I would call the summit a success, and a lot of good things came out of it. It wasn't all sunshine and puppies though, and there are definitely some things I personally, and we as a community, could improve. Which means I should have lots of interesting things to talk about in this post. Let's get right to it.

The Whys and Hows of the Oslo Namespace Change

Edit Jan. 26, 2015: After discussing this with the Oslo team some more, I discovered that almost everything I said here was already covered quite well in the drop namespaces spec (that I reviewed... ;-). You're probably just as well off going and reading that, but I'm going to leave this here just in case it happens to help get the word out.

The Why

During the Kilo cycle the Oslo team has been busy deprecating the oslo. namespace in all of our projects. The first question this probably raises for most people is: why? Unfortunately the answer to that is not simple, and I'm not sure I understand some of the deeper details of it myself. However, after having talked to some of the Python packaging folks that hang around the OpenStack project we came to the conclusion that namespace packages in Python 2 are just too broken for us to continue using them.

Subscribe to RSS - Oslo