Thirding sponsorship.
I didn¹t review as much as the other two, but I helped merge a couple of
the patches. Agreed with Jay otherwise; we¹re almost there, let¹s finish
it.
-Original Message-
From: Jay Pipes jaypi...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage
-Original Message-
From: Sandy Walsh sandy.wa...@rackspace.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Thursday, July 10, 2014 at 9:31 AM
To: OpenStack Development Mailing List (not for usage questions)
-Original Message-
From: Eoghan Glynn egl...@redhat.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Thursday, July 10, 2014 at 3:30 PM
To: OpenStack Development Mailing List (not for usage questions)
To add to this, the majority of my reviews come out of the period in the
morning before my team's daily standup. I've found that sufficient for
getting some reviews in, and conversely, fights off the tremendous burnout
I used to get when we had review days back in the beginning of the project.
Good idea!
Only thing I would point out is there are a fair amount of changes, especially
lately, where code is just moving from one portion of the project to another,
so there may be cases where someone ends up being authoritative over code they
don't totally understand.
From: Alessandro
I'll second the jinja2 recommendation. I also use it with Pyramid, and
find it non-obtrusive to write and easy to understand.
-Original Message-
From: Sandy Walsh sandy.wa...@rackspace.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Date: Tuesday, July