►
From YouTube: Sub-Team Sync: 2020-08-05
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
C
A
Cool
so
guest,
starting
with
standing
items,
we
could
kind
of
do
a
quick
roundup
for
status
updates.
A
I
think
last
time
we
broke
it
down
into
like
the
different
like
what
is
it
sections
or
subteams
right
so,
on
the
platform
side
of
things,
we're
getting
a
lot
of
prs
for
one
of
them
for
sure
is
tech
that
we're
making
changes
to
the
acceptance
tests.
I
think
simon's
been
working
a
lot
on
that.
Getting
that
progress
in
there
myself,
I'm
working
on
volume
mounts
the
read.
Write
volume
mounts
that
pr
is
in
draft
right
now,
making
some
final
tweaks
to
get
all
the
tests.
A
Passing
and
outside
of
that
I
was
looking
into
the
ssl
ca
certs
and
I
was
ping
a
couple-
people
emily
and
stephen
about
some
of
the
findings
and
what
we
really
wanted
to
do.
My
hope,
ultimately,
is
to
maybe
just
do
with
the
rewrite
volumes
and
provide
some
sort
of
guidance,
whether
it
be
like
a
blog
post
or
a
guide
on
our
website,
that
kind
of
explains
or
kind
of
walks
you
through
how
to
be
able
to
add
system
certs
to
your
build
process,
specifically
for
mac.
A
At
least
we
know
that
works
so
yeah,
that's
kind
of
where
I
I
wanted
to
shift
focus
onto
this
rewrite
volumes,
rfc
implementation,
that's
what
I'm
working
on
right
now,
david!
Do
you
have
anything
else,
david
and
travis
for
platform.
D
For
me,
thanks
again
david
and
javier
for
the
review
of
the
yank
command
for
the
build
pack
registry.
I
just
merged
that
in
a
little
bit
ago.
In
addition
to
that,
I
am
still
working
on
some
refactoring,
better
error
handling
around
the
github
actions
to
consume
registry
bill
pack,
registry
issues
that
come
in
through
github
once
that's
done,
and
we've
banged
on
it
a
little
bit.
D
The
next
phase
will
be
integrating
it
into
the
actual,
build
packs
organization
and
then
there'll
be
some
other
things
that
I'm
going
to
work
with
joe
on,
like
some
media
trying
to
get
it
out
there.
Basically-
and
hopefully,
people
can
start
using
it.
We
have
people
here
in
heroku
who
we
can
already
have
start
moving
over,
like
our
java,
our
node
and
other
language
build
packs
to
start
making
use
of
the
registry.
D
B
F
A
Okay,
I
could
speak
a
little
bit
about
the
the
learning
side
of
things,
the
learning
team.
Recently
we
added
the
features
page
to
the
buildpacks.io,
where
it
lists
all
the
features
to
the
best.
You
know
that
I
could
put
together
and
then
a
comparison
across
some
of
the
like
more
explicit
alternatives
to
build
packs
that
was
linked
to
on
the
home
page,
and
I
got
some
feedback
from
kashup
on
the
potato
side
where
he
thinks
that
we
can
make
that
kind
of
transition
a
little
bit
better
between
the.
A
Why
used,
build
packs
and
then
to
the
feature
set?
I
guess
you
could
say
so
I'll
continue
to
add
a
little
bit
there.
A
A
E
E
A
A
There
are
a
couple
items
that
did
come
up
throughout
the
week
that
we
added
on
here,
one
of
the
things
from
amica
had
to
do
with
a
rebate
issue
that
he
found
and
he's
trying
to
propagate
through
through
ggcr
image
detail
which,
if
our
my
memory
serves
me
correct,
we'll
have
to
get
lifecycle,
updated
and
then
pack
to
up
update
the
lifecycle
dependency,
so
a
little
a
little
blocked
on
the
pack
side,
but
it
seems
like
it's
got
a
little
good
traction
behind
it
right
now.
A
The
last
time
we
had
this
meeting,
we
kind
of
like
weaved
our
priorities
into
the
top
of
backlog.
That
is
something
that
we
could
continue
doing.
Some
of
the
feedback
that
I
did
get
back
was
that
there
wasn't
a
lot
of
life
cycle
stuff
at
the
top,
and
I
don't
know
if
that's
something
that
we
want
to
focus
in
on
this
meeting.
F
A
So
I
guess
my
question
would
be.
How
would
the
stuff
that,
let's
say
jesse
would
want
to
work
on?
How
would
he
know
what
what
would
be
best
for
him
to
prioritize?
If
we're
talking
saying
that
this
is
currently
like
platform
focused.
F
F
That's
slated
to
be
in
the
next
release
has
sort
of
felt
like
an
appropriate
level
of
prioritization
like
if
it's
going
to
be
the
next
release,
it's
a
higher
priority
than
if
it's
not
and
then
within
that,
like
I
haven't,
really
felt
the
need
to
prioritize
those
things
against
each
other.
G
I
think
one
of
the
conversations
we
had
is
that
I,
I
think
one
of
the
desires
from
from
our
sort
of
internal
company
team
of
people
that
are
working
on
cloud-native,
build
packs
is,
is
that
we
can
have
a
kind
of
consistent
space
where
we
can
get
a
view
as
to
as
to
what
our
priority
would
be
for,
especially
for
those
who
don't
have
a
sort
of
pre-existing
idea
of
like
oh,
I
know
exactly
what
I'm
going
to
jump
to
next,
I'm
not
saying
that
supersede
that
if
we
already
know
what
we
want
to
work
on
we're
very
comfortable,
but
I
think
in
order
to
get
more
of
us
just
sort
of
being
able
to
gently
familiarize
ourselves
with
the
different
code
bases,
it
would
be
really
useful
to
have
like
that
single
view,
and
even
if
it
just
means
kind
of
allowing
us
to
internally
put
the
priorities
side
by
side,
wouldn't
necessarily
change
the
priority
for
you
right
emily.
G
We.
I
don't
think
we're
saying
that
if
we
were
to
have
life
cycle
stories
interweave
with
this
backlog,
you
would
then
have
to
suddenly
start
working
on
three
pack
stories
before
you
could
pick
up
a
life
cycle
story,
but
it
would
mean
that
once
I'd
finished
those
three
pack
stories,
I
would
have
the
opportunity
to
then
say:
okay,
I
guess
we've
decided
collectively
that
the
next
big
thing
on
for
the
whole
project,
the
project
as
a
whole,
is
I
want
to
pick
up
this
life
cycle
thing.
C
And
also
just
chime
in
on
that,
like
I
haven't
necessarily
done,
you
know
personally,
I
haven't
done
much
life
cycle
work
in
the
past,
but
that's
not
to
say
that,
like
if
I
didn't
know
that
something
was
especially
important
or
something
good,
easy
low-hanging
fruit
I
wouldn't
go,
I
wouldn't
go
to
do
it.
I
just
don't
think
to
look
at
the
life
cycle
issues
as
much
and
I
don't
know
what's
not
easily.
C
F
Well,
I
definitely
see
the
ask
like
people
want
to
know
how
to
contribute.
I
feel
like
to
put
it
in
this
priority
board.
I
would
have
to
weigh
its
priority
against
the
priority
of
things
in
pack,
which
I
don't
have
a
good
sense
of
at
the
moment,
what
the
part
of
things
in
pack
r,
I'm
sure
I
care
at
that
level
of
detail
right.
F
A
Able
to
what,
if
we
don't
put
them
against
each
other
right
so
like
right
now.
What
I
did
was
I
just
kind
of
collapsed
and
removed
a
lot
of
stuff.
That's
not
important,
like
I
think,
even
the
image
you
till
might
be
important
to
the
implementation
team.
So
in
this
particular
view
right,
it
might
be
easier
for
you
to
be
over
able
to
prioritize
those
items
right
and
then
I
guess
still
at
a
high
level.
H
I
have
a
feeling
that
this
conversation
conversation
relates
to
the
other
topic
that
I
added
to
the
document.
The
way
we
want
to
work
with
life
cycle
in
general.
However,
I
think
that
you
want
to
bring
this
up
today
with
emily,
so.
A
A
H
H
H
Mean
we
had
a
different
opinion
on
how
to
work
on
life
cycle
for
in
our
team,
so
I
thought
maybe
it
relates
to
to
how
we
want
to
work.
I
need
to
bring
the
issues
of
pack
and
life
cycle
to
zenhub.
I
feel
that
these
two
topics
relate
to
each
other,
but.
G
I
think
there's,
maybe
doesn't
maybe
isn't
required
to
have
the
focus
on
a
prioritization.
I
think
that's
where
we
may
be
tripping
ourselves
up
in
this
in
this
situation.
G
It
sounds
like
we're
more
interested
in
this
kind
of
bucket
and
what
we're
gonna
move
in
in
terms
of
like
changing
the
goal
posts
in
response
to
external
factors.
I
how
much
we've
done
is
the
release
timing,
as
opposed
to
the
feature
sets
so
we're
we're
basically
saying
these
are
of
equal
priority.
We
will
do
them
all
barring
some
unforeseen
cataclysm,
and
then
we
will
make
a
release
almost
regardless
of
how
long
that
will
take
us,
so
in
which
case
that
doesn't
really
need
a
prioritization,
but
what
we?
G
What
we
do
need
in
order
to
kind
of
asynchronously
be
able
to
pick
up
pieces
of
work
without
worrying
about
duplicating
effort
is
to
have
a
a
known
state
for
each
of
those
each
of
the
things
in
the
bucket.
We
need
to
know
if
someone's
doing
this
already,
if
someone
started
it
and
put
it
down
and
the
stuff
exists
on
a
branch
somewhere.
If
someone
like
fully
intends
to
do
this
in
a
way
that
they
don't
want
anyone
else
to
interfere
with
or
whether
this
is
genuinely
like
good
to
go,
get
started
immediately.
F
I
think
that
makes
a
lot
of
sense
that
framing
the
problem,
especially
for
a
life
cycle,
where
we're
sort
of
boxed
into
doing
feature-based
releases
rather
than
time-based
releases
by
the
like
the
what's
the
word,
the
atomic
nature
of
the
spec
spec
versions,
and
I'm
definitely
not
opposed
to
having
a
meeting
where
people
who
are
interested
in
that
work.
We
can
like
go
over
what
state
things
are
in.
F
And
I
know
for
things
that
I've
created
a
little
life
cycle
issues
for
in
the
past,
if
say,
like,
the
spec
isn't
finalized,
yet
I'll
stick
a
special
label
on
it,
so
that,
like
maybe
you
can
start
working
on
it
but
know
that
it's
not
the
exact
wording
isn't
in
the
spec
yet.
So
it's
got
something
to
keep
an
eye
on
before
the
release
stuff
like
that.
A
My
alternative
proposal
would
be:
could
it
not
be
as
simple
you
know
to
kind
of
align
with
what
the
platform
side
does,
which
is
more
on
the
time
based
release
where,
in
here,
the
backlog
listed
here
could
be
only
the
stuff
in
the
milestone.
A
F
B
You
know
found
in
zenhub,
but
I
feel
like
there
are
other
reasons
why
you
have
face-to-face
meetings,
and
I
don't
know
if
we're
trying
to
cover
all
of
those
here
but
like,
for
example,
just
context
sharing
or
helps.
You
know,
I'm
working
on
x
issue
right
now
and
I'm
stuck
here
like,
maybe
that's
something
that
could
just
be
had
in
slack
like
a
conversation
that
you
know.
B
Maybe
then
proceeds
to
you
know
zoom
or
whatever,
when
it's
required,
but
I
don't
know
I
I
not
exactly
sure
what
I'm
asking
of
the
group
but
like
do.
We
feel
that
we
have
established
the
right
practices
so
that
people
who
are
interested
in
contributing
to
either
either
you
know,
platform
or
implementation,
or
you
know
whatever
else-
can
get
the
support
that
they
need.
F
I
like
the
idea
of
trying
to
use
slack
more
if
we
can,
like
I've,
seen
teams
that
sort
of
have
a
remote
or
have
a
text
based
stand
up
right.
So,
like
once
a
day
in
a
specific
channel,
you
just
write
a
sentence
or
two,
but
what
you're
working
on
so
it
gives
everyone
a
chance
to
look
for
areas
where
they
are
like.
Oh,
I
know
what
that
person's
blocked
on.
Maybe
I
can
help
them
and
also
get
an
overview
of
what
people
are
up
to.
A
Yeah,
I
totally
agree
and
value
asynchronous
or
just
you
know,
having
a
very
distributed
way
of
communicating.
I
do
think
that
having
these
you
know
in
this
case,
bi-weekly
sinks
is
valuable
in
that
it
does.
At
least
it
provides
us
a
certain
point
in
time
in
which
we
could
all
get
together
and
actually
communicate
things
that
might
be
too
hard
to
communicate
via
text
right.
B
Yeah,
I'm
all
for
that.
I
think,
personally,
part
of
the
reason
why
it's
hard
for
me
to
turn
to
public
slack
as
the
first
choice
for
asking
my
questions
is
because
often
my
question's
gonna
look
something
like.
I
just
realized
that
I
have
no
idea
how
this
thing
works.
B
I'm
I'm
actually
okay,
like
personally,
I'm
okay
with
being
more
exposed,
but
I
could
see
how
some
people
might
not
feel
comfortable.
E
A
All
right,
so
I
think
we're
done
with
the
status
updates.
So
now
talking
about
you
know
the
planning
side
of
things
I
don't
know,
I
feel
like
we
kind
of
broke
out.
We
went
into
this
like
different
rabbit,
hole,
different
conversation,
it
seems
like
the
things
for
life
cycle
are
slightly.
You
know
different
in
the
way
that
they
work
versus
pac.
A
I'm
not
entirely
sure
what
to
do
about
it,
at
least
for
the
platform
side
of
things
where
we
do
prioritize
items
we
work
more
based
on.
You
know,
whatever
can
make
into
this
release,
cadence
versus
having
specific
milestones,
I'm
not
a
proponent
of
changing
that,
but
it
doesn't
mean
that
we
can't
have
that
conversation
but
yeah.
A
So
maybe
that's
something
that
the
platform
team
could
take
separately,
but
I
don't
know
I
feel
kind
of
weird
about
it,
because,
even
though
that's
a
decision
that
platform
maintainers
can
do,
I
feel
like
we
get
a
lot
of
really
good
value
and
feedback
from
other
people
right.
I
think
emily.
In
the
last
meeting,
you
proposed
certain
things
that
you
wanted
to
get
done,
that
I
don't
think
otherwise
we
would
have
cared
to
at
the
top
of
the.
A
A
I
don't
know
if
there's
any
actual
thoughts
you
know
there,
but
if
we
look
from
that
arena
at
what
the
platform
side
of
things
is
going
to
do,
are
there
any
kind
of?
Maybe
the
the
real
question
is,
instead
of
prioritizing
every
single
item
in
the
backlog,
it's
more
like
a
a
place
in
time
where
anybody
could
bring
up
anything
that
they'd
want
to
add
to
the
very
top
right,
something
top
of
mind
to
them.
A
Aside
from
this
rebase
issue
that
propagates
to
different
aspects
of
the
of
the
system,
I
think
there's
there
hasn't
been
a
lot
of
requests.
There
is
something
that
came
up
recently,
which
I
maybe
wanted
to
run
by
everybody,
because
it
is
a
pac-specific
thing.
A
C
C
But
with
s2i
they
did
note
the
difficulty
of
having
it.
You
know
when
it's
further
down
in
the
tree.
E
C
A
A
Something
that
we
don't
have
cool
so
yeah
what
you
know.
I've
looked
at
this
backlog.
Quite
a
lot.
I'm
curious
from
a
life
cycle's
perspective.
What
that
looks
like
for
the
things
that
are
important.
A
I
know
that
it
that
isn't
on
this
document
right
now,
but
if
we
were
to
look
at
the
build
packs
lifecycle
is
that
where
we
would
currently
see
what
is
being
worked
on.
F
F
F
F
Most
of
it
is
in
progress,
except
for
the
one
windows
bug.
I
saw
a
comment
on
that
that
the
windows
team
tried
to
validate
it
and
couldn't
reproduce
it.
So
it's
going
to
go
back
and
see
whether
it
is
reproducible
in
my
machine
now
or
not
whether
it's
like
a
machine
difference
or
it
has
been
fixed
by
some
other
change
to
master
accidentally.
F
C
Is
that
going
to
need
something
on
pax
and
also.
C
F
F
That's
usually
people
launch
their
app
images
with
docker
run
rather
than
with
pack
and
a
lot
of
these
changes
that
are
going
into
0.90
until
pac
supports
platform,
api
04
and
tells
the
life
cycle
to
use
it.
You
won't
really
see
any
of
these
changes,
so
there
might
be
a
lot
of
features
in
the
new
lifecycle,
but
as
long
as
pack
is
still
using
the
old
api
things
will
look
the
same.
E
E
A
B
C
I
would
not
immediately,
but
in
a
few
weeks
I'm
going
to
be
moving
across
multiple
time
zones
and
this
is
going
to
be
pretty
late
at
night
this
time
slot.
So
I
would
also
advocate
for
moving
it,
hopefully
some
any
day
the
weekend
earlier,
but
you
can.
I.
I
was
going
to
raise
that
when
I
was
actually
there,
I'm
trying
to
figure
that
out.
A
A
meeting
around
my
name
that,
honestly,
one
of
the
thoughts
that
has
come
up
is
also
instead
of
having
this
every
other
week,
which
is
kind
of
a
pain
to
schedule.
A
B
Do
we
need
a
mechanism
to
determine
a
viable
time
for
everyone,
given
that
we
can't
see
everyone's
calendars.
A
Yeah
I
mean
typically,
this
is
really
hard
to
do.
I
could
look
into
candy
calendly,
but
I
don't
think
we
have
a
paid
version
for
it
yet
so,
honestly,
one
of
the
things
that
I've
been
doing
is
just
reaching
out
to
travis
and
jesse,
since
I
could
see
everybody
else's
calendar
and
just
pinging
them
and
seeing
if
that
certain
times
work
for
them.
E
A
Last
but
not
least,
there
are
certain
people
that
are
gonna
work
at
a
booth.
Is
everybody
aware
that
is
working
that
booth
that
they
have
to
sign
up
by
end
of
day-to-day
for
the
booth?
A
A
Yeah
so
like
there's
an
email,
I
sent
it
in
a
private
slack
that
you
should
be
looking
for.
It
has
the
instructions
for
how
to
sign
up
for
kubecon
and
a
certain
code
that
you'll
need
and
the
signup
the
registration
isn't
quick.
I
mean
it
has
a
lot
of.
You
know
typical
questions
like
what
projects
do
you
use
blah
blah,
so
just
it
takes
about
10
minutes.
It's
not
a
two
minute
thing.
I
I
I've
been
emailing
with
jesse
he's
on
vacation,
but
he
reached
out
asking
if
he
should
sign
up
for
it
and
take
the
spot,
and
I
told
him
yes
sign
up
for
everything,
and
so
hopefully
does
that
having
somebody
on
the
vmware
side
reach
out
to
people
at
the
cncf
and
just
to
make
sure
that
if
we
don't
get
him
and
other
folks,
all
perfectly
signed
up
with
the
correct
email
addresses
and
everything
that
we
have
some
leeway
and
that
they
can
fix
stuff.
I
A
Deal
yeah
ben
hale
redid
a
demo
for
us
specifically
for
this
event,
so
dude
he
took
your
spotlight.
I
Emily
sorry
did
we
get
that
does
does
grandma
know
to
give.
A
Yes,
okay,
I've
been
coordinating
with
karima
and
them
also
for
those
at
least
the
ones
that
are
working.
The
booth,
we're
gonna,
get
some
shirts
or
something,
and
so
I'm
gonna
be
designing
that
here
in
a
bit
and
it's.
C
I
think
I
I
mean
I
I
I
I
may
be
able
to
do
some
of
the
hours,
certainly
on
the
17th
and
18th
just
to
have
like
my
moving
movers
coming
in
the
19th.
So
everything
will
be
a
bit
a
bit
in
question,
but
I
definitely
should
be
able
to
use
some
to
do
some
hours
for
the
booth
for
the
17th
and
18th.
I
You're
not
signed
up
for
the
booth
or
I
don't
think
you're
on
the
that
list
of
the
five
people
that
they're
going
to
add
to
the
booth
staff.
People
thing
I
don't
know
how
much
it
matters
and
actually
the
project
pavilion
is
open
to
anybody.
It's
you
don't
have
to
have
a
just
to
be
an
attendee.
You
don't
have
to
pay
anything
for
the
project.
I
Pavilion
pass,
there's
like
a
complimentary
pass,
so
you
may
be
able
to
be
in
the
booth
and
talk
to
people,
but
if
you
want
them
to
designate
you
as
a
moderator,
we
can
do
that
because
I
think
we
can
add
more
than
five
people.
We
just
can't
give
people
free
passes
to
the
conference
on
top
of
that.
So
the
question
is:
are
you
registered
for
cubecon?
In
the
end.
I
I
I
I
That's
the
main
thing.
Whatever
email
you
put
your
slack,
because
that's
the
one
that
went
to
the
booth
builder
people
and
if
you're,
not
in
that
five
list,
which
is
travis
jesse
me
javier
and
natalie.
I
think
I
think
we
have
extra
passes
if
you're
not
signed
up
for
kubecon
and
I
can
get
those
because
I
was
already
signed
up
and
I
expensed
it
and
everything
and
so
mine's
open
and
javier.
I
don't
know
if
you
were
you
signed
up
already.
No,
I
was
not.
We
have
one
extra
pass.
A
I
I
I
We
can
get
you
added
to
the
booth
list,
but
I
kind
of
need
that
by
the
end
of
the
day,
if
that's
okay,
whether
you
wanna,
do
it
so
reach
out
in
the
maintainers
channel
all
right,
it's
been
like
a
whole
mess
of
stuff
over
the
past
couple
days,
yeah
we're
working
through
half
of
that.
Last
reason
why
I'm
not
paying
as
much
attention
here
just
trying
to
figure
out
logistics
for
this.
I
E
A
Right
so
yeah
we
could,
if
there's
nothing
else,
we
could
have
10
minutes
back
of
our
lives.
Get
that
life
cycle
release
out.
You
know
we.