[Openstack] Bringing focus to the Operators and Users at the next summit

Sean Dague sean at dague.net
Thu Dec 19 11:53:21 UTC 2013


On 12/17/2013 04:40 AM, Thierry Carrez wrote:
> Tim Bell wrote:
>> I would also propose that these user/operator points should be provided to the PTLs at least one month in advance of the summit. Armed with this input, the PTLs can factor this into the summit session planning. If there are needs for a user/operator advocate in design sessions, I think we can find candidates as we expand through the volunteers and ambassador programs.
> 
> Yes, there would be more value if that user/operator feedback could be
> gathered early enough so that it influences the schedule of the Design
> Summit.
> 
> I'm afraid that putting user/operator concerns discussion as "the first
> session of the design summit" would not significantly influence the
> content of the other pre-scheduled sessions. For example, I know that
> getting access to the User Survey pain points a few weeks earlier was
> really useful for PTLs working on design summit schedule.

Yes, that was great. I know it dramatically informed how I put together
my piece of the schedule, and what sessions I made sure to participate in.

> So yes, we need some forum to express user/operator pain points and
> priorities, but making it happen just after the PTL elections (one month
> before design summit) would be the most effective if the goal is to
> really influence what gets worked on for the next development cycle.

I really like this approach. I think that there would be no reason to
align the cadence with the design summit.

I actually think that the way the Linux Foundation does the End User
Summit is potentially an interesting pattern here (which we should
liberally borrow from when it makes sense) -
http://events.linuxfoundation.org/events/enterprise-end-user-summit

	-Sean

-- 
Sean Dague
Samsung Research America
sean at dague.net / sean.dague at samsung.com
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131219/91e5d5a4/attachment.sig>


More information about the Openstack mailing list