►
From YouTube: Learning Sync: 2021-03-23
Description
Meeting notes: https://bit.ly/38pal2Z
A
A
B
A
C
This
yeah,
I
I
added
that
for
like
just
to
figure
out
what
to
do
with
that
repository
and
to
plan
forward.
So
in
the
last
meeting
we
discussed
like
whether
catholic
would
be
something
that
would
be
useful
and
the
conclusion
was
yes,
but
we
still
need
to
figure
out
like
how
to
make
it
so
that
it
stays
in
sync
with
the
documentation
and
other
things
the
currently,
since
all
of
the
tutorials
are
not
migrated
over.
C
That'll
just
be
like
layout
things
which,
like
splitting
up,
commands
into
different
code
blocks,
or
something
like
that,
so
that
it
makes
like
it
works
on
both
the
sides
and,
while
working
on
that,
I
also
noticed,
like
some
small
issues
where,
like
so
not
not,
the
entirety
of
dogs
are
tested
using
that
tool.
What's
it
called
the
one
that
compliments,
google,
I'm
forgetting
the
name?
Oh
the
hugo
yeah,
yes,
yeah
yeah.
So
so
not
not,
all
of
the
dogs
are
tested
using
that
so
like,
for
example,
the
app
developers
there.
C
You
can
have
a
few
typos
that
I
discovered
since
they
were
coming
through
it,
and
I
think
we
should
also
try
and
remove
any
hardcoded
credentials
because,
for
example,
the
app
developer
guide
assumes
that
you
have
access
to
the
buildbackside
or
docker
registry
in
order
to
use
like
the
cache
image
stuff,
which
I
don't
know.
If
you
want
to
put
that
there.
C
C
If
we
can
figure
out
like
a
consistent
format
between
the
two,
so
I
was
hoping
we
could
create,
like
the
katakuri
version
of
it,
see
what
changes
we
have
to
make
to
the
official
docs
and
if
it
makes
sense
to
make
those
changes
and
then
sort
of
once
both
of
those
things
are
in
place.
We
can
then
merge
the
two
and
strip
out
those
mountain
extensions,
using
like
a
simple
set
or
something
else.
We
just
replace
those
things
with
with
like
just
white
space
or
something
like
that.
A
Yeah
yeah
that
definitely
makes
sense.
It
sounds
like
this
is
more
of
a
epic
than
a
small
issue
right.
So
so
I
appreciate
the
efforts
nonetheless,
and
I
think
you
know
as
I
get
we
go
forward
with
it.
I
think
the
first
step
is
kind
of
setting
up
the
the
environment
right.
So
I
think
we
want
to
set
up
a
catacota
organization
as
as
one
of
the
action
items
we
want
to
take
in
the
repo
that
you've
created
and
then
kind
of
at
this
point.
A
If,
if
the
discussion
is
you
know,
correct
on
our
slack
is
the
phase
one
would
be.
We
just
have
two
two
places:
we,
we
would
be
maintaining
the
tutorials
right
and
they
wouldn't
be
exactly
in
sync
and,
as
you
were
mentioning
right
now,
just
figuring
out
a
way
to
then.
Finally,
sync
them
up
at
some
point
in
time,
and
that
would
be
like
the
phase
two
right
and
then
yeah.
I
don't
know
if
we
need
to
go
further
than
that
right.
I
think
that
would
be
a
really
nice
spot.
A
A
It
looks
like
you
start
this
app
developer
guide
and
it
just
like
walks
you
through
maybe
what's
not
like
additive
changes
right
like
this
one
talks
about
this
one
thing
and
then,
like
the
context,
drastically
changes
to
this
one
now
talking
about
something
completely
different,
and
so
I
wonder,
if
that's
the
best
way
to
you
know,
formulate
it
or
if
it
would
be
better
to
like
break
up
each
individual
topic
into
a
tone.
You
know
section,
but
I
don't
know
if
that's
better
or
if
it
just
creates
more
clutter.
C
So
within
each
steps
you
still
retain
the
environment.
From
the
previous
step,
I
just
found
it
useful,
initially
like
while
iterating
to
have
like
that
back
set
up
and
the
docker
images
downloaded
from
my
previous
steps.
But
if
you
split
it
into
different
scenarios,
then
they'll
have
to
essentially
each
time
they
open
a
new
scenario.
It
sets
up
the
environment
again,
which
takes
a
few
seconds
but
yeah.
A
I
see
that
makes
sense
yeah.
I
guess
I
don't
have
a
strong
preference
right
now,
but
it
does
seem
like
the
scenarios
with
the
course
would
be
like
a
slightly
different.
I
don't
know,
maybe
within
the
course
you
could
also
have
like
a
table
of
contents.
I
don't
know
if
that's
possible,
but
where
you
could
jump
to
certain
scenarios
instead
of
having
to
go
one
at
a
time.
C
C
A
C
A
A
C
A
A
A
B
C
That's
sort
of
a
continuation
from
a
threat
we
had
in
slack
so
docker
and
cncf
are
organizing
these
series
of
like
workshop
stocks.
I
don't
know
like
a
series
of
notes,
essentially
based
around
different
aspects
of
container
technologies,
so
I
think
they're
starting
with
the
runtime,
and
they
eventually
want
to
tackle
like
images
and
security
and
more
so
the
runtime
schedule
is
already
out,
but
I
was
thinking
we
could
target
like
the
image
section
which
I
couldn't
find
any
details
about,
except
for
the
fact
they
just
mentioned
the
emit
section.
B
A
Yeah
I
was
able
to
find
a
blog
post
on
the
docker
blog
about
it
and
it
does
basically
kind
of
mention.
I
believe
your
was
one
of
the
primary
and
he
has
they
have
his
handle
to
go
ping
him
directly
on
the
cncf
slack.
So
that's
what
I
was
going
to
do,
but
if
you
feel
you
know
like
that's
something
you
want
to
take
on
by
all
means
that'd
for
him.
A
A
A
Okay:
okay!
Yes,
that's
like
what
I
found
on
the
blog
post,
too
I'll.
Let
them
link
to
that,
but
I
didn't
find
like
you
know.
This
is
who's
going
to
be
giving
this
presentation,
and
this
is
what
it's
about,
which
is
what
what
I'm
trying
to
like
gather
from
this
is
like
what
the
expected
audience
is
right.
Is
it
very
conversational
right
where
you
know
it's
back
and
forth,
or
is
it
really
like
presentations
and
that
that
sort
of
you
know
standard
setup.