Open Stack

the next PTG is confirmed, and is in a time and region that meets the
community expectations for the next ops meetups, so i think giving it a go
is fine and appropriate.

If no more PTGs happen, or if they become less appropriate somehow,
kick-starting the independent events again is quite easy since these are
some of the most no-frills events I've been to - a venue, lunch, wifi, some
content etherpads, some moderators, you can have an Ops Meetup!

Chris

On Wed, Mar 28, 2018 at 4:10 PM, Jimmy McArthur <jimmy at openstack.org> wrote:

> Matt,
>
> Good question. The PTG is definitely occurring in the Fall.  We would
> evaluate the value of it as a community based on feedback from the PTG/Ops
> meetup, Board feedback, survey results, budget, etc...  If it was decided
> not to hold the PTG in 2019, we would of course need to reevaluate at that
> time.
>
> Let me know if I can answer any further questions.
>
> Thanks,
> Jimmy
>
> Matt Riedemann <mriedemos at gmail.com>
> March 28, 2018 at 2:32 PM
>
>
> Not to be too much of a downer here, but with the future of the PTG survey
> I just took, does the ops community want to wait until that's all sorted
> out? i.e. what happens if the future of the PTG means there is no PTG, and
> it's all just munged together at the Forum, which is no longer at the
> beginning of the cycle for vertical teams to plan their release (like the
> old design summit) and is prohibitively expensive for lowly devs and ops to
> attend? Would the ops community just want to continue doing what they are
> doing?
>
> Chris Morgan <mihalis68 at gmail.com>
> March 27, 2018 at 12:49 PM
> Hello Everyone
>   You've probably see the thread about possibly combining ops meetups with
> PTG to make a new broader event. Here is a rough draft of what that would
> actually look like:
>
>
> *"Monday and Tuesday are cross-project days where ops are welcome to
> attend SIG and other discussions, and if not interested can be travel days
> or whatever for them. Then Wed-Thurs are the two tracks/events where the
> ops folks have what has traditionally been done for ops meetups. Then
> Friday is a travel day or ops can stick around to follow up with dev-side
> thingsthat they weren't able to get to over the week or wanted to follow up
> on."*
>
> Thanks to Sean McGinnis for proposing this to get the ball rolling. This
> would mean there's a "normal" ops meetup for two days on days 3 and 4 of
> this combined event, with the option of attending earlier (days 1 and 2) if
> you want to contribute to dev/ops/openstack community sessions (e.g. SIGs),
> and possibly also staying a 5th day.
>
> The event is currently pencilled in for September in a central part of the
> USA. It will be organized by the Foundation logistically but the various
> sub-groups own their technical agendas.
>
> We unfortunately forgot to record the chat as a formal meeting, but you
> can see the raw IRC chat here
> http://eavesdrop.openstack.org/irclogs/%23openstack-operator
> s/%23openstack-operators.2018-03-27.log.html#t2018-03-27T14:03:40
>
> With the current level of support for this idea, it looks likely to
> happen, but, particularly if you object, please speak up ASAP. Note that
> this would be instead of the tentative idea we had of an event in NYC in
> August. If this is welcomed by the operators community, I'll certainly try
> to swap the sponsorship from my employer over to this as I feel it will be
> even more valuable and initial feedback from other potential sponsors is
> favorable.
>
> Please make your voice heard on this issue!
>
> Chris
>
> --
> Chris Morgan <mihalis68 at gmail.com>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Chris Morgan <mihalis68 at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20180328/8bf3e565/attachment.html>