OpenStack Folsom Design Summit

This is a brainstorming session to determine what we can or should do during the Folsom release cycle to prepare for Python 3 in a G or later release. After PyCon 2012, it's clear than Python 3 is here, and we need to starting thinking about it. It's also clear this isn't happening in Folsom. This is a big effort, and we should probably start planning sooner rather than later. Initial topics for discussion are: - Tracking our package dependencies and their Python 3 status - Will all projects move to Python 3 simultaneously ? - How do we handle incubated projects and contributed modules ? - Do we even consider supporting 2.x and 3.x simultaneously ? - Impacts on continuous integration - Impacts on downstream packages and distros - What code guidelines can we put in place for Folsom to help the transition ? The objective of this session to produce a short list of specific actions we an take in the Folsom timeframe to make the inveitable transition easier. (Session lead is Mike Pittaro)