►
From YouTube: Learning Sync: 2021-06-15
Description
Meeting notes: https://bit.ly/38pal2Z
A
B
A
I'm
here
for
you,
I'm
here,
for
you
too,
if
you
need,
oh,
if
you
don't
mind
digging
those
sides,
I
do
not
mind
at
all.
It's
my
pleasure.
It's
it's.
B
Cool
so
status
updates.
I
don't
think
I
have
anything.
Last
week
I
was
mostly
busy
with
like
some
buildback
stuff.
We
do
have
a
new
team,
the
buildback
authors,
team,
wow
and
I
know
there
have
been
lots
of
discussions
in
the
past
on
how
documentation
could
be
improved
for
buildback
authors,
especially
since
a
lot
of
things
are
currently
only
in
the
spec
and
not
documented
on
the
website.
B
So
looking
forward
to
working
with
the
new
team
to
try
and
improve
state
of
the
docs
user
research,
I
don't
know
anthony
if
you
know
anything
what's
happening
here.
A
B
I
don't
think
we
have
anything
either.
So,
let's
go
ahead
to
the
next
topic,
which
is
still
issues
and
pull
requests.
So
let's
look
at
the
scale
issues.
B
Let
me
quickly
update
the
date
to
be
okay,
so
we
usually
try
to
go
and
look
at
the
least
recently
updated
issues
and
try
and
see
if
we
can
act
upon
them,
that's
good.
So
first
one
up
is
buildback
groups.
B
B
Team,
if
there's
anything
specific
that
the
buildback
authority
might
want
to
look
at
this,
for
it
might
be
useful.
B
A
B
Add
documentation
of
configuration
files.
We
went
through
this
last
time
where
there
are
like
a
bunch
of
related
issues
and
we
tried
updating
them.
So
this
is
just
like
a
meta
issue
to
track
all
the
like
child
issues.
We
did
go
through
all
of
them
last
time,
so
there's
I
don't
think
much
to
do
on
this
one.
B
B
B
A
B
So
if
I
remember
correctly,
there's
a
improved
performance
with
caching,
it
just
caches
the.
B
B
Yeah,
this
clearly
seems
like
a
buildback
author's
guide.
I
don't.
I
think
this
was
initially
tagged
as
the
implementation
team,
because
there
was
no
buildback
author's
team.
B
A
B
For
steel
issues,
next
up
we
have
coprs.
B
B
A
B
Created
the
pull
request
and
we
have
some
pending
like
joe
and
I
gave
our
thoughts.
We
had
some
pending
questions.
A
B
B
So
this
one
is
a
community
one.
I
think
we
pinged
emily
last
time.
B
And
for
the
unlabeled
issues,
I
think,
since
we
have
created
the
new
team,
we
have
not
updated
the
photos.
Actually,
I'm
just
gonna.
B
A
Okay,
yo
thanks
this
was,
I
gotta,
say:
you're,
pretty
good
at
this
you're
very
efficient,
any
agenda
items,
anything.
A
B
B
Since
both
javier
and
david
are
not
here,
maybe
we
can
talk
about
it
when
they
are
because
they
know
more.
A
Okay,
I'm
fine
with
it.
Let's
just
talk
about
a
swim
is
a
dox
tool.
A
A
Okay,
one
other
question:
for
you
not
to
take
up
your
time.
I
did
have
a
question
about
your
catacota
docs,
which
was
really
good
for
the
project.
I
guess
I'm
wondering
if
you
know
you're
seeing
the
traction
you
are
for
right
right,
like
I
know
that
we,
you
know,
I'm
sure,
you've
been
in
this
project
for
a
while.
We
keep
talking
about
hey
doctor
are
not
great.
They.
You
know
for
entry-level
developers
right
for
for
newbies
right,
but
you
made
these
catacota
docs.
A
B
Do
I
see
the
same
thing
about
what
like
sorry,
I
didn't
get
your
question.
No.
A
That's
right,
it
was
a
poorly
worded
question.
I
guess
I'm
just
speaking
out
loud,
I'm
just
speaking
a
lot
like
you
know.
When
we
talk
about
hey,
we
want
to
make
docs
more
accessible.
We
want
to
make
better
docs.
You
know
you
have
these
catacota
docs,
which
pretty
much
do
exactly
that.
You
know
why.
Why
isn't
part
of
that?
Why
isn't
that
the
strat
part
of
our
strategy?
I
guess.
B
I
think
it
is
we've
been
trying
at
least
all
the
existing
like
hands-on
tutorials
have
been
converted.
What
I
think
the
next
step
is
is
to
one
figure
out
how
we
can
more
deeply
integrate
category.
B
I
think.
Last
week
we
had
an
agenda
item
where
we
wanted
to
talk
with,
like
the
leadership
team
on
getting
like
an
enterprise
catholic
subscription,
so
that
we
can
embed
it
into
the
website
itself.
B
So
I
know
other
cncf
projects
like
cube,
istio,
etc.
Oh
sorry,
not
history,
but
cube.
Has
it
and
like
so,
does
docker
and
like
a
bunch
of
other
cloud
native
tools,
so
they
have
like
an
enterprise
version
where
they
embed
these
tutorials
and
then
and
then
once
it's
on
the
website,
we
can
also
track
engagement
and
everything
else
in
a
unified
fashion,
with
the
rest
of
our
like
metric
tooling.
B
So
currently,
the
other
issue
with
carthage
is
like
the
metrics
and
engagement
is
on
like
a
separate
platform
itself
and
there's
no
easy
way
to
connect
to
and
follow
like
which
tutorials
are
interesting
to
our
users,
which
ones
like
which
tutorials
are
places
where
they
start
off.
But
they
just
leave
in
the
middle
because
they
can't
follow
the
logic
or
something
like
that.
A
Okay
know
that
that
sorry
for
the
poorly
worded
question,
but
that
did
help
me
a
lot
right.
I
I
don't
know
you
know
we
have
this
road
map
item
about
documentation,
rework
it
seems
like
you've
made
a
step.
I
just
don't
want
it
to
be.
You
know
sam's
thing
right,
sam's
initiative
that
he
he
did
on
the
side
right.
This
is
clearly
for
the
project
and
it
was
one
of
our
big
ticket
items.
B
Yeah,
I
appreciate
the
thoughts
I
think,
like
other
maintainers
are
also
aware.
It's
just
that
we're
stuck
where
karthikova
is
also
at
this
point
sort
of
being
merged
into
o'reilly
as
an
offering.
So
I
think
we
we
just
have
to
figure
out
like
how
to
integrate
it
better
with
the
rest
of
the
website,
so
that
one
other
issue
right
now
is
that
whenever
you
update
the
tutorials
on
the
docs
github
repository,
you
have
to
make
a
similar
pr
on
the
carthagoda
one.
B
But
if
you
could
just
embed
the
the
the
the
tutorials
themselves
in
the
website,
we
could
avoid
the
duplication
and
extra
tooling.
So
it's
it's
definitely
on
our
minds.
I
think
just
needs
someone
from
the
leadership
team
to
figure
out
how
to
like
either
create
like
a
cncf
service,
just
ticket
to
figure
out
what
like,
if
we
are,
if
we
get
any
benefits
or
like
do,
we
have
to
set
this
up
on
our
own.