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. 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. Note that it doesn't prevent having a operator day at the conference (and making sure the devs can attend it). -- Thierry Carrez (ttx) _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
