{"body":"We also need to be careful with not restoring issues we had with the\nold-style Design Summit. We want to avoid creating conflicts that would\nreduce the productivity of the PTG (so running in parallel would be\ndangerous). We also want to make sure the PTG remains a work event\nrather than a feedback gathering event, as the start of the cycle is not\nthe best moment to introduce new priorities. That timing resulted in a\nlot of frustration in the past.\n\nRunning the Ops meetup on the last days of the week before is one\noption. That would let organizations save a bit on travel for people\nthat want to attend both (although hotel costs would increase with the\nstay-over-weekend). My personal objection to that is that my brain\nusually shuts down after 5 days of intense work, so I'm not looking\nforward to that long week (or I would skip the Ops meetup to focus on\nthe PTG).\n\nMore generally I think we need to have that discussion in the broader\ncontext of our event portfolio. What is the best way to have Ops meetups\nin 2018, with increased participation from ops in Forums at summits and\nOpenStack Days ? I feel like smaller, local events like OpenStack Days\nwere quite successful in reaching out to the silent majority of our\nusers that would not travel to a twice-a-year Ops Meetup. Should we\nencourage more of that ? The Public Cloud WG/SIG managed to hold\ndiscussions at various OpenStack Days as well... So we could encourage\nhaving ops-centric discussions around local OpenStack Days, and then use\nForums at Summits as the funnel to close the feedback loop in those\ndiscussions. That would reduce the need for a \"big\" twice-a-year Ops\nMeetup and let us piggyback on already organized events...\n\nJust thinking out loud...","name":"ttx","extension":"txt","url":"https://www.irccloud.com/pastebin/2H9PAX4A/ttx","modified":1511879051,"id":"2H9PAX4A","size":1728,"lines":30,"own_paste":false,"theme":"","date":1511879051}