On 04/24/2015 06:28 PM, David Medberry wrote: > On Fri, Apr 24, 2015 at 2:14 AM, Chris Dent <chd...@redhat.com> wrote: > >> >> What can and should the TC at large, and you specifically, do to ensure >> quality improves for the developers, end-users and operators of >> OpenStack as a full system, both as a project being developed and a >> product being used? > > > Hello Chris et al, > > OpenStack quality will improve for the operators with a strong operator > voice that helps focus developers and the overall technical focus on usage. > OpenStack quality improves for developers in other ways: by hearing from > end users and operators they can in part anticipate (or respond more > quickly) to issues that will otherwise become truly raging hotspots (crises > if you will.) > > The other way to directly improve quality for OpenStack Devs is to improve > test coverage and gate checks on more "production-like" systems. As an > operator and advocate, I can persuade or motivate other operators to offer > up resources (people as well as systems) to aid in this area of improvement. > > These are indeed new times with operators playing a very critical role in > OpenStack.
As a follow up to this thought - we _may_ be in a place over the next cycle where Infra would be in a position to accept systems from operators or others. Up until now we've only been in a position really to deal with public clouds - but we're taking a stab at something new and if it works out, it should open the door to taking advantage of offers like this - which I agree will be a good thing for the project. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
