<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 03/07/2018 06:12 AM, Chris Dent
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1803071211280.70132@cdent-m01.vmware.com">
<br>
HTML: <a class="moz-txt-link-freetext" href="https://anticdent.org/tc-report-18-10.html">https://anticdent.org/tc-report-18-10.html</a>
<br>
<br>
This is a TC Report, but since everything that happened in its
window
<br>
of observation is preparing for the
<br>
[PTG](<a class="moz-txt-link-freetext" href="https://www.openstack.org/ptg">https://www.openstack.org/ptg</a>), being at the PTG, trying to
get
<br>
home from the PTG, and recovering from the PTG, perhaps think of
this
<br>
as "What the TC talked about [at] the PTG". As it is impossible to
be
<br>
everywhere at once (especially when the board meeting overlaps
with
<br>
other responsibilities) this will miss a lot of important stuff.
I
<br>
hope there are other summaries.
<br>
<br>
As you may be aware, it [snowed in
<br>
Dublin](<a class="moz-txt-link-freetext" href="https://twitter.com/search?q=%23snowpenstack">https://twitter.com/search?q=%23snowpenstack</a>) causing
plenty
<br>
of disruption to the
<br>
[PTG](<a class="moz-txt-link-freetext" href="https://twitter.com/search?q=%23openstackptg">https://twitter.com/search?q=%23openstackptg</a>) but everyone
<br>
(foundation staff, venue staff, hotel staff, attendees, uisce
beatha)
<br>
worked together to make a good week.
<br>
<br>
# Talking about the PTG at the PTG
<br>
<br>
At the [board
<br>
meeting](<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/foundation/2018-March/002570.html">http://lists.openstack.org/pipermail/foundation/2018-March/002570.html</a>),
<br>
the future of the PTG was a big topic. As currently constituted it
<br>
presents some challenges:
<br>
<br>
* It is difficult for some people to attend because of visa and
other
<br>
travel related issues.
<br>
* It is expensive to run and not everyone is convinced of the
return
<br>
on investment.
<br>
* Some people don't like it (they either miss the old way of doing
the
<br>
design summit, or midcycles, or $OTHER).
<br>
* Plenty of other reasons that I'm probably not aware of.
<br>
<br>
This same topic was reviewed at [yesterday's office
<br>
hours](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T09:19:32">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T09:19:32</a>).
<br>
<br>
For now, the next 2018 PTG is going to happen (destination
unknown) but
<br>
plans for 2019 are still being discussed.
<br>
<br>
If you have opinions about the PTG, there will be an opportunity
to
<br>
express them in a forthcoming survey. Beyond that, however, it is
<br>
important [that management at contributing
<br>
companies](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T22:29:24">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T22:29:24</a>)
<br>
hear from more people (notably their employees) than the
foundation
<br>
about the value of the PTG.
<br>
<br>
My own position is that of the three different styles of in-person
<br>
events for technical contributors to OpenStack that I've
experienced
<br>
(design summit, mid-cycles, PTG), the PTG is the best yet. It
minimizes
<br>
distractions from other obligations (customer meetings,
presentations,
<br>
marketing requirements) while maximizing cross-project
interaction.
<br>
<br>
One idea, discussed
<br>
[yesterday](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T22:02:24">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T22:02:24</a>)
<br>
and [earlier
<br>
today](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-07.log.html#t2018-03-07T05:07:20">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-07.log.html#t2018-03-07T05:07:20</a>)
<br>
was to have the PTG be open to technical participants of any sort,
not
<br>
just so-called "OpenStack developers". Make it more of a place for
<br>
people who hack on and with OpenStack to hack and talk. Leave the
<br>
summit (without a forum) for presentations, marketing, pre-sales,
etc.
<br>
<br>
An issue raised with conflating the PTG and the Forum is that it
would
<br>
remove the
<br>
[inward/outward
focus](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-07.log.html#t2018-03-07T08:20:17">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-07.log.html#t2018-03-07T08:20:17</a>)<br>
concept that is supposed to distinguish the two events.
<br>
<br>
I guess it depends on how we define "we" but I've always assumed
that
<br>
both events were for outward focus and that for any inward
focussing
<br>
effort we ought to be able use asynchronous tools more.
<br>
</blockquote>
I tried bringing this up during the PTG feedback session last
Thursday, but figured I would highlight it here (it also kinda
resonates with Matt's note, too).<br>
<br>
Several projects have suffered from aggressive attrition, where
there are only a few developers from a few companies. I fear going
back to midcycles will be extremely tough with less corporate
sponsorship. The PTGs are really where smaller teams can sit down
with developers from other projects and work on cross-project
issues.<br>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1803071211280.70132@cdent-m01.vmware.com">
<br>
# Foundation and OCI
<br>
<br>
Thierry mentioned
<br>
[yesterday](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T09:08:04">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T09:08:04</a>)
<br>
that it is likely that the OpenStack Foundation will join the
[Open
<br>
Container Initiative](<a class="moz-txt-link-freetext" href="https://www.opencontainers.org/">https://www.opencontainers.org/</a>) because of
<br>
[Kata](<a class="moz-txt-link-freetext" href="https://katacontainers.io/">https://katacontainers.io/</a>) and
<br>
[LOCI](<a class="moz-txt-link-freetext" href="https://governance.openstack.org/tc/reference/projects/loci.html">https://governance.openstack.org/tc/reference/projects/loci.html</a>).
<br>
<br>
This segued into some brief concerns about the [attentions and
<br>
intentions of the
<br>
Foundation](<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T09:13:34">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-06.log.html#t2018-03-06T09:13:34</a>),
<br>
aggravated by the board meeting schedule conflict (there's
agreement
<br>
that will never ever happen again), and the rumor milling about
the
<br>
PTG.
<br>
<br>
# Friday at the PTG with the TC
<br>
<br>
The TC had scheduled a half day of discussion for Friday at the
PTG. A
<br>
big
[agenda](<a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/PTG-Dublin-TC-topics">https://etherpad.openstack.org/p/PTG-Dublin-TC-topics</a>), a
<br>
fun filled week, and the snow meant we went nearly all day (and
since
<br>
there's no place to go, let's talk, let's talk, let's talk) with
some
<br>
reasonable progress. Some highlights:
<br>
<br>
* There was some discussion on trying to move forward with
<br>
constellations concept, but I don't recall specific outcomes
from
<br>
that discussion.
<br>
<br>
* The team diversity tags need to be updated to reflect
adjustments in
<br>
the very high bars we set earlier in the history of OpenStack.
We
<br>
agreed to not remove projects from the tc-approved tag, as that
<br>
could be taken the wrong way. Instead we'll create a new tag for
<br>
projects that are in the trademark program.
<br>
<br>
* Rather than having Long Term Support, which implies too much, a
<br>
better thing to do is enable [extended
<br>
maintenance](<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/548916/">https://review.openstack.org/#/c/548916/</a>) for those
<br>
parties who want to do it.
<br>
<br>
* Heat was approved to be a part of the trademark program, but
then
<br>
there were issues with where to put their tests and the tooling
used
<br>
to manage them. By the power of getting the right people in the
room
<br>
at the same time, we reached some consensus which is being
finalized
<br>
on a [proposed
<br>
resolution](<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/521602/">https://review.openstack.org/#/c/521602/</a>).
<br>
<br>
* We need to make an official timeline for the deprecation (and
<br>
eventual removal) of support for Python 2, meaning we also need
to
<br>
accelerate the adoption of Python 3 as the primary environment.
<br>
<br>
* In a discussion about the availability of
<br>
[etcd](<a class="moz-txt-link-freetext" href="https://coreos.com/etcd/">https://coreos.com/etcd/</a>) it was decided that [tooz needs
to
<br>
be
<br>
finished](<a class="moz-txt-link-freetext" href="https://docs.openstack.org/tooz/latest/user/compatibility.html">https://docs.openstack.org/tooz/latest/user/compatibility.html</a>).<br>
<br>
See the
<br>
[etherpad](<a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/PTG-Dublin-TC-topics">https://etherpad.openstack.org/p/PTG-Dublin-TC-topics</a>)
for
<br>
additional details.
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>