►
From YouTube: Learning Sync: 2021-04-06
Description
Meeting notes: https://bit.ly/38pal2Z
A
All
right
good
morning,
most
and
yeah
welcome
all
let's
see
we're
starting
off
with
status
updates,
as
I
am
speaking
I'll
go
ahead
and
give
mine
in
regards
to
the
learning
sub
team.
The
only
thing
that
I've
really
done
is
on
the
build
packs.
I
o
site
added
google
analytics
and
a
dashboard
along
with
that.
A
So
I
added
a
discussion
or
a
topic
to
the
agenda
that
we
could
talk
about
like
what
kind
of
you
know,
metrics
or
data
we
want
to
capture
or
have
a
visual
of
yeah,
and
then
I
also
added
a
link
to
devstats
which,
if
you're
not
aware
devstats,
gives
you
like
it's
part
of
the
cncf
any
project.
That's
on.
There
has
a
lot
of
analytics
revolving
the
project,
so
a
lot
of
it
has
to
do
with
code
contributions,
but
it
goes
pretty
in
depth
into
a
lot
of
just
information.
B
A
A
A
A
A
So
some
of
the
you
know
basic
things
like
sessions,
total
users,
new
users
where
they're
coming
from
you
know
a
country.
A
lot
of
this
is
kind
of
more
or
less
taken
from
the
cato
dashboard,
so
that's
kind
of
like
our
starting
base,
but
I
wanted
to
open
up
the
discussion
to
see
whether
or
not
we
could
brainstorm
any.
A
A
You
know,
based
on
the
feedback
from
the
the
landing
page,
that
we'll
talk
about
a
little
bit
later,
like
it'd,
be
nice
to
know
that
when
people
jump
in
and
then
instead
of
clicking
around
just
immediately
jump
out
right
like
that
would
be
the
bounce
rate.
It'd
be
nice
to
know,
maybe
per
page
like
how
they
bounce
or
which
one
has
a
higher
bounce
rate,
and
maybe
from
there
we
could
kind
of
create
a
goal
of
trying
to
lower
that
bounce
rate.
At
some
point,.
A
A
B
A
Okay,
so
are
we
talking
about
like?
Maybe
I
I'm
pretty
sure
this
is
called
a
funnel
right,
but
our
in
in
our
particular
case
the
funnel
would
be
the
completion
of
the
the
guide
right
so
like
they
hit
the
end
of
the
guide,
for,
let's
say,
build
pack
creation.
So
we
have
that
for
catacota
right
so
you're
saying
we
should
probably
have
that
for
our
own
guides.
B
C
C
A
A
C
A
No,
it
doesn't.
I
think
that
was
part
of
some
of
the
discussion
during
the
rfc
process
is
because
of
the
way
it's
implemented
it.
It
becomes
very
difficult
it
it's
more
or
less
based
on
what
is
it
called
like
the
the
oci
registry,
the
image
registry,
that
that's
the
thing
that
tracks
it.
I
don't
recall
if
there
were
some,
like
you
know,
tangible
proposals
that
might
come
up
in
the
future,
but
as
of
right
now,
there
is
not.
C
A
So
I
think
the
problem
with
the
current
implementation,
if
I
remember
correctly,
is
that
for
at
least
pac
right,
if
you
you're
talking
about
pac
in
particular,
we're
pulling
the
entire
registry
right
like
we're,
cloning,
the
entire
registry
index
and
then
doing
a
lookup
on
the
file
system
right.
So
then,
theoretically,
right
a
solution
could
be
that
we
could
send
that
lookup
to
a
central
server,
some
somewhere.
B
C
A
A
A
A
The
project
itself
is-
and
you
know
this
is
probably
repetitive
to
some,
but
the
way
I
I
like
to
visualize
it
is
that
we
have
multiple
tiers
of
what
we
the
project
is
providing,
and
I
think
that
adds
to
the
complexity
of
trying
to
explain
exactly
what
it
is
that
we
are.
The
project
is
about
so
like
we
have
the
spec
at
the
core
right,
and
this
makes
it
interoperable
and
multiple.
You
know
there
could
be
multiple
implementations
and
you
know
it
creates
an
ecosystem.
It
enables
an
ecosystem.
A
Then
we
have
like
the
life
cycle.
The
engine
right
like
this
is
a
thing
that
people
could
use
and,
along
with,
like
the
build
packs
right
that
are
shareable,
but
like
the
project
itself,
doesn't
actually
produce
any
build
packs.
So
like
there
comes
like
the
first
kind
of
confusion
right,
the
build
packs
project
doesn't
have
build
packs.
A
Then
it
also
provides
like
some
user-facing
tools
like
pack
right
so,
like
that's
the
like
very
easily
tangible
thing
for
an
app
developers
like
pac
right,
but
it's
only
like
one
part
of
it
right.
So,
if
I
think,
if
we
sold
just
pack
right
or
if
we
sold
just
a
techton
integration
or
any
other
component
right
like
it's,
it
would
be
doing
a
disservice
because
we
we
want
to
like
create
an
ecosystem.
A
C
I
think
for
me
as
well,
when
I
first
got
introduced
to
buildbacks
like
listening
to
those
videos
that,
like
that
terence
or
emily
or
joe
presented,
that
made
me
understand
what
build
packs
were
more
so
than
the
landing
page
of
the
features
page,
because,
as
someone
new,
you
may
not
even
be
aware
of
some
of
the
terms
and
even
the
features
page.
It
shows
comparisons
against
things
which
again,
you
may
not
be
aware
of
so
like.
If
people
don't
know
what
like
advanced
caching
or
whatever
is
they
will
obviously
not.
B
C
C
The
main
part
of
what
cnb
does
is
is
part
of
that
banner,
which
says
cloudy:
buildbacks,
transform
your
application
source
code
into
images
that
can
run
on
any
cloud
and
then,
after
that,
the
next
thing
is
that
list
of
features
which
again
is
very
cryptic
to
people
who
don't
know
what
it
is.
And
then
the
next
thing
is
this
about
the
project
stuff.
C
B
A
A
C
A
So
I
was
hoping
to
bring
in
the
features
right
into
the
landing
page,
and
you
know
based
on
some
of
the
feedback.
The
way
that
we
do
so
may
may
change
right
and
even
more
so
would
change,
even
hopefully
for
the
better
if
we
base
it
off
of
the
video
right,
like
the
outcomes
of
the
video,
how
we
structure
the
video,
what
we
really
want
to
present
or
put
in
front
of
the
user
in
that
very
first
glance
would
be
the
things
that
we
would
want
to
put
in
the
main
page.
The
landing
page.
A
And
then
one
of
the
things
I
remember
when
we
first
did
the
the
features
was,
I
think,
right
now.
They're
they're
they're
definitely
obscure
right
and
very
high
level,
and
I
think
what
we
wanted
to
ultimately
do
is
maybe
link
them
to
like
where
people
could
read
more
about
a
very
specific
feature
right.
A
So,
if
you
look
at
our
features-
and
we
talk
about
like
building
materials
right
like
we
should
be
able
to
click
on
it,
link
to
like
what
does
build
materials
mean,
maybe
what's
its
value
and
how
you
know,
how
does
how
is
it
implemented
right
or
where
can
I
see
more
and
a
lot
of
the
other
features
here
like
rebasing
right,
like
we
have
a
page
for
rebasing,
so
linking
to
that
should
be
relatively
easy.
Yeah.
C
I
think,
for
each
of
these
features
like
having
a
concrete
example,
would
also
help
like
this
is
why
they're
useful-
and
this
is
how
they're
used
so
like
you-
can
link
to
a
bill
of
materials
and
maybe
some
of
the
projects
that
we
like,
like.
For
example,
in
the
tooling
section
we
link
to
things
like
kpac
or
git
lab
or
other
things
we
could
do
something
similar
for
like.
A
Yeah,
I
I
definitely
agree
with
that.
I'm
a
little
bit
hesitant
to
link
to
pocato,
specifically,
I
think
we're
trying
to
be.
You
know
as
agnostic
as
possible
in
regards
to
book
pack
providers
or
vendors.
So
that
would
be
the
only
like
real
reservation
there.
I
think
either
we'd
want
to
create
our
own
samples
yeah
exactly
or
use
the
samples.
B
A
B
D
Hello
guys
yes
yeah,
I'm
new
in
vmware
and
I
was
assigned
to
buildback
team
last
week.
I
was
talking
with
glennio,
so
I
just
found
this
meeting
in
the
website.
I
was
reading
a
little
bit
about
buildback
and
somehow
I
saw
the
meeting
link
and
I
said:
okay,
let's
join
because
it
seems
that
it
started
15
minutes
ago.
So
I
was
just
listening.
I
suppose
I
was
going
to
meet
you
at
some
point
with
the
manager
or
something
so
maybe
I
just
you
know,
do
it
without
any
notice
but
yeah
great.
D
I
I
believe
I
will
I've
been
playing
around
with
the
project
by
myself,
checking
the
github
repo
reading
about
it,
how
what
it's
doing
and
what
it's
not
so
yeah
so
far,
I'm
it's
very
cool
for
me
to
join
you
know.
Open
source
project
will
be
my
first
time
contributing
to
that
one
and
yeah.
I
hope
I
I
can
help
and
learn.