Qiming Teng wrote:
> On Tue, Oct 11, 2016 at 10:39:11PM -0500, Michał Jastrzębski wrote:
>> One of reasons we created PTG in the first place is that Summit became
>> big and expensive, and project developers had harder and harder time
>> attending it due to budget issues.
> So a trip to PTG is really cheaper than summit? Is the PTG one
> sponsored by someone?

PTGs happen in more cost-effective locations, airport hubs with cheaper
hotels, which should lower the cost of attending. Yes, I'm pretty sure
traveling to Atlanta downtown for a week will be cheaper than going to
Barcelona, Boston or Sydney downtown for a week.

>> [...]
>> PTG becomes very important for project team, summit arguably will
>> become less important as many of developers will be able to afford
>> only PTGs.
> Summit is less (or just NOT) important to developers, emm ... that is
> true if 1) the team knows exactly what users/ops want so they don't even
> bother interact with them, just focus on getting things done; 2) the
> person who approves your trip request also believes so.
>> If we say that "Don't expect Ops at PTG", that means
>> OpenStack dev community will become even more disconnected from Ops
>> community.
> Wasn't that part of the plan? [...]

Yes, the plan is (amongst other things) to make sure that upstream
developers are available to interact with users (operators, but also app
developers...) during the very week where *all* our community gets
together (the OpenStack Summit). Currently we try to get things done at
the same time, which results in hard choices between listening and
doing. By clearly setting out separate times for each activity, we make
sure we stay focused.

For an ops-focused team like Kolla, I'd argue that participating to
OpenStack Summits (and Ops midcycles, to be honest) is essential. That
doesn't mean that everyone has to go to every single event, but the
Kolla team should definitely self-organize to make sure that enough
Kolla people go to those events to close the feedback loop. The PTG is
not where the feedback loop is closed. It's a venue for the *team* to
get together and build the shared understandings (priorities,
assignment, bootstrap work) necessary to a successful development cycle
(some teams need that more than others, so YMMV).

Thierry Carrez (ttx)

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to