On Mon, Mar 31, 2014 at 10:40 PM, Adam Young <ayo...@redhat.com> wrote:
> On 03/28/2014 03:01 AM, Tom Fifield wrote: > >> Thanks to those projects that responded. I've proposed sessions in swift, >> ceilometer, tripleO and horizon. >> > > > Keystone would also be interested in user feedback, of course. Crossing openstack-dev threads [1] here, gathering feedback on proposed deprecations would be a great topic for such a session. [1] http://lists.openstack.org/pipermail/openstack-dev/2014-April/031652.html > > >> On 17/03/14 07:54, Tom Fifield wrote: >> >>> All, >>> >>> Many times we've heard a desire for more feedback and interaction from >>> users. However, their attendance at design summit sessions is met with >>> varied success. >>> >>> However, last summit, by happy accident, a swift session turned into a >>> something a lot more user driven. A competent user was able to describe >>> their use case, and the developers were able to stage a number of >>> question to them. In this way, some of the assumptions about the way >>> certain things were implemented, and the various priorities of future >>> plans became clearer. It worked really well ... perhaps this is >>> something we'd like to have happen for all the projects? >>> >>> *Idea*: Add an "ops" session for each project in the design summit >>> https://etherpad.openstack.org/p/ATL-ops-dedicated- >>> design-summit-sessions >>> >>> >>> Most operators running OpenStack tend to treat it more holistically than >>> those coding it. They are aware of, but don't necessarily think or work >>> in terms of project breakdowns. To this end, I'd imagine the such >>> sessions would: >>> >>> * have a primary purpose for developers to ask the operators to answer >>> questions, and request information >>> >>> * allow operators to tell the developers things (give feedback) as a >>> secondary purpose that could potentially be covered better in a >>> cross-project session >>> >>> * need good moderation, for example to push operator-to-operator >>> discussion into forums with more time available (eg >>> https://etherpad.openstack.org/p/ATL-ops-unconference-RFC ) >>> >>> * be reinforced by having volunteer "good" users in potentially every >>> design summit session >>> (https://etherpad.openstack.org/p/ATL-ops-in-design-sessions ) >>> >>> >>> Anyway, just a strawman - please jump on the etherpad >>> (https://etherpad.openstack.org/p/ATL-ops-dedicated- >>> design-summit-sessions) >>> or leave your replies here! >>> >>> >>> Regards, >>> >>> >>> Tom >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev