>From: Kyle Mestery ><mest...@noironetworks.com<mailto:mest...@noironetworks.com>> >Reply-To: "OpenStack Development Mailing List (not for usage questions)" ><openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> >Date: Friday, March 21, 2014 2:49 PM >To: "OpenStack Development Mailing List (not for usage questions)" ><openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> >Subject: Re: [openstack-dev] [Nova] Updates to Juno blueprint review process
>This is the part I'm keenly interested in Russell. Once you have some feedback >on things here, >this model of using gerrit for review is something I'd like to see other >projects use going forward >as well. For what it's worth, as a person who's 99% on the operator side, I used the proposed template as my first foray into: * Getting things set up with Geritt * Submitting a change for review * Getting myself set up to be aware of the nova-specs project for future Blueprint reviews All in all, aside from me getting my head wrapped around the commit message guidelines, it went pretty smooth. I've also gained a lot of insight off the blueprints already submitted (though to Russell's credit, they are trying to push back a little for a few days until the template is good and baked) I think the overall model has a lot of promise. I'm just waiting on word form Russell and company to say a lot more on the operator's list. From my experience, however, it's a great way to lower the barrier to entry for "operators" and the like in the the "code" side of OpenStack – one of the key outputs from the mini summit! Thanks again, for pushing this along! Let me know when you are ready for a bigger deal to be made outside the dev lists. Thanks! Matt
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
